Redirecting to styles/linkit_tomcat.xml...

If page does not load within 5 seconds, click here.

mPower Server: LinkIT Tomcat Platform For mPower applications: LinkIT Describes platform configuration and software installation for LinkIT on the Tomcat Platform. This document assumes you have a working knowledge of Linux or Unix administration, as well as knowledge of Java and Tomcat. Contact your NetSol representative for assistance if needed. General Preparation System Requirements Review the mPower Server hardware and software requirements. You must install and configure all required software before installing the mPower program files. LeasePak Server The mPower server requires an installed and working LeasePak server. Refer to documentation in the LeasePak System Administration Guide for more information. mPower Users To use one of the mPower applications, you must first set up the appropriate user(s) on the LeasePak server. For more information, refer to the mPower Users section of the document LeasePak and mPower Users. To finish setting up the LinkIT (Web Services API) user or ServIT (Web Customer Self Service) users, you will need to install the mPower software (as detailed below) before editing the css_db.xml or web.xml files. mPowerd Daemon on the LeasePak Server You can install the mPower server on its own machine or on the same machine as the LeasePak server. In either case, you must set up the mPowerd daemon on the LeasePak server. For more information about daemons and services, refer to the document LeasePak Server Configuration and Maintenance in the LeasePak System Administration Guide. On the LeasePak server: All OS Platforms: create entry in /etc/services official_service_nameport_number/protocol_name [aliases] [#comment] Create an entry in the /etc/services file using the following format: official_service_name Must be unique for the server. For example, mPowerd_v53a_5356. port_number/protocol_name The port number must be greater than 1023 and unique for the server. By default 5356. The protocol name is tcp. Example: mPowerd_v53a_5356 5356/tcp # mPower v53a mPowerd /opt/msi/v53a Multiple concurrent versions: if you have more than one version of mPower installed on the same server, each installation requires its own entry in /etc/services with a unique service name and port number. Create entry in inetd.conf or xinetd.d HP and Sun: create an entry in the /etc/inetd.conf file. The entry or file consists of one line. Delimit fields with a space or tab. If you need to continue the entry on a second line, end the first line with a backslash (\). Example: mPowerd_v53a_5356 stream tcp nowait root \ /opt/msi/v53a/live/bin/mPowerd mPowerd \ -d /opt/msi/v53a -l /opt/msi/v53a/log/mPowerd.log -f /opt/msi \ /v53a/etc/hostname_v53a_rt.lpkd where hostname is the name of your LeasePak server machine. Linux: create a file service_name in the /etc/xinetd.d directory Create a file in /etc/xinetd.d where service_name is the official service name (official_service_name) from /etc/services. From the above example the name would be mPowerd_v53a_5356. Example: # mPowerd v53a daemon service mPowerd_v53a_5356 { disable = no id = mPowerd_v53a_5356 socket_type = stream user = root server = /opt/msi/v53a/live/bin/mPowerd wait = no protocol = tcp port = 5356 server_args = -d /opt/msi/v53a -l /opt/msi/v53a/log/mPowerd.log -f /opt/msi/v53a/etc/hostname_v53a_rt.lpkd } where hostname is the name of your LeasePak server machine. Java Installation Download Java (J2SE v 1.4.2_xSDK). For Linux (including Red Hat), Microsoft Windows, and Sun Solaris, you can download the software from Sun Microsystem's Java Technology (Sun Developer Network) site (java.sun.com). For HP-UX, you can download the software from HP's Java Technology Software site (www.hp.com/java). Follow either Sun's or HP's instructions for installing the software. No additional configuration is needed. Tomcat Installation and Configuration Download Tomcat 4 (version 4.1.x) from the Apache Tomcat (Apache Jakarta Project) site (jakarta.apache.org/tomcat) and follow the instructions for installing the software. tomcat4.conf If you have a tomcat4.conf (or tomcat.conf) file in your CATALINA_HOME/conf directory (CATALINA_HOME represents the root directory of the Tomcat installation on your machine), you may need to edit it for the following environment variables: JAVA_HOME="java_root_dir" JAVA_OPTS="-Xmx768M" CATALINA_HOME="tomcat_root_dir" JASPER_HOME="tomcat_root_dir" CATALINA_TMPDIR="tomcat_tmpdir" TOMCAT_USER="tomcat_user" SHUTDOWN_WAIT=30 CATALINA_PID=tomcat_pid_file where java_root_dir is the root directory of the Java installation on your machine (for example, /usr/java/j2sdk1.4.2_02). JAVA_OPTS is set to a percentage of the total system memory. In this example, where the server is exclusively an mPower server, JAVA_OPTS is set to 75% of total system memory. System memory is 1 GB, so the variable is set to 768 MB. If you are installing LeasePak and mPower on the same server, adjust the amount accordingly. Contact your NetSol representative for assistance if needed. The variable tomcat_root_dir is the root directory of the Tomcat installation on your machine (for example, /var/tomcat4), tomcat_tmpdir is the temp file directory under the Tomcat root directory (for example, /var/tomcat4/temp), tomcat_user is the name of the Tomcat user, SHUTDOWN_WAIT is set to 30 seconds (the default), and tomcat_pid_file is the file where the system stores the Tomcat process ID (PID) after Tomcat starts (for example, /var/run/tomcat4.pid. If the tomcat4.conf file does not exist, you may need to instead edit the Tomcat startup script in /etc/init.d (file will be either tomcat4 or tomcat) to set values for JAVA_HOME and JAVA_OPTS. Startup and Shutdown Scripts If you install Tomcat directly (for example, using tar instead of the RPM or package installer), you may just have the script files startup.sh and shutdown.sh in your tomcat_home_dir/bin directory (where tomcat_root_dir is the root directory of Tomcat on your machine--for example, /var/tomcat4). In this case, you will need to use export or setenv to set values for JAVA_HOME and JAVA_OPTS before using these scripts. Contact your NetSol representative for assistance if needed. mPower Installation To install the mPower software: Stop Tomcat if it is running. For Linux, if you installed Tomcat using the RPM, use the service tomcat4 stop command. Otherwise, use the shutdown.sh script in the tomcat_root_dir/bin directory. Copy the file mpower-v53a.war to the CATALINA_HOME/webapps directory (CATALINA_HOME represents the root directory of the Tomcat installation on your machine). Execute the following commands: cd CATALINA_HOME/webapps mkdir mpower-v53a cd mpower-v53a $JAVA_HOME/bin/jar -xvf (path to war file)/mpower-v53a.war (where JAVA_HOME represents the root directory of your Java installation). mPower Configuration leasepak.xml Edit the following parameters in leasepak.xml, located in the mpower/WEB-INF/envs directory: leasepak_server leasepak_environment mPowerd_port where leasepak_server is the IP address or name of your LeasePak server, leasepak_environment is the name of the LeasePak environment, and mPowerd_port is the TCP port number for the mPowerd daemon (not the leasepakd daemon). web.xml Edit the web.xml file, located in the mpower/WEB-INF directory. First, find the following element group: LPCODES_UPDATE_INTERVAL value java.lang.String ChannelIT and ServIT users: set the value of LPCODES_UPDATE_INTERVAL to 5 (minutes) or more to specify the interval at which the program updates LeasePak codes (the LPCODES.TXT file). NetSol recommends a minimum of 60 minutes. If you add or change LeasePak codes frequently, you can set this number lower, but no lower than 5 (minutes). LinkIT users: set value to 0 if you are not using ChannelIT or ServIT. By itself, LinkIT does not use this, and setting value to anything other than 0 can create performance issues. Next, find the customization section of the file and edit as needed: apiuid api_username_value java.lang.String apipwd api_password_value java.lang.String docgen_endpoint http://host:port/dxGen-v53a/services/DocGenWsdl java.lang.String smtp_mail_host mail_host.domain.suffix java.lang.String The API username is the account you have designated for use with the mPower server (ChannelIT, LinkIT, or ServIT) and the API password is the LeasePak client string password created for the account. For more information on LeasePak passwords, refer to the document LeasePak and mPower Users. mPower Deployment To deploy the mPower software: Use chown -R owner:group on the mpower directory and all its contents (including subdirectories and contents), where owner:group is the Tomcat user and corresponding group. Start Tomcat. For Linux, if you installed Tomcat using the RPM, use the service tomcat4 start command. Otherwise, use the startup.sh script in the tomcat_root_dir/bin directory. LinkIT Deployment If you are using the LeasePak API, create a Bourne shell script similar to the following, using your directories, host name, and port number: #! /bin/sh # this is the web service you are going to deploy DEPLOYFILE=$1 # the name of the contextroot SERVICE_NAME=mpower-v53a # the directory you created SERVICE_DIR=mpower-v53a # the name of the host HOST=http://host.domain.suffix # the port that the service is on; default install is 8080 PORT=port_number #tomcat4 INSTALL_BASE TOMCAT_BASE=tomcat_root_dir # base path to java home JAVA_HOME=java_root_dir # mpower base is the location of the actual service on the filesystem MPOWER_BASE=$TOMCAT_HOME/webapps/$SERVICE_DIR # mpower libs is the location within mpower_base of the api required libraries MPOWER_LIBS=$MPOWER_BASE/WEB-INF/lib # this should not change CLASSPATH=$JAVA_HOME/lib/tools.jar for APIFILE in $MPOWER_LIBS/*.jar ; do CLASSPATH=$CLASSPATH:$APIFILE done $JAVA_HOME/bin/java -classpath "$CLASSPATH" org.apache.axis.client.AdminClient -l$HOST:$PORT/$SERVICE_NAME/services/AdminService $DEPLOYFILE where host.domain.suffix is the URL or IP of your mPower host, port_number is the port for Tomcat, tomcat_root_dir is the root directory of the Tomcat installation on your machine, and java_root_dir is the root directory of Java. Name the script mpower_ws.sh and save it to your mPower WEB-INF/config directory. Then cd to your WEB-INF/config directory and run the script for each service you wish to deploy. For example: mpower_ws.sh LPClient/deploy.wsdd mpower_ws.sh LPApplication/deploy.wsdd mpower_ws.sh LPAsset/deploy.wsdd etc. You should only have to do this once, unless additional methods are added to a service. Contact your NetSol representative for more information. LeasePakTM 5.3a mPower Documentation © 2005 by NetSol Technologies Inc. All rights reserved. The information contained in this document is the property of NetSol Technologies Inc. Use of the information contained herein is restricted. Conditions of use are subject to change without notice. NetSol Technologies Inc. assumes no liability for any inaccuracy that may appear in this document; the contents of this document do not constitute a promise or warranty. The software described in this document is furnished under license and may be used or copied only in accordance with the terms of said license. Unauthorized use, alteration, or reproduction of this document without the written consent of NetSol Technologies Inc. is prohibited.