Configuring a service for outbound operations

The configuration process is done using the enterprise service discovery wizard in WebSphere® Integration Developer.

Why and when to perform this task

As you complete the process you will enter all the information necessary to configure the adapter for the first time. The output from the enterprise service discovery wizard is saved to a business integration module, which contains the business objects, the import file (which describes outbound processing, as defined by the ActivationSpecification), the export file (which describes inbound event processing, as defined by the InteractionSpecification), and the Web Services Description Language (WSDL) file.
Important: During deployment, if you specify J2C activation specification properties when you initially configure the service, those property settings will remain in place (in other words, you cannot update the properties later, after you install the application, via the WebSphere Process Server administrative console - the properties can still be updated, but the adapter will not recognize the updated values if those properties are already set during deployment). If, for any reason, you want to set the J2C activation specification properties after installing the application via the administrative console, then you should refrain from setting them during deployment. Note that J2C connection factory properties can be set during deployment and then updated via the administrative console after you install the application.

Steps for this task

  1. From the WebSphere Integration Developer window, switch to the Business Integration perspective by selecting Window > Open Perspective > Other from the menu bar. All perspectives are displayed. Select Business Integration perspective in WebSphere Integration Developer.
  2. In the Business Integration Perspective of WebSphere Integration Developer, right-click the frame and from the pop-up menu, select New > Enterprise Service Discovery. The Select an Enterprise Service Resource Adapter window is displayed.
  3. Select the IBM WebSphere Adapter for Flat Files (version 6.0.0) from the ’CWYFF_FlatFile’ Connector Project and click Next. The Configure Settings for Discovery Agent window is displayed.
  4. In the Configure Settings for Discovery Agent window, as illustrated in the graphic below, set the connection properties by selecting Outbound for the ServiceType. Outbound is the default ServiceType.

    In the Configure Settings for Discovery Agent window, select Outbound for the ServiceType.

    The Configure Settings for Discovery Agent window

  5. (Optional) To enable BiDi support, select the BiDi Transformation check box in the Configure Settings for Discovery Agent window and select the appropriate BiDi format.
  6. At the bottom of the Discovery Agent Initialize Properties window, click the Show Advanced button. You can set logging and tracing levels here. Click Next.
  7. In the Find and Discover Enterprise Services window, click the Run Query button to display the meta-data tree of the Flat Files adapter.
  8. Under Objects Discovered, select the Inbound root node of the meta-data tree. As illustrated in the graphic below, the objects that can be selected for import are displayed in the Objects Discovered box. Highlight the object you would like to import, then click the Add Selected button to add the objects to the Objects to be imported box. Click Next.
    Note: To remove objects from the Objects Discovered box, highlight the object that you would like to remove and click the Remove Selected button.
    In the Objects Discovered box, you can select the objects to be imported.

    The Find and Discover Enterprise Services window

  9. In the Configure Objects window, specify the properties for the objects that will be imported by the discovery agent. As illustrated in the graphic below, for the BO Location property, specify the folder name within the Business Integration module where the .xsd file should be generated. Click Next.

    The supported operations for Outbound include:

    • Create
    • Append
    • Retrieve
    • Delete
    • Overwrite
    • Exists
    • List

    In the Configure Objects window, specify the BO Location property.

    The Configure Objects window

  10. In the Generate Artifacts window, do the following:
    1. Specify the module name where the SCA artifacts (business objects, their properties, import file, export file, and WSDL) should be saved, and then click New to create a new business integration module.

      The New Module window is displayed.

    2. In the New Module window, enter the Module name and click Finish.
    3. In the Generate Artifacts window, enter the folder name.
    4. In the Generate Artifacts window, select "Use discovered connection properties", enter the JNDI Lookup Name and click Next.
    5. In the Generate Artifacts window, specify the Flat Files ManagedConnectionFactory properties.
      Note: Properties marked with an asterisk (*) are required.
    6. In the Generate Artifacts window, specify the ResourceAdapter properties. You can also set logging and tracing files sizes and file name here as well.
      Note: Properties marked with an asterisk (*) are required.
    7. (Optional) Enter the BiDi properties.
      Note: Clear theTurn BiDi Off check box, otherwise BiDi support will not be invoked.
  11. When you are finished entering property values, click Finish.

What to do next

Now, you can use WebSphere Integration Developer to generate reference bindings for the SCA component that the enterprise service discovery wizard creates.

Related tasks
Enabling logging
Enabling tracing
Configuring properties
Related reference
J2C connection factory properties
Resource adapter properties

Terms of use |

Last updated: Sun Mar 12 11:47:10 2006

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)