Configuring JiGlue
Beginning with the P8 4.0 release, the Process Engine API uses the Content Engine API for authentication processes.
Note: Access to the Content Engine API using JiGlue is supported only via the Web services transport.
To configure JiGlue, do the following:
- Ensure that the jiglue.dll and jiglue.tlb files (located in the ecm_help\developer_help\process_java_api\Developer Files directory on the P8 Documentation CD or ESD image),and the pe.jar, wcm.jar, pw.jar, pe3pt.jar and peResources.jar have been copied to the same directory.
- Register the jiglue.dll file. At a command line, enter the following:
regsvr32.exe jiglue.dll
- Install the Content Engine API, or copy the \fnsw\CE_API directory and subdirectories located on a Process Engine server. At the minimum, the following files and subdirectory are required:
CE_API\lib\Jace.jar
CE_API\lib\log4j.jar
CE_API\wsi (all files)
-
Copy the following JAAS configuration file for the WSI transport from a Process Engine server to the CE_API\config directory (from the previous step):
\fnsw\bin\jaas.conf.WSI
- Set the classpath for Jiglue using either the classpath environment variable, or by setting a registry key as follows:
- Add the locations for Jace.jar, log4j.jar and wsi\lib\wasp.jar to one of the subkeys of HLM\Software\FileNet\eProcess. For example:
[HKEY_LOCAL_MACHINE\SOFTWARE\FileNet\eProcess\P840CE]
@="C:\\CE_API\\lib\\Jace.jar;C:\\CE_API\\lib\\log4j.jar;C:\\CE_API\\wsi\\lib\wasp.jar"
- Ensure that the pe.jar, pe3pt.jar and peResources.jar are available on the machine and are specified in one of the subkeys of HLM\Software\FileNet\eProcess. This key must follow in sequence the key specified in the previous step (wasp.jar must precede pe3pt.jar in the classpath). For example:
[HKEY_LOCAL_MACHINE\SOFTWARE\FileNet\eProcess\P840PE]
@="C:\\PE_API\\lib\\pe.jar;C:\\PE_API\\lib\\peResources.jar;C:\\PE_API\\lib\pe3pt.jar"
- Create the following registry key:
HLM\Software\FileNet\eProcess\VMOptions
- Create the following subkeys of the registry key specified in the previous step:
jaas
datatype: string
value: -Djava.security.auth.login.config=c:\CE_API\config\\jaas.conf.WSI
wasp
datatype: string
value: -Dwasp.location=c:\CE_API\wsi
For example:
[HKEY_LOCAL_MACHINE\SOFTWARE\FileNet\eProcess\VMOptions]
[HKEY_LOCAL_MACHINE\SOFTWARE\FileNet\eProcess\VMOptions\jaas]
@="-Djava.security.auth.login.config=c:\\CE_API\\config\\jaas.conf.WSI"
[HKEY_LOCAL_MACHINE\SOFTWARE\FileNet\eProcess\VMOptions\wasp]
@="-Dwasp.location=c:\\CE_API\\wsi"
- The Process Engine API for P8 4.0 requires a bootstrap Content Engine URI. Refer to the Javadocs for the VWSession constructors. In summary, do one of the following:
- Use VWSession.setBootstrapCEURI.
-
Use a JVM system property (for example, add a subkey to the VMOptions key similar to the following:
[HKEY_LOCAL_MACHINE\SOFTWARE\FileNet\eProcess\VMOptions\ceURI]
@="-Dfilenet.pe.bootstrap.ceuri=http://ceserver:ceport/wsi/FNCEWS40DIME/"
-
Create a file named WcmApiConfig.properties containing the Content Engine URI, then specify the location of this file in the classpath for JiGlue. The format of the WcmApiConfig.properties entry is as follows:
RemoteServerUrl = cemp:http://CEServer:CEPort/wsi/FNCEWS40DIME/
You could add the location of the WcmApiConfig.properties in either the P840PE or P840CE registry keys used in previous examples. For example, assuming that the WcmApiConfig.properties is created in c:\PE_API, its location can be specified in a P840PE key as:
[HKEY_LOCAL_MACHINE\SOFTWARE\FileNet\eProcess\P840PE]
@="C:\\PE_API\\lib\\pe.jar;C:\\PE_API\\lib\\peResources.jar;C:\\PE_API\\lib\pe3pt.jar;c:\\PE_API"