Setting Up a Thin Client Application Development Environment Using CEWS Transport

The information in this procedure can assist you in setting up your client application using the CEWS transport. This procedure is applicable if you have a heterogeneous brand of application server (for example, IBM WebSphere®) but the versions of the application server software are not the same on the server as on the client (for example, 6.0 on the Content Engine server and 5.1 on the client).

  1. Create and deploy a custom EAR file in which the WAR\WEB-INF\lib folder contains the .jar files listed under "Required for a Content Engine Java API CEWS transport client" in the Required Java Archive (JAR) Files topic.
  2. On the WebSphere administration console, set the EAR and WAR classloader mode to PARENT_LAST. (Classloader will attempt to load classes first from the local classpath.)
  3. Copy the FNSW/CE_API folder structure from the Content Engine server into a folder (such as <drive>:\CE_API) on the client server.
  4. Add the following JVM arguments using the WebSphere administration console under server > Process Definition > Java Virtual Machine > Generic JVM arguments:
    -Dwasp.location=<drive>\\CE_API\\wsi

If you are using the Content Engine Java API, no additional steps are required. However, if you are using the IBM FileNet P8 Compatibility Layer, which is a client-side API that allows you to upgrade and maintain applications written using the 3.5.x Content Java API, then you must perform the following two additional steps:

  1. Modify the WcmApiConfig.properties file with the following entries:

    RemoteServerUrl=cemp:http://ceServer:9080/wsi/FNCEWS40DIME(http://ceserver:8080/wsi/FNCEWS40DIME)
    RemoteServerUploadUrl=cemp:http://ceServer:9080/wsi/FNCEWS40DIME(http://ceserver:8080/wsi/FNCEWS40DIME)
    RemoteServerDownloadUrl=cemp:http://ceServer:9080/wsi/FNCEWS40DIME(http://ceserver:8080/wsi/FNCEWS40DIME)

  2. Modify WcmApiConfig.properties to point jaasConfigurationName to FileNetP8WSI.