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).
-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:
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)
jaasConfigurationNam
e to FileNetP8WSI.