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 > Lotus Domino > Configure the module for deployment > Configure the module for outbound processing > Setting deployment properties and generating the service
Setting deployment properties for a runtime environment
The connection properties 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.
Ensure that you have configured the business object.
To generate artifacts for your module follow this procedure:
Procedure
- 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 that you are creating.
- In Deployment Properties, specify how you want the adapter to connect to the Lotus Domino server by selecting any one of these authentication methods.
- To use a J2C authentication alias, click Using an existing JAAS alias (recommended) and type the name of the alias in the J2C authentication data entry field. You can either 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 the security properties from the managed connection properties, click Using security properties from the managed
connection factory and enter the following information:
- In the User name field, type the user name to connect to the Domino server.
- In the Password field, type the password to connect to the Domino server.
The security properties are not encrypted and stored as plain text.
- To use any other method of authenticating to the Domino server, click Other.
- 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.
- If you selected On server for use by multiple applications in the previous
step, specify how you want to set the connection properties at runtime.
- 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 Lotus Domino server 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:
- In Connection properties, select Use predefined connection properties.
- In JNDI Lookup Name, type the name of the JNDI data source for an existing managed connection factory or activation specification.
- Click Next.
- If this application is the first one 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.
Figure 1. Specify the service generation and deployment properties window
- 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 Lotus Domino server 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:
- Optional: Review and if necessary, change the values of the required connection properties. The fields are initialized
with the connection information you specified when you started the wizard.
- Connection properties
- In the Host name field, type the host name or IP address of the Lotus Domino server.
- In the DIIOP port number field, type the port number of the Lotus Domino server. The default DIIOP port number is 63148.
- Connection properties
- Click Advanced.
Expand the advanced sections to review and specify the following options:
- Processing methods for illegal XML characters
- 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.
Figure 2. Processing methods for illegal XML characters
- From the Illegal XML character processing drop-down
list, select one of the options that correspond to your requirement:
- Additional configuration
- To specify support for business faults, select one of the choices
from the Support for business faults during runtime list.
- To enable fault handling only for the business faults, accept the default setting Only business faults (1).
- To specify fault handling support for both business and WebSphere Adapter for Lotus Domino faults, select the Business faults and Lotus Domino faults (2) option from the list.
- To completely disable fault handling support, select the No fault handling and log the errors as exception (0) option from the list. See Set business faults behavior during run time.
- To specify the number of connection exceptions during the outbound operation, set Maximum number of retries in case of system connection failure to a value greater than or equal to 0. See Maximum retries on connection failure.
- To specify the time interval between attempts to connect to the Lotus Domino server if a connection fails, set Connection retry interval to a value in milliseconds. See Retry interval if connection fails (in milliseconds) entities.
- To specify support for business faults, select one of the choices
from the Support for business faults during runtime list.
- Logging and tracing
- If you have multiple instances of the adapter, set Adapter ID to a value that is unique for this instance. See Adapter ID.
- You can select the Disguise user data as 'XXX' in log and trace files check box to prevent sensitive user data from being written to log and trace files. See Disguise user data as "XXX" in log and trace files.
- Processing methods for illegal XML characters
- Click Next.
Results
The Specify the Location Properties window is displayed.
Setting deployment properties and generating the service
Related concepts:
Related tasks:
Setting location properties for artifacts
Related reference:
Managed (J2C) connection factory properties
Interaction specification properties