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 > IBM i > Configure the module for deployment > Configure the module for outbound processing > Calling IBM i programs > Setting deployment environment and generating the service description

Setting deployment properties for runtime environment

The connection properties in this task are initialized to the values that the wizard used to connect to the database. To configure the module to use other values, change values such as User name and Password here.

This task is performed using the Specify the Service Generation and Deployment Properties window of the external service wizard.

To generate artifacts for your module follow this procedure:


Procedure

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

    Figure 1. Service Generation and Deployment Configuration window

  2. Specify how you want the adapter to connect to IBM i system. In the Deployment Properties area, specify how you want the adapter to get the user name and password at runtime environment.

    • 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 the managed connection factory and type the values in the User name and Password fields.

    • To administer the user name and password from other mechanism, click 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: With the adapter files 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 need to run different versions of the adapter. Using an embedded adapter enables you 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 adapters in the previous step, specify how you want to set the connection properties at runtime environment.

    • 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 IBM i 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:

      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.

    • If this is the first application that connects to the database 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. Specify advanced properties by clicking Advanced as shown in the following figure. If the module contains an interface or business object with the same name as any you are now configuring, the original interface or business object in the module is replaced by the new version.

    • Additional properties:

      • To specify the number of times the adapter can attempt to reconnect to the database in case of connection failure, set Maximum retries on connection failure to a value greater than or equal to zero.

        1. If the property value is set to 0, then the adapter does not perform any EIS connection validation and executes the outbound operation.

          If the EIS connection is invalid, the outbound operation fails. Though the subsequent requests get executed successfully if the IBM i system is functional, the current request fails.

        2. If the property value is set to greater than 0, then during each request, the adapter validates that the EIS connection is active/alive.

        3. If the connection is valid, then the operation is completed. If the connection is invalid, the adapter invalidates the current managed connection so that a new managed connection is created (new physical connection). If the connection is created successfully, the outbound operation is completed. Otherwise a ResourceException error is thrown.
      • Set the Time interval between retries if the connection fails (milliseconds) field with the appropriate integer to indicate the time in milliseconds, in between retries. This property is enabled only when the connectionRetryLimit property has a value, greater than 0.

    • Globalization

      Figure 2. CCSID support for PCML and EMD encoding values (for Chinese characters)

      1. In the Connection CCSID field, enter the CCSID used for the connection. You can specify the CCSID either in the PCML or in the EMD. If CCSID is present in both PCML and EMD, the EMD CCSID is recognized as the highest priority for both single byte and double byte character values. If no EMD value is provided, then the PCML CCSID is recognized as the default coded character set identifier.

      2. In the Data CCSID field, enter the CCSID used for the conversion of data (for DBCS graphic fields).

      3. In the Characters Type list, specify if the parameter is single byte or double byte.
    • Process illegal XML character:

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

      • Select Do not validate illegal XML characters, if you want to work with the default adapter behavior.

      • Select 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 character in the trace file, at run time.

      • Select Discard all illegal XML characters and related logs, if you want the adapter to discard the illegal XML character, and log the character in the trace file, at runtime.

      Figure 3. Process Illegal XML character window

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


Results

The Specify the Location Properties window is displayed.

Setting deployment environment and generating the service description