In this tutorial you will create the LANSA Integrator SOAP Agent solution that you will use with LANSA Composer's JSM Binding Scripts in later tutorials.

After you have defined the solution you will build it and deploy it to your LANSA Composer server, ready for later use.

  1. Open LANSA Integrator Studio from the Tools menu within the LANSA Composer client program.
  2. Right-click on Projects and select New Project from the popup menu.  Type CurrencyExchangeRate as the new project name and click OK.
  3. Right-click on Solutions and select New Solution Group from the popup menu.  Type CurrencyExchangeRate as the new solution group name and click OK.  Click Yes when asked to confirm the new solution group.
  4. Expand Solutions, right-click on CurrencyExchangeRate and select New Solution from the popup menu.  Complete the dialog as shown and click OK.
  5. When the New SOAP Agent Project window is shown, click Browse to specify the location of the WSDL that defines the SOAP service to be used.  Copy and paste the following string into the resulting Select WSDL window, and click OK.  Then click OK in the New SOAP Agent Project window.
    http://www.webservicex.net/CurrencyConvertor.asmx?WSDL

  6. The LANSA Integrator SOAP Wizard window should now be shown.  Click the Operations tab at the bottom to display the available SOAP operations for this web service, select the ConversionRate operation and click (check) its checkbox.  You should now see the outbound and inbound parameters that are defined by the web service for the ConversionRate operation.
  7. Right-click on the FromCurrency parameter and select Field from the popup menu to specify the program field that is to be bound to this parameter.  Type DXBINDF0A as the field name and click OK.  (You do not need to type anything in the Format box.)
  8. Repeat the previous step for the ToCurrency parameter, but this time specify DXBINDF0B as the field name.
  9. Repeat again for the ConversionRateResult return parameter, but this time specify DXBINDF0C as the field name.  The LANSA Integrator SOAP Wizard window should now look similar to this:
  10. Click the Build tool button () to generate and compile the solution.
  11. Close the LANSA Integrator SOAP Wizard window, clicking Yes when prompted to save your changes.
  12. Back in the LANSA Integrator Studio window, expand the CurrencyExchangeRate solution, then right-click on the CurrencyExchangeRate.soap.jar file and select Send To / Integrator Folder from the popup menu.
  13. Repeat the previous step for the SOAPAgentService.properties file.
  14. In the LANSA Integrator Studio window, expand the Servers item near the bottom of the tree and double-click the server definition corresponding to your LANSA Composer server.  This will open a view of the server in the right-hand window pane, allowing you to deploy the completed CurrencyExchangeRate solution from your PC to the server.
  15. 15.  Expand the Integrator item in the tree on the left-hand side, then expand the bindings folder and locate the CurrencyExchangeRate.soap.jar file.  Right-click the file and select Publish File from the popup menu.  Click Yes when prompted to confirm the request.
  16. Expand the properties folder and locate the SOAPAgentService.properties file.  Right-click the file and select Publish Section from the popup menu.  Click Yes when prompted to confirm the request.
  17.  Finally, you need to restart LANSA Integrator on your server in order to use the new solution.  Before you do so, be sure (especially in a production environment) that no jobs are using the LANSA Composer or LANSA Integrator server.  Restarting LANSA Integrator will interrupt running jobs that are using it.

    When you are ready to restart LANSA Integrator, select the server Instance in the right-hand pane, right-click and select Shutdown / Reboot from the popup menu.  Click Yes when prompted to confirm the request.
  18. Close LANSA Integrator Studio and continue with the next tutorial.

Now continue with the following tutorial:
JSM012 - Create a JSM Binding Script Configuration

  • No labels