Configuring IBM Content Manager OnDemand

Configure the main settings of the component.

The component configuration window contains the following settings:

Option Description
Activate Activate the component according to a condition. For more information about conditions, see Conditional Activation. This option is enabled only in the eConnector component.
Pass through

Set this option to Yes to pass the original document to subsequent components in the workflow. If this option is not set to No, the component does not pass the input documents to the subsequent components in the chain.

You can use conditions in this field. For more information about conditions, see Conditional Activation.
If you enter an invalid condition into Pass through box, the activation is Yes by default.
This option is enabled only in the eConnector component.
General Use this group to specify the import file settings.
Codepage Specify the codepage value for your IBM Content Manager OnDemand system/application.
Application/Filename Configure the application group and application name accordingly. By default, this text box contains the value:
IBM.NSI.DEFAULTAPPGRP.DEFAULTAPP

To configure another application group or application name, just replace the relevant parts of the string (between the '.') as required by your application on the IBM Content Manager OnDemand server side. The entered value will be used for building names of three import files. Each file name is followed by a date stamp .<YYMMDD> and a time stamp .<HHMMSS> in which leading zeroes are trimmed. The three generated files have the following extensions:

  • .ARD.out — A file containing the input file content,
  • .ARD.ind — A file containing the meta-data (fields, codepage, group file name, comment, and so on.)
  • .ARD — An empty file that is generated to inform the IBM Content Manager OnDemand service that the two above-mentioned files are already copied\moved to the "shared" folder and are ready to be imported to the IBM Content Manager OnDemand storage.

For example, the following 3 files may be generated:

  • IBM.NSI.DEFAULTAPPGRP.DEFAULTAPP.201097.122559.ARD.out
  • IBM.NSI.DEFAULTAPPGRP.DEFAULTAPP.201097.122559.ARD.ind
  • IBM.NSI.DEFAULTAPPGRP.DEFAULTAPP.201097.122559.ARD
File output path Specify the shared folder to which the import files will be written. IBM Content Manager OnDemand system can pick up the import files here. You can specify folder path manually or click to open the Browse for Folder dialog box that allows selection of an existing folder as well as creation of a new one.

Make sure that the Workflow Server logon (user) has sufficient rights to access this folder at service run time.

The specified directory must exist (it will not be created at run time).

Remote path This path represents the incoming document import path from the IBM Content Manager OnDemand server perspective.
This entry, together with the file name, represents the GROUP_FILENAME entry in the import file. The path must end with a directory separator character (\ or / depending on your back-end system), for example: /AutoStore/scans/.
Backup path Specify a back-up directory. Import files will be moved to this directory, should a problem occur. Example: The network share - specified in the Fileoutput path setting might not be available.

You can specify back-up path manually or click to open the Browse for Folder dialog box that allows selection of an existing folder as well as creation of a new one.

The specified directory will be created at run time if does not exist yet.
Fields Specify the fields (meta-data) that you would like to import into IBM Content Manager OnDemand along with your documents.
Make sure these field names correspond to your fields in the IBM Content Manager OnDemand application.
Enter the field names (as created in your IBM Content Manager OnDemand application) on the left side (OnDemand Field Name). Then select the right side (Value) and enter your desired value here. You can of course drag & drop RRTs for the values instead of entering them manually.
We strongly advise that only an IBM Content Manager OnDemand administrator should attempt to configure the component (due to the specific required knowledge on the IBM Content Manager OnDemand system side).