Setting deployment properties for a runtime environment, WebSphere Adapter for Enterprise Content Management

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 > Enterprise Content Management > 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. From this screen, you can modify the user information for the module.

Ensure that you configure the business object.

To generate artifacts for your module, use the following 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 CMIS 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 CMIS server.
In the Password field, type the password to connect to the CMIS server.
The security properties are not encrypted and stored as plain text.

To use any other method of authenticating to the CMIS 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 adapters in the previous step, specify how you want to set the Connection Properties at run time.

If you manually created and configured a managed connection factory or activation specification on the server or if you have deployed an application that connects to the same CMIS 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:

From the Connection settings list, select Use predefined connection properties.
In the JNDI Lookup Name field, 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

In Connection Properties, 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.

In the Connection field, select the connection protocol from the following options: http or https.
In the Server field, specify the server name or IP address of the CMIS end point.
In the Port number field, select the appropriate port number or enter the port number.
In the Path field, specify the context root.

Specify advanced properties by clicking Advanced. Expand each of the advanced sections to review the properties.

Additional Properties
Figure 2. Additional properties for specifying endpoint URLs

In the Object discovery endpoint URL field, you can execute the query made during RetrieveAll operation. The default content in this field is the CMIS server URL followed by /DiscoveryService.

For example, http://hostname:portnumber/contextroot/DiscoveryService
In the Object service endpoint URL field, you can update the URL for performing ID-based Create, Retrieve, Update, Delete operations on objects in a Content Management Repository. The default content in this field is the CMIS server URL followed by /ObjectService.

For example, http://hostname:portnumber/contextroot/ObjectService
In the Navigation service endpoint URL field, you can update the URL used to traverse the folder hierarchy in a Content Management Repository, and to locate Documents that are checked out. The default content in this field is the CMIS server URL followed by /NavigationService.

For example, http://hostname:portnumber/contextroot/NavigationService
In the Versioning service endpoint URL field, you can update the URL used to navigate or update a Document Version Series. The default value in this field is the CMIS server URL followed by /VersioningService.

For example, http://hostname:portnumber/contextroot/VersioningService
In the Locale field, type the preferred language.
For example, English (en_US).

In the Bidi properties area, select Bidi transformation. Set the ordering schema, text direction, symmetric swapping, character shaping, and numeric shaping properties to control how bidirectional transformation is performed.
Logging and Tracing
Figure 3. Logging and Tracing property

If you have multiple instances of the adapter, set Adapter ID to a value that is unique for this instance.
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.

Processing methods for illegal XML characters
Figure 4. Processing methods for illegal XML characters property

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.
If you select the Do not validate illegal XML characters option, the adapter displays an exception as the Enterprise Content Management server does not support illegal characters.
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.

Click Next.

Results
The Specify the Location Properties window is displayed.

Setting deployment properties and generating the service

Related concepts:

Outbound processing
User authentication

Related tasks:

Setting location properties for artifacts

Related reference:

Managed (J2C) connection factory properties
Resource adapter properties
Connection properties for the wizard