Previous      Contents      Index      Next
Sun Java System Communications Express 6 2004Q2 Administration Guide

Chapter 5
Deploying Communications Express and Identity Server

This chapter lists the combination of deployment scenarios for Communications Express with Identity Server and the configuration steps to be performed for proper operation.

---

Deploying Communications Express and Identity Server in Web Container Instance

This section provides the configurations to be performed when deploying Communications Express and Identity Server in both SSL and non-SSL modes, on different and same Web container.

Deploying Identity Server and Communications Express in the same Web Container Instance
Other Identity Server and Communications Express Deployment Scenarios

Deploying Identity Server and Communications Express in the same Web Container Instance

In non-SSL Mode

When Identity Server and Communications Express are deployed in the same web container instance in non SSL mode you need to

Remove jss3.jar from <uwc-deployed-path>/WEB-INF/lib

For example, #rm /var/opt/SUNWuwc/WEB-INF/lib/jss3.jar

Remove am_sdk.jar, am_services.jar from <uwc-deployed-path>/WEB-INF/lib

For example,

#rm /var/opt/SUNWuwc/WEB-INF/lib/am_sdk.jar

#rm /var/opt/SUNWuwc/WEB-INF/lib/am_services.jar

Restart the web container for the changes to take effect.
In SSL Mode

When Identity Server and Communications Express are deployed in the same web container instance in SSL mode you need to

Remove jss3.jar from <uwc-deployed-path>/WEB-INF/lib

For example, #rm /var/opt/SUNWuwc/WEB-INF/lib/jss3.jar

Remove am_sdk.jar, am_services.jar from <uwc-deployed-path>/WEB-INF/lib

For example,

#rm /var/opt/SUNWuwc/WEB-INF/lib/am_sdk.jar

#rm /var/opt/SUNWuwc/WEB-INF/lib/am_services.jar

Make sure the following property is set in AMConfig.properties file:

com.iplanet.am.jssproxy.trustAllServerCerts=true

AMConfig.properties is present in <IS-SDK-BASEDIR>/lib

For example, /opt/SUNWam/lib

Restart the web container for the changes to take effect.

Other Identity Server and Communications Express Deployment Scenarios

You need to perform the configuration steps mentioned below for the following deployment scenarios:

When Identity Server and Communications Express are deployed in different web container instance in non- SSL mode
When Identity Server and Communications Express are deployed in different web container instance in SSL mode
When Identity Server and Communications Express are deployed in different web container instance with Identity Server deployed in SSL mode and Communications Express in non-SSL mode
When Identity Server and Communications Express are deployed in different web containers that are running on the same system, in non- SSL mode
When Identity Server and Communications Express are deployed in different web containers on the same system in SSL mode
When Identity Server and Communications Express are deployed in different web containers, with Identity Server deployed in SSL mode and Communications Express in non-SSL mode

Configuration Steps:

Remove jss3.jar from <uwc-deployed-path>/WEB-INF/lib

For example,

#rm /var/opt/SUNWuwc/WEB-INF/lib/jss3.jar

Install and configure IS SDK before proceeding further.
If the web container is Sun Java System Web Server:
Change to <IS-SDK-BASEDIR>/bin directory

For example, /opt/SUNWam/bin

Run amws61config program
If the web container is Sun Java System Application Server:
Change to <IS-SDK-BASEDIR>/bin directory

For example, /opt/SUNWam/bin

Run amas70config program
Make sure the following is present in the web container’s CLASSPATH:

/opt/SUNWam/lib:/opt/SUNWam/locale:/etc/opt/SUNWam/config:/opt/S UNWam/lib/am_logging.jar:/opt/SUNWam/lib/am_sdk.jar:/opt/SUNWam/ lib/am_services.jar:/opt/SUNWam/lib/am_sso_provider.jar:/usr/sha re/lib/mps/secv1/jss3.jar

Note	In the code, /opt/SUNWam/ is considered to be the directory denoting IS SDK install directory. The code is specified in web container’s configuration file.

Make sure the following JVM options are set in web container’s configuration file:
<JVMOPTIONS>-Dcom.iplanet.coreservices.configpath=/opt/SUNWam/config/ums</JVMOPTIONS>
<JVMOPTIONS>-Djava.protocol.handler.pkgs=com.iplanet.services.comm</JVMOPTIONS>

Note	In the code /opt/SUNWam/ is considered to be the directory denoting IS SDK install directory.

In AMConfig.properties file, set the following property:

com.iplanet.am.notification.url=<url-to-access-web-container-of-UWC>/servlet/com.iplanet.services.comm.server.PLLRequestServlet

For example,

com.iplanet.am.notification.url=http://mysystem.siroe.com:85/servlet/com.iplanet.services.comm.server.PLLRequestServlet

The AMConfig.properties file can be found in <IS-SDK-BASEDIR>/lib

For example, /opt/SUNWam/lib

Restart the web container for the changes to take effect.

Previous      Contents      Index      Next

---

Copyright 2004 Sun Microsystems, Inc. All rights reserved.