IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > PeopleSoft Enterprise > Configure the module for deployment > Configure the module for outbound processing

Setting deployment properties and generating the service

After you select and configure business objects for your module, you can use the external service wizard to configure properties that the adapter uses to connect to a specific enterprise information system. The wizard creates a business integration module where all the artifacts and property values are saved.

Ensure that you have configured the business object.

Use the Specify the Service Generation and Deployment Properties and Specify the Location Properties windows of the external service wizard to perform this task. The connection properties in this task are initialized to the values that the wizard used to connect to the enterprise information system. To configure the module to use other values, change the values here.


Procedure

  1. In the Specify the Service Generation and Deployment Properties window, click Edit Operations if you want to review or modify the names, or add a description for the operations to the business objects that you are creating.

    Figure 1. Specify the Service Generation and Deployment Configuration window

    1. In the Edit Operations Name window, select the operation you want to edit, and then click Edit.

    2. In the Add/Edit properties window, type a new operation name and description, and then click Finish.

  2. Specify how you want the adapter to get the user name and password at run time.

    • To use a J2C authentication alias, select Using an existing JAAS alias (recommended) and type the name of the alias in J2C Authentication Data Entry. You can specify an existing authentication alias or create one at any time before deploying the module. The name is case-sensitive and includes the node name.

    • To use managed connection properties, select Using security properties from managed connection factory and type the values in the User name and Password fields.

    • If you want to administer the user name and password from other mechanism, select Other.

  3. In the Deploy connector project field, specify whether to include the adapter files in the module. Select one of the following values:

    • With module for use by single application. When the adapter files are embedded in the module, you can deploy the module to any application server. Use an embedded adapter when you have a single module using the adapter or if multiple modules must run different versions of the adapter. You can use an embedded adapter to upgrade the adapter in a single module without the risk of destabilizing other modules by changing their adapter version.

    • On server for use by multiple applications.

      If you do not include the adapter files in a module, install them as a stand-alone adapter on each application server where you want to run the module. Use a stand-alone adapter when multiple modules can use the same version of the adapter and you want to administer the adapter in a central location. A stand-alone adapter can also reduce the resources required by running a single adapter instance for multiple modules.

  4. If you selected On server for use by multiple applications in the previous step, indicate how you want to specify the connection properties.

    • If you manually created and configured a managed connection factory or activation specification on the server or if you have already deployed an application that connects to the same enterprise information system using the same managed connection factory or activation specification properties, you can reuse the managed connection factory or activation specification by specifying the name of its Java™ Naming and Directory Interface (JNDI) data source. The following figure shows the JNDI Lookup Name field.

      1. In Connection settings, select Use predefined connection properties.

      2. In JNDI Lookup Name, type the name of the JNDI data source for an existing managed connection factory or activation specification.

      3. Click Next to complete this task.

    • If this application is the first that connects to the enterprise information system with a specific user name and password, or if you want to administer the user name and password separately from other applications, select Specify connection properties.

  5. Review and, if necessary, change the values of the required connection properties. The Host name, Port number, and Language code fields are initialized with the connection information that you specified when you started the wizard. You can also connect to an alternate enterprise information system, although the schema names must be the same in both. The format of the connection properties is specific to the enterprise information system. For more information about the properties, see Managed connection factory properties.

  6. Enter the name of the Component interface for testing failed connection.

  7. After clicking Advanced, specify the advanced options.

    Figure 2. Specify the Service Generation and Deployment Configuration window-Advanced

    • Processing methods for illegal XML characters

      1. From the Illegal XML character processing drop-down list, select one of the options that correspond to your requirement:

        • Do not validate illegal XML characters, if you want to work with the default adapter behavior.
        • Throw exception if contents in the BO contains illegal XML characters, if you want to proceed after you get an exception message, and log the illegal XML characters in the trace file, at runtime.
        • Discard all illegal XML characters and related logs, if you want the adapter to discard the illegal XML characters, and log the characters in the trace file, at runtime.

    • Logging and tracing area:

      1. If you have multiple instances of the adapter, set Adapter ID to a value that is unique for this instance. For more information, see Adapter ID (adapterID).

      2. You can select Disguise user data as 'XXX' in log and trace files if you want to prevent sensitive user data from being written to log and trace files. See Disguise user data as "XXX" in log and trace files (hideConfidentialTrace).
    • Run time Connection properties area:

      1. Select Use Invalid Request Fault, if you want the adapter to return an invalid request fault business object if any error occurs during run time. See Use Invalid Request Fault (useInvalidRequestFault).

      2. Select Show error on empty result set, if you want the adapter to generate a RecordNotFoundFault fault when no records are found. See Show error on empty result set (showErrorOnEmptyResultSet).
    • Connection retry settings area:

      1. To specify the number of connection exceptions in the outbound operation, set the Maximum retries in case of system connection failure: to a value greater than or equal to 0. For more information, see Maximum retries in case of system connection failure (connectionRetryLimit).

      2. To specify the time interval between retries if a connection fails, set the Retry interval if connection drops (in milliseconds): to a value in milliseconds. See Retry interval if connection drops(in milliseconds) (connectionRetryInterval).

  8. Click Next. The Specify the Location Properties window is displayed.

  9. In the Specify the Location Properties window, specify the name of the module to create. This module can be new or existing.

    • If the module name is displayed in the Module list, select its name.


      Important: If the module contains an interface or business object with the same name as any that you are now configuring, the original interface or business object in the module is replaced by the new version.

    • Otherwise, in the Specify the Location Properties, create a module:

      1. Click New.

      2. In the Select a Business Integration Project Type window, select Create a module project and click Next.

      3. In the Create a Module window, type a name for the module.

        For example, PeopleSoftOutboundInterface.

      4. If you want the service description files (the .import and .wsdl files) to be in the default folder in the module, leave Use default location selected. If you want to specify a different folder in the module, clear the option and then click Browse to specify a different folder in Location.

      5. If you want the module to be opened automatically in the assembly diagram in IBM Integration Designer when the wizard closes, select Open module assembly diagram. Otherwise, clear this option.

      6. Click Finish to create the module.

  10. Specify the namespace that you want to use for your business objects.

    • If you want the business objects in the module to use the default derived namespace, leave Use default namespace selected.

    • To specify a different namespace, clear the option and type a different value in Namespace.

  11. Optional: Specify the folder within the new module where the service description is saved. In Folder, type the folder name or browse to an existing folder. If you do not specify a folder name, the artifacts (the import, XSD, and WSDL files) are stored in the root folder of the module, that is, the folder with the module name.

  12. In Name, accept the default import name or type a different name.

  13. If you want to save the business objects in a library where they can be used by other modules, select Save business objects to a library and specify the location of the library in Library.

  14. Optional: In Description, type a descriptive comment about the module.

  15. When you are finished setting properties, click Finish.

  16. If the Model Changed window is displayed, click Yes.


Results

The wizard exits. The module is created in the project and artifacts are generated.


What to do next

You might need to use the assembly editor to complete the configuration. Later, you can test or deploy your module.

Configure the module for outbound processing


Previous topic: Configure the selected objects


Related reference:

Configuration properties

Globalization