Installation and Configuration

This section describes how to install and use the JSR 309 Connector.

For system requirements and supported platforms, see System Requirements.

Preparing the J2EE Converged Application Server

The JSR 309 Connector has been deployed and tested on OCCAS 5.0. If you are not familiar with OCCAS or how to set it up, refer to the Appendix: JSR 309 Connector Environment Setup for guidance and detailed instructions.

Installing the JSR 309 Connector

Follow this procedure to get the application (WAR file) in an OCCAS environment to correctly load the JSR 309 Connector (dlgmsc.jar).

The JSR 309 Connector supports the new PowerMedia XMS via the MSML protocol. When using this release, the mediaserver.msType=XMS attribute must be set to XMS. This will load the correct connector implementation.

Step 1

Extract the .tgz distribution package for this release which will create a <Release Package>/lib directory.

Note: <Release Package> refers to the .tgz distribution package provided for this release.

Copy the following .jar files from <Release Package>/lib directory to your <Domain Location>/lib directory:

Note: <Domain Location> refers to the domain path as specified during OCCAS installation.

Step 2

Set up the properties file (dlgmscTemplate.properties). In order for applications to work, you must configure IP addresses and ports for the JSR 309 Connector and the PowerMedia XMS.

Follow these steps to set up the properties file:

1. Create a user directory. For example:
   /root/user1
   Note: This is a directory which will be accessible from the OCCAS to JSR 309 Connector configuration files.

2. Copy the dlgmsc-log4j-sample.properties file from <Release Package>/about-log4j to /root/user1.

3. Make a copy of the dlgmscTemplate.properties file which is part of the distribution. Place this file in any directory that is accessible by the OCCAS. For example:
   /root/user1/user1_dlgmsc.properties

4. Edit this properties file according to your needs. Change the IP and port values for the JSR 309 Connector and the PowerMedia XMS to match the following setup:
   # Connector's address information (typically same as the SipServlet container)
   connector.sip.address=xxx.xxx.xxx.xxx
   connector.sip.port=5060
   
   # Media Server's address information
   mediaserver.msType=XMS
   mediaserver.1.sip.address=xxx.xxx.xxx.xxx
   mediaserver.1.sip.port=5060

5. Edit the <Domain Location>/bin/startWebLogic.sh OCCAS startup script. Look for the following line:
   CLASSPATH="${SAVE_CLASSPATH}"
   
   Add the following four lines directly after:
   export DLG_PROPERTY_FILE=/root/user1/user1_dlgmsc.properties
   LOG4J_OPTIONS="-Dlog4j.configuration=file:/root/user1/dlgmsc-log4j-sample.properties"
   XQUERYPATH=/root/Oracle/Middleware/modules/features/weblogic.server.modules.xquery_10.3.3.0.jar
   CLASSPATH="${SAVE_CLASSPATH}:${ORCL_HOME}/server/modules/mscontrol.jar:${ORCL_HOME}/server/lib/jsr309-descriptor-binding.jar:${XQUERYPATH}"

6. Add the following line in OCCAS startup script to enable some of the relevant items and to disable serialization (highlighted in bold):
   ${LOG4J_OPTIONS} -Dlog4j.debug -Dwlss.local.serialization=false
   
   from:
   
   if [ "${WLS_REDIRECT_LOG}" = "" ] ; then
           echo "Starting WLS with line:"
           echo "${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS} ${PROXY_SETTINGS} ${SERVER_CLASS}"
           ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS} ${PROXY_SETTINGS} ${SERVER_CLASS}
   else
           echo "Redirecting output from WLS window to ${WLS_REDIRECT_LOG}"
           ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS} ${PROXY_SETTINGS} ${SERVER_CLASS}  >"${WLS_REDIRECT_LOG}" 2>&1
   fi
   
   to:
   
   if [ "${WLS_REDIRECT_LOG}" = "" ] ; then
           echo "Starting WLS with line:"
           echo "${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME} ${LOG4J_OPTIONS} -Dlog4j.debug -Dwlss.local.serialization=false -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS} ${PROXY_SETTINGS} ${SERVER_CLASS}"
           ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME} ${LOG4J_OPTIONS} -Dlog4j.debug -Dwlss.local.serialization=false -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS} ${PROXY_SETTINGS} ${SERVER_CLASS}
   else
           echo "Redirecting output from WLS window to ${WLS_REDIRECT_LOG}"
           ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME} ${LOG4J_OPTIONS} -Dlog4j.debug -Dwlss.local.serialization=false -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS} ${PROXY_SETTINGS} ${SERVER_CLASS}  >"${WLS_REDIRECT_LOG}" 2>&1
   fi
   
   For more details on disabling serialization, refer to Disabling Serialization.

7. Save the properties file then restart the WebLogic Server.

Configuring Logging

You can configure logging in the log4j.properties file. By default, logging is configured to use INFO level and to output to the console as well as to a log file, dlgmsc.log.