Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

This section explains:

 Configuring Adeptia Suite to use WSDL4j Parser

This section explains how to configure the Adeptia Suite to use WSDL4j parser. 
 

Steps to configure Adeptia Suite to use WSDL4j parser

  1. On the Adeptia Suite home page, click the Administer tab and then click at the Setup menu. This action will show you all the options of the Setupmenu (see Figure 315).

    Figure 315: Set Up Menu Options

  2. Select the Application Settings option. This action will show you the Application Settings screen (see Figure 316).

    Figure 316: Application Settings

  3. Click the Update System Properties link. This action will show you the Update System Properties page.

  4. Click Services to expand the Services hierarchy (see Figure 317).

    Figure 317: Application Setting Page

  5. Expand Web Service Configuration.

  6. Change the value of the abpm.webservice.consumer.wsdlparser.iswsdl4j property to true (see Figure 318).

    Figure 318: Web Service Configuration Properties

  7. Click the Save button to save the web service configuration settings.

 

 

If you want to re-enable the new parser for WS Consumer activity, EasyWSDL parser, then, simply set the value of theabpm.webservice.consumer.wsdlparser.iswsdl4j property to false.


Creating Web Service Consumer Activity using WSDL4j Parser

This section covers the steps to create Web Service Consumer Activity using wsdl4j parser. Adeptia Suite also supports easy WSDL parser from version 6.0 onwards.
 

Steps to create a Web Service Consumer Activity

  1. On the Adeptia Suite homepage, click the Develop tab.

  2. Go to Configure > Services > Web Services and then click Consumer. This action will show you the Manage Consumer screen (see Figure 319).

    Figure 319: Manage Consumer Page

  3. Click the Create New link. This action will show you the New Web Service Consumer screen.
  4. Enter the name of the new WS Consumer activity in the Name field. Then, enter the description for this activity in the Description textbox.

  5. Check the URI checkbox in the Web Service Definition Location field (see Figure 320).

    Figure 320: Locate WSDL

  6. Select a consumer type from Consumer Type radio button.

     

    Select SOAP, when you want to access any SOAP-based Web Service. 
    To know how to create a Web Service Consumer activity to access any RESTful Web Service, refer to the Creating Web Service Consumer activity for RESTful Web Service section.

  7. Select the location of URI.

    In the URI Location, select:

    • HTTP, if the WSDL file is on a HTTP Site.
    • Local/LAN, if the WSDL file is on a Local/LAN environment.


  8. Click the Browse WSDL button. This action will show you the Upload WSDL File screen (see Figure 321).

     

    If, for the URI Location field, you check the HTTP radio button then skip the steps 8 - 9 and continue from step 10.



    Figure 321: Upload WSDL File

     

  9. Click the Browse button to select the WSDL file. Then click the Upload File button. This action will upload the file and display it in the WSDL File Path (Local/LAN) textbox on the Web Consumer screen (see Figure 322).


    Figure 322: Uploaded WSDL File

  10. Select the Secure checkbox if the path in the WSDL URL field is secured. Then enter the user ID and password in the User ID and Password field respectively.

    If, for the URI Location field, you check the Local/Lan radio button then follow steps 8 - 9 and skip step 10.


  11. Click the Next button. This action will show you the New Web Consumer screen (see Figure 323).

    Figure 323: Select Web Service Operation

  12. Select the name of service from the Service Name dropdown list.
  13. Select a port type from the Port Type dropdown list. A port type can support multiple ports. This selection populates the options in the Ports dropdown list.
  14. Select a port for the port type from the Ports dropdown list.

  15. Select an operation from the Operation(s) dropdown list. This selection will automatically display you the name of the style in the Style Name dropdown list.

    When you select an operation then the Style Name field gets its data automatically. There are two types of styles in this field:

    • Document: When a WS Consumer invokes a document style Web service, the consumer typically sends it an entire document, such as a purchase order, rather than a discrete set of parameters. The Web service accepts the entire document, processes it, and may or may not return a result document. In a document style, the input can be read from context or a stream coming from another activity. Similarly, output can be set to context or the WS Consumer activity can generate it as a stream to other activities. In case the output is set to context then, the WS Consumer activity creates a variable in the context with the name as specified in the Output Parameter Name field. The WS Consumer activity then sets the output into that variable. Additionally, you can use the XSD of the Web Service Consumer activity to create an XML schema.
    • rpc: In rpc style, the WS Consumer invokes a Web Service and sends some parameter values to it. The Web Service then executes few methods using these parameter values and sends back the result. In rpc style, the WSDL4j parser creates a variable in the context with a name same as in the Output Parameter Name field and then the output is set into that variable. This style does not generate a stream.

    In the current example, the Web Service is of doc

  16. Select an operation from the Operation dropdown list.

  17. Click the Next button. This action will show you the Web Service Consumer screen (see Figure 324).

  18. Select a security Policy from the dropdown list if required.

    You may also override the security policy activity that is being called within a consumer activity. For this, there is a context variable,securityPolicy. It is accessible via put-context-var action of a process flow designer. For details, refer to the following sections:

    • Overriding an activity using put-context-var
    • Creating Security Policy for Web Services

    To learn about its Advanced Properties, please refer to the Changing Advanced Properties section.

  19. Click the Save button.

 

 

In case you want to update your existing Web Service Consumer Activity using EasyWSDL parser then please refer to the Updating Existing Web Service Consumer Activity Using EasyWSDL Parser section.

  • No labels