(248) 706-1540 | sales@KorsEngineering.com

PRODUCTS COMPANY SERVICES SUPPORT RESOURCES CONTACT

Plex DataSource Test Client

In order to be able to quickly and (relatively) easily interact with the Plex "Data Source" web service, we have created a tool to be able to see and execute them. One of the main purposes in creating this tool was to make it easier to create templates for the PleXML Micro Web Service Client (MicroWSC) object - but it turned out to be a pretty good way to manually execute the Plex data source web services on its own. The app is built with .NET, so you really shouldn't need to install it to run it on any machine that has a .NET 2.0 or greater runtime. The picture below is taken after a transaction has been executed - when you first launch it the first time some of the fields will have to be filled in with your account information.

Plex DataSource Test Client.png

Each if the highlighted fields above is described below:

  1. The Proxy information must only be filled out if your internet access is through a proxy.
  2. The Plex URL for sending the transactions. This should always be either https://hermes.plexus-online.com/DataSource/Service.asmx for the Plex test database or https://mercury.plexus-online.com/DataSource/Service.asmx for the production database.
  3. These should be the username and password assigned to your PCN for doing Web Service transactions
  4. The data source key to get a template for. Use the Plex Customer Data Sources page to find the key of the data source you would like to execute.
  5. The Get Template button will connect to Plex to discover what the input parameters are for the data source key entered. This should fill in boxes 6 and 7.
  6. This box shows the proper structure of a web service request for the entered data source. If you are using a tool like SoapUI to send manual transactions, this is the sample you could use.
  7. This box gives a template that can be directly copied and pasted to a PleXML MicroWSC object in the Request Template field. The template will have variables or the most appropriate data type inserted at the correct locations (see {s:inPLCName} in the example above).
  8. The grid will show all of the input parameters (both optional and required) defined by the entered data source. To execute the web service you can fill in values for any parameters you would like to pass.
  9. This box will probably cause a little bit of grief (and if we rewrite this in the near future, it will change!!!). Basically, this box should always have the same value as box 4 above but it DOES NOT populate itself automatically.
  10. Use this button to send a transaction to Plex with the entered datasource key (in box 9) and parameters in grid 8. This should fill in boxes 11 and 12.
  11. This box will shows the proper structure of a web service response from Plex for the entered data source. If you are using a tool like SoapUI to send manual transactions, this is the result you would expect to see.
  12. This box gives a template that can be directly copied and pasted to a PleXML MicroWSC object in the Response Template field. The template will have variables inserted at the correct locations (see {s:inPLCName} in the example above). Because no datatype is returned by Plex for these fields, ALL VARIABLES WILL BE OF TYPE STRING – but they can be changed before pasting into the MicroWSC. Use {s for string, {b for boolean and {n for numeric.
  13. This box can be used to show different "rows" if Plex is returning more than one row of data. By default, box 11 only shows the first row returned by Plex.

 I found this article helpful. (0)