The IPSMGW Element Manager module is distributed as a Rhino Element Manager (REM) plugin.
The IPSMGW Element Manager module should be installed if the REM instance is only used to provision Sentinel-IPSMGW. If REM will be used to provision both Sentinel-VoLTE and Sentinel-IPSMGW installations then only the Sentinel VoLTE provisioning module should be installed. The Sentinel VoLTE provisioning module is capable of provisioning both Sentinel-IPSMGW and Sentinel-VoLTE installations. See Installing the Sentinel VoLTE Provisioning Module. |
It requires a standalone distribution of REM 1.5.0.4 or later. REM can be installed with Jetty or Apache Tomcat. For IPSMGW, the Apache Tomcat method is required.
You’ll need these files to install the IPSMGW Element Manager module:
-
apache-tomcat-<version>.zip
-
rhino-element-manager-<version>.zip
-
ipsmgw-element-manager-<version>.em.jar
Below are the procedures to:
Set up Tomcat
To set up Apache Tomcat for the IPSMGW Element Manager module:
1 |
Follow the instructions for running REM on Apache Tomcat in the REM Guide. |
---|---|
2 |
Create the cd apache-tomcat-<version> mkdir -p rem_home/plugins |
Install the REM plugin
To install the REM plugin for the IPSMGW Element Manager Module:
1 |
Copy cd apache-tomcat-<version> cp /full/path/to/ipsmgw-element-manager-<version>.em.jar rem_home/plugins/ |
---|
Customize plugin logging
1 |
Unzip cd apache-tomcat-<version> mkdir rem-tmp cd rem-tmp unzip ../webapps/rem.war WEB-INF/classes/log4j.properties |
---|---|
2 |
Edit log4j.rootLogger=INFO, FILE, CONSOLE log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout log4j.appender.CONSOLE.layout.ConversionPattern=%d{ABSOLUTE} %-5p <%t> [%c] %m%n log4j.appender.FILE=org.apache.log4j.FileAppender log4j.appender.FILE.File=${rem.home}/rem.log log4j.appender.FILE.layout=org.apache.log4j.PatternLayout log4j.appender.FILE.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p <%t> [%c] %m%n log4j.logger.rem=INFO log4j.logger.openjpa=INFO log4j.logger.org.apache.wink=INFO log4j.logger.sentinel.audit=INFO, AUDIT log4j.additivity.sentinel.audit=false log4j.appender.AUDIT=org.apache.log4j.FileAppender log4j.appender.AUDIT.File=${rem.home}/sentinel-audit.log log4j.appender.AUDIT.layout=org.apache.log4j.PatternLayout log4j.appender.AUDIT.layout.ConversionPattern="%d{yyyy-MM-dd HH:mm:ss,SSS}", "%c{1}", %m%n |
3 |
Replace zip ../webapps/rem.war WEB-INF/classes/log4j.properties |
4 |
Remove temporary files: cd .. rm -rf rem-tmp |
Import Rhino trust certificate
This can also be done using the REM web UI.
1 |
Import a Rhino Trust Certificate into REM: "${JAVA_HOME}/bin/keytool" -importcert -file ${RHINO_HOME}/rhino-trust.cert -keystore "${TOMCAT_HOME}/rem_home/rhino-ems.ks" -storepass changeit -noprompt |
---|
Security considerations
Below are recommendations for securely running the IPSMGW Element Manager Module.
Use https
Be aware that the IPSMGW Element Manager machine API uses HTTP BASIC authentication. This passes the username and password with every request.
To prevent your credentials going over the network unencrypted, run REM over https.
Set up SSL
See the Tomcat 7 - SSL How-To docs for help setting up SSL in Apache Tomcat 7.