Documentation updates for IBM Content Integrator 8.6

Product Documentation

Abstract

This document summarizes the changes and corrections to the IBM Content Integrator 8.6 documentation.

Content

Tab navigation

Product overview
Installing
Deploying
Configuring access to repositories
Configuring and administering Content Integrator

New APIs in Content Integrator 8.6 (Fix Pack 3)

Security
Developing applications
Configuring viewers
Developing connectors to access custom sources
Troubleshooting and support

The information in this document is newer than in the IBM Content Integrator 8.6 documentation.

Product overview

There are currently no changes or corrections to the product overview information.

Installing

This section contains changes or corrections to the installation information.

Hardware, software, and supported operating system requirements

The system requirements link and URL in this topic point to the wrong web page. The link and URL currently point to:

http://www.ibm.com/support/docview.wss?uid=swg27016282

The link and URL should point to:

http://www.ibm.com/support/docview.wss?rs=86&uid=swg27016931

Deploying

This section contains changes or corrections to the deployment information.

Deploying SOA Web services

Important: The information in this section is specific to IBM Content Integrator Version 8.6. These JAR file problems are fixed in version 8.6 Fix Pack 1.

When you perform step 4, exceptions and a warning can occur. You can ignore the exceptions and warning for the file annogen-0.1.0.jar, but you cannot ignore the exception for the file xalan-2.7.0.jar if you retrieve XSD or version information in your application. Follow the instructions to download the missing files and prevent the exceptions and warnings from occurring again.

Step 4 currently reads:

4. Verify that the IBM Content Integrator SOA Web service is successfully deployed. Open the Axis2 Welcome Page: http://IP_ADDRESS:PORT_NUMBER/vbr_soa

a. Click Validate to ensure a correct Axis2 deployment.

b. Click Services to ensure a correct SOAService deployment.

Step 4 should read:

4. Verify that the IBM Content Integrator SOA Web service is successfully deployed.

a. Open the Axis2 Welcome Page: http://IP_ADDRESS:PORT_NUMBER/vbr_soa

b. Click Validate to ensure a correct Axis2 deployment.

c. Click Services to ensure a correct SOAService deployment.

After you successfully deploy SOA Web services, you will see the following exception on the services listing page (typically, http://IP_address:Port /vbr_soa/services/listServices):

Faulty Services

Path_to_installed_application_node \vbr_soa_war.ear\vbr_soa.war\WEB-INF\ services\version-1.4.1.aar

You will also see the following warning on the happy Axis page (typically, http://IP_address:Port /vbr_soa/axis2-web/HappyAxis.jsp):

Examining Version Service

There was a problem with the Axis2 version service, maybe the service was not available or something has gone wrong. But this does not mean the system is not working! Try to upload some other service and check to see whether it is working.

And you will see the following exception when you try to view the XSD artifacts by using either of these URLs:

http://IP_address:Port /vbr_soa/services/SOAService?xsd=xsd1.xsd
http://IP_address:Port /vbr_soa/services/SOAService?xsd=xsd0.xsd

or when a user clicks the Version link on the SOA services page (typically, http://IP_address:Port / vbr_soa/services/Version?wsdl):

SRVE0260E: The server cannot use the error page specified for your application to handle the Original Exception printed in the following.

Original Exception:

Error message: java.lang.ClassCastException:

org.apache.xalan.processor.TransformerFactoryImpl incompatible with
javax.xml.transform.TransformerFactory

Error Code: 500

Target servlet: AxisServlet

Error Stack:

java.lang.ClassCastException:
org.apache.xalan.processor.TransformerFactoryImpl incompatible with javax.xml.transform.TransformerFactory

At javax.xml.transform.TransformerFactory.newInstance(Unknown Source)

At org.apache.ws.commons.schema.XmlSchema.serialize_internal(XmlSchema.java:453)

At org.apache.ws.commons.schema.XmlSchema.write(XmlSchema.java:426)

At org.apache.axis2.description.AxisService.printXSD(AxisService.java:1256)

At org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:294)

At org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:242)

The exceptions and warnings occur because the files annogen-0.1.0.jar (which is required for the Axis2 version service) and xalan-2.7.0.jar (which is required to retrieve the artifacts) are not included in the class path for the SOA deployment. To prevent the exceptions and the warning, download the JAR files from the Apache website and make them available to SOA web services:

Download the binary distribution for Apache Axis2 Version 1.4.1 from http://axis.apache.org/axis2/java/core/
Extract annogen-0.1.0.jar and xalan-2.7.0.jar from the binary distribution.
Stop the application server instance in which SOA web services are deployed.
Copy the JAR files to WebSphere_installation_directory \profiles\profile_name \installedApps\cell_name \ vbr_soa_war.ear\vbr_soa.war\WEB-INF\lib
Restart the application server instance in which SOA web services are deployed.

Deploying Web Services API (WSAPI) service (deprecated)

Important: The information in this section is specific to IBM Content Integrator Version 8.6. These JAR file problems are fixed in version 8.6 Fix Pack 1.

When you perform step 4, exceptions and a warning can occur. You can ignore the exceptions and warnings for the file annogen-0.1.0.jar , but you cannot ignore the exception for the file xalan-2.7.0.jar if you retrieve XSD or version information in your application. Follow the instructions to download the missing files and prevent the exceptions and warnings from occurring again.

Step 4 currently reads:

4. Verify that the WSAPI service is successfully deployed. Open the Axis2 Welcome Page: http://IP_ADDRESS:PORT_NUMBER/vbr_wsapi

a. Click Validate to ensure a correct Axis2 deployment.

b. Click Services to ensure a correct WebServicesAPI.Endpoint deployment.

Step 4 should read:

4. Verify that the WSAPI service is successfully deployed.

a. Open the Axis2 Welcome Page: http://IP_ADDRESS:PORT_NUMBER/vbr_wsapi

b. Click Validate to ensure a correct Axis2 deployment.

c. Click Services to ensure a correct WebServicesAPI.Endpoint deployment.

After you successfully deploy the WSAPI service, you will see the following exception on the services listing page (typically, http://IP_address:Port /vbr_wsapi/services/listServices):

Faulty Services

Path_to_installed_application_node \vbr_wsapi_war.ear\vbr_wsapi.war\WEB-INF\services\version-1.4.1.aar

You will also see the following warning on the happy Axis page (typically, http://IP_address:Port /vbr_wsapi/axis2-web/HappyAxis.jsp):

And you will see the following exception when you try to view the XSD artifacts by using this URL:

http://IP_address:Port /vbr_wsapi/services/WebServicesAPI.Endpoint? xsd=WebServicesAPI_schema1.xsd

or when a user clicks the Version link on the WSAPI services page (typically, http://IP_address:Port / vbr_wsapi/services/Version?wsdl):

The exceptions and warning occur because the files annogen-0.1.0.jar (which is required for the Axis2 version service) and xalan-2.7.0.jar (which is required to retrieve the artifacts) are not included in the class path for the WSAPI deployment. To prevent the exceptions and the warning, download the JAR files from the Apache web site and make them available to the WSAPI service:

Download the binary distribution for Apache Axis2 Version 1.4.1 from http://axis.apache.org/axis2/java/core/
Extract annogen-0.1.0.jar and xalan-2.7.0.jar from the binary distribution.
Stop the application server instance in which the WSAPI service is deployed.
Copy the JAR files to WebSphere_installation_directory \profiles\profile_name \installedApps\cell_name \ vbr_wsapi_war.ear\vbr_wsapi.war\WEB-INF\lib
Restart the application server instance in which the WSAPI service is deployed.

Deploying SOA Web services on Oracle WebLogic Server

Important: The information in this section is specific to IBM Content Integrator Version 8.6 Fix Pack 4.

Deploying VBR SOA on Weblogic 12c

Follow these steps if your Weblogic server 12c.

Tag	VALUE
prefer-web-inf-classes	false
prefer-application-packages	<<no value, it is a complex property>>
package-name	org.apache.axis2

Go to the folder location where you have extracted "vbr_soa.war". Former folder location will be referred to as "<soa-home>" in following steps.
Open and edit 'Weblogic.xml' under "<soa-home>\WEB-INF" using your text editor.
Add following tags with values as follows in the deployment descriptor (weblogic.xml)
Refer the following sample "weblogic.xml" snippet. This is how your vbr_soa.war's 'weblogic.xml' shall look before deployment of "vbr_soa.war" in Weblogic 12c.

<weblogic-web-app>
- <container-descriptor>
  - <prefer-web-inf-classes>false</prefer-web-inf- classes>
    - <prefer-application-packages>
      - <package_name>org.apache.axis2</package_name>
      </prefer-application-packages>
  </container-descriptor>
</weblogic-web-app>

Configuring access to repositories

This section contains changes or corrections to the configuration information for accessing repositories.

Configuring the Documentum connector

The content should be read as the following:

On Windows: Modify the RMIbridge.bat file. Add these lines before
Set VBR_CLASSPATH=%VBR_HOME%\lib\vbr.jar;%VBR_CLASSPATH%:

Set DFC_JAR=C:\\Program Files\\Documentum\\dctm.jar
Set DFC_CONFIG_HOME=C:\\Documentum\\config
Set VBR_CLASSPATH=%VBR_CLASSPATH%:%DFC_JAR%:%DFC_CONFIG_HOME%

On UNIX systems: Modify the RMIbridge.sh file. Add these lines before
Export VBR_ALLJARS=$VBR_HOME\lib\vbr.jar;$VBR_CLASSPATH:

DFC_JAR=C:\\Program Files\\Documentum\\dctm.jar
export DFC_JAR
DFC_CONFIG_HOME=C:\\Documentum\\config
export DFC_CONFIG_HOME
VBR_CLASSPATH=$VBR_CLASSPATH:$DFC_JAR:$DFC_CONFIG_HOME
export VBR_CLASSPATH

And

Both set VBR_CLASSPATH command lines in the Windows-specific instructions contain a typographical error. Instead of a colon (:), these lines should contain a semi-colon (;). The lines with the error currently read:

Set VBR_CLASSPATH=%VBR_CLASSPATH%:%DFC_JAR%:%DFC_CONFIG_HOME%

These lines should read:

Set VBR_CLASSPATH=%VBR_CLASSPATH%;%DFC_JAR%:%DFC_CONFIG_HOME%

Configuring the Content Manager Enterprise Edition 8.7 connector

The content should be read as the following:

1.   First set below things in config.bat file :

set VBR_HOME=C:\Users\Administrator\IBM/ContentIntegrator
SET PATH=%JAVA_HOME%\bin;%PATH%;%VBR_HOME%\combridge\bin
set VBR_CLASSPATH=%VBR_HOME%\docs\examples\java
set VBR_CLASSPATH=%VBR_CLASSPATH%;%VBR_HOME%\docs\examples\wsapi\java
set VBR_CLASSPATH=%VBR_CLASSPATH%;%WAS_HOME%\Properties

rem Set the VBR_CLASSPATH environment variable
set lcp=
for %%i in ("%VBR_HOME%\lib\*.jar") do call "%VBR_HOME%\bin\lcp.bat" "%%i"
for %%i in ("%VBR_HOME%\lib\*.zip") do call "%VBR_HOME%\bin\lcp.bat" "%%i"
set lcp=%lcp:"=%
set VBR_CLASSPATH=%VBR_CLASSPATH%;%lcp%

set VBR_CLASSPATH=%VBR_HOME%\lib\vbr.jar;%VBR_CLASSPATH%

2.   Modify the RMIbridge.bat file. Add these lines :

set II4C_HOME=C:\Program Files\IBM\db2cmv8
set JAVA_HOME=%II4C_HOME%\java\jre
set PATH=%JAVA_HOME%\bin;%PATH%

set VBR_ALLJARS=%VBR_CLASSPATH%;%II4C_HOME%\lib\cmbicmsdk81.jar
set VBR_ALLJARS=%II4C_HOME%\lib\cmbview81.jar;%VBR_ALLJARS%
set VBR_ALLJARS=%II4C_HOME%\lib\cmb81.jar;%VBR_ALLJARS%
set VBR_ALLJARS=%II4C_HOME%\lib\db2jcc.jar;%II4C_HOME%\lib\db2jcc4.jar;%VBR_ALLJARS%
set VBR_ALLJARS=%II4C_HOME%\lib\db2jcc_license_cu.jar;%VBR_ALLJARS%
set VBR_ALLJARS=%II4C_HOME%\lib\db2jcc_license_cisuz.jar;%VBR_ALLJARS%
set VBR_ALLJARS=%II4C_HOME%\cmgmt;%VBR_ALLJARS%

set VBR_ALLJARS=%VBR_ALLJARS%;%VBR_HOME%\ejb\vbr_view_services.jar
set VBR_ALLJARS=%VBR_ALLJARS%;%VBR_HOME%\ejb\vbr_contentmgr.jar

set lcp=
for %%i in ("%VBR_HOME%\opt\*.jar") do call "%VBR_HOME%\bin\lcp.bat" "%%i"
set lcp=%lcp:"=%
set VBR_ALLJARS=%VBR_ALLJARS%;%lcp%;%VBR_HOME%\opt

3. Locate the cmbicmsrvs.ini file. This file is typically under the

II4C_ROOT\cmgmt\connectorsdirectory, where II4C_ROOT is the IBM Information Integrator for Content installation directory. Set the values for the host name, port, and database
as per below example .

ICMSERVER=icmnlsdb
ICMSERVERREPTYPE=DB2
ICMSCHEMA=icmadmin
ICMSSO=FALSE
ICMDBAUTH=SERVER
ICMREMOTE=TRUE
ICMHOSTNAME=myhostname.ibm.com
ICMPORT=50000
ICMREMOTEDB=icmnlsdb

Configuring and administering Content Integrator

This section contains changes or corrections to the configuration and administration information for Content Integrator.

Deploying the common viewer applet as a stand-alone Web application in WebSphere Application Server, Version 7.0

Step 15 is incomplete. It currently reads:

15. Click New. Enter vbrLibrary in the Name field, and enter the full path of the vbr.jar file in the classpath field. This path should be located in the ICI_HOME\lib directory, for example: C:\Program Files\IBM\ContentIntegrator\lib\vbr.jar

This step should read:

Important: In addition, be sure to add the appropriate ejb\vbr_*.jar file for any connector that is used with the viewer, for example, vbr_contentmgr.jar for the IBM Content Manager connector.

View services do not work correctly on Linux

Important: The information in this section supersedes the topic in the information center.

If view services do not work correctly on a Linux system, the problem is typically due to missing dependencies. Symptoms include blank graphics in documents and errors like the following one:

class com.venetica.vbr.client.ConversionException

COEV5040E: An error occurred while converting /Temp/128ac0cd087e35fb180545acf6b25699/MyDoc.ppt

To resolve this problem:

1. Navigate to the directory that contains the standard content converter, by default, ICI_HOME/htmlconverter, where ICI_HOME is the Content Integrator installation directory.

2. Determine whether missing dependencies are the problem by entering the following command, which produces a list of dependencies for the specified library:

ldd library_name

Example: To determine whether there are missing dependencies for the libos_xwin shared object, enter:

ldd libos_xwin.so

If your system is missing a compatible library, the output looks like this:

libXm.so.3 => not found

3. If there are missing dependencies, install the necessary libraries.

If the product CDs for your Linux platform do not include the necessary libraries, you can find instructions for downloading a binary RPM at the RPM repository at http://rpmfind.net/linux/RPM.

4. If you installed a necessary library, but the dependency is still not resolved, the problem might be that you have a more recent version of the shared object than expected. To resolve this problem, create a symbolic link from the library that you have to the missing library.

Example: The following command creates a symbolic link from libXm.so.4 to libXm.so.3, which satisfies the OpenMotif library dependency for the standard content converter in Content Integrator:

ln -s /usr/lib/libXm.so.4 /usr/lib/libXm.so.3

New APIs in Content Integrator 8.6 (Fix Pack 3)

Delete Item properties API is added in ICI 8.6 fix pack 3. The details of the new method calls:

Package com.venetica.vbr.client

Interface IContent

- - void deleteItemProperty(): Deletes the selected properties of an item in a repository
  - void deleteAllComplexProperty(): Deletes all the complex properties associated with an item in a repository

Package com.venetica.vbr.client

Class ContentBase

- - void deleteItemProperty(): Deletes the selected properties of an item in a repository
  - void deleteAllComplexProperty(): Deletes all the complex properties associated with an item in a repository

Package com.venetica.vbr.client

Class Property

- - void deleteValue(String value): Deletes the value of this property.
  - void deleteValues(String[] values): Deletes the values of this property.

DeleteItemPropeties.java is also added to Java samples to demonstrate these APIs in action.

Currently, these APIs are supported only for the ICI Content Manager connector.

Security

There are currently no changes or corrections to the security information.

Developing applications

This section contains changes or corrections to the application development information.

Simple search with basic operators

The example word search values in the Full-text search section of this topic are incorrect. These lines currently read:

WORD = 'foosball'

WORD = 'Arena AFL' (is conceptually the same as WORD = 'Arena' AND WORD = 'AFL'

WORD = 'vacation spring summer fall winter'

These lines should read:

WORD = 'foosball'

WORD = 'Arena' AND WORD = 'AFL'

WORD = 'Arena' OR WORD = 'AFL'

com.venetica.vbr.client.Constraints (IBM Content Integrator Integration API)

Beginning in IBM Content Integrator Version 8.6 Fix Pack 2, the return value for the getMin method changed.

The return value is currently documented as:

Returns:
the minimum value that is stored in this object, or Long.MIN_VALUE * if the minimum is not set.

From version 8.6 Fix Pack 2 forward, the return value should be documented as:

Returns:
the minimum value that is stored in this object, or -1 if the minimum value is not set.

Configuring viewers

There are currently no changes or corrections to the viewer's configuration information.

Developing connectors to access custom sources

There are currently no changes or corrections to the connector development information.

Troubleshooting and support

There are currently no changes or corrections to the troubleshooting and support information.

Related Information

IBM Software Product Compatibility Reports

IBM Content Integrator 8.6 documentation

[{"Product":{"code":"SSWLLY","label":"Content Integrator"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.6","Edition":"All Editions","Line of Business":{"code":"LOB45","label":"Automation"}}]

Tips