User's Guide
Get Adobe Reader |
This chapter describes the installation of a WebLogic Network Gatekeeper in a clustered environment. For a complete and successful installation, all sections and steps below have to be performed in the order they are presented.
Before you start the installation it is recommended that you learn the basics about the Network Gatekeeper by reading the BEA WebLogic Network Gatekeeper Product Description.
The installation instruction covers installation on RedHat Linux Advanced Server 3 and HP-UX Itanium v11.23.
The instructions below describes the steps to be taken for each server in the cluster building up the WebLogic Network Gatekeeper.
The paths to the installation files are described in Installation CD and the directory structure for an installed system is described in Installed system.
Individual files are referred to as filename<version>.type
. For example, a file referred to as jrockit-j2sdk<version>.bin.gz could have the full name jrockit-j2sdk1.4.2_05-linux-ia32.bin.gz
.
The following sections provide installation instructions:
gunzip jrockit-j2sdk<version>.bin.gz
chmod u+x jrockit-j2sdk
<version>.bin
./jrockit-j2sdk
<version>.bin
Follow the instructions below to install MySQL. MySQL should only be installed on two servers in the cluster building up the WebLogic Network Gatekeeper. Normally the servers resides in the Network Layer of the cluster.
gunzip -c <path to installation files>/linux/mysql-<version>.tar.gz | tar xvf -
/usr/local/mysql-<version>/INSTALL-BINARY
Below is an summary of commands to install MySQL, refer to the actual installation instructions for a description of each command.
groupadd mysql
useradd -g mysql mysql
cd /usr/local
ln -s /usr/local/mysql-standard-<version> mysql
cd mysql
scripts/mysql_install_db --user=mysql
chown -R root.
chown -R mysql data
chgrp -R mysql.
bin/mysqld_safe --user=mysql &
<path to installation files>/wng/hpux/joob_<version>.depot
Follow the instructions below to install MySQL. MySQL should only be installed on two servers in the cluster building up the WebLogic Network Gatekeeper. Normally the servers resides in the Network Layer of the cluster.
tar xvf <installation file directory>/wng/hpux/mysql-<version>
/usr/local/mysql-<version>/INSTALL-BINARY
Below is an summary of commands to install MySQL, refer to the actual installation instructions for a description of each command.
groupadd mysql
useradd -g mysql mysql
cd /usr/local
ln -s /usr/local/mysql-<version> mysql
cd mysql
scripts/mysql_install_db --user=mysql
chown -R root.
chown -R mysql data
chgrp -R mysql.
bin/mysqld_safe --user=mysql &
Due to import control restrictions for some countries, the Java Cryptography Extension (JCE) policy files shipped with the Java 2 SDK, Standard Edition and the Java 2 Runtime Environment allow strong but limited cryptography to be used.
An unlimited strength version of these files indicating no restrictions on cryptographic strengths is available on the Java 2 SDK web site for those living in eligible countries.
Note: The version of the JCE Policy files must be correlated with the Java version installed.
slee_install_path
to the path of the SLEE, normally /usr/local/slee
database_install
to the path of the MySQL installation. Ignore if MySQL is not installed on this server.address
IP-address of the server running the first database.port
port number for the database on this server.address
IP-address of the server running the second database.port
port number for the database on this server.directory
to the directory to store the back-up.Note: All servers in a cluster shall have identical values in <SLEE_DB_1>
, <SLEE_DB_2>
and <BACKUP>
There are other configuration options for memory sizes, garbage collections sizes, and CORBA configuration used to tune the system. These parameters are deployment specific and depends on type of server, CPU type and son on. The default values can be used.
/usr/local/slee/bin
chmod u+x *.sh
./SLEEConfig.sh
./postconfig.sh
Depending on the type of server being installed delete the service not relevant for the one being set up.
/usr/local/slee/bin/runAgent.sh
Note: MySQL must be started before the WebLogic Network Gatekeeper is started.
When all servers in the cluster have been installed and configured, the complete installation must be verified using test applications.
This sections describes all the different SLEE services in the installation directory structure.
It explains which files that can be removed, depending on the type of server being installed.
The following notation is used in this section:
The following files are included as default in the directory /usr/local/slee/bin/_autoslee
c_slee_snmp.jar (O. Keep for SNMP support)
d_slee_backup.jar (O. Keep on server running DB)
e_slee_global_counter.jar (NL - M, AL - R)
e_slee_list_matcher.jar (NL - M, AL - R)
e_slee_time.jar (O. Used for time synchronization if not done on OS level.)
g_slee_resource.jar (NL - M, AL - R)
h_slee_statistics.jar (NL - M, AL - R)
i_slee_scsmgr.jar (NL - M, AL - R)
x_embedded_tomcat.jar (NL - O. Keep if local web service is used, for example MM7, AL - M)
The following files are included as default in the directory /usr/local/slee/bin/autosrv
b_charging_resource.jar (NL - O, AL - R)
b_cimd_gms_resource.jar (NL - O, AL - R)
b_db_sp_resource.jar (NL - O, AL - R)
b_eaif_mms_resource.jar (NL - O, AL - R)
b_mlp_ul_resource.jar (NL - O, AL - R)
b_mm7_gms_resource.jar (NL - O, AL - R)
b_mps_ul_resource.jar (NL - O, AL - R)
b_mps_us_resource.jar (NL - O, AL - R)
b_smpp_gms_resource.jar (NL - O, AL - R)
b_smpp_gms_resource_ussd.jar (NL - O, AL - R)
cert_builder.jar (NL - O, AL - R)
c_osa_nichs.jar (NL - O. Keep if call control is supported, AL - R)
d_resource_osa_access.jar (NL - O, AL - R)
e_resource_osa_ul.jar (NL - O, AL - R)
resource_osa_callui.jar (NL - O, AL - R)
resource_osa_cs.jar (NL - O, AL - R)
resource_osa_gcc.jar (NL - O, AL - R)
resource_osa_gui.jar (NL - O, AL - R)
resource_osa_messaging.jar (NL - O, AL - R)
resource_osa_mms.jar (NL - O, AL - R)
resource_osa_mpcc.jar (NL - O, AL - R)
resource_osa_sp.jar (NL - O, AL - R)
resource_osa_us.jar (NL - O, AL - R)
subscription_handler.jar (NL - O, AL - R)
x_espa_access.jar (NL - M, AL - R)
x_espa_call_control.jar (NL - O, AL - R)
x_espa_call_ui.jar (NL - O, AL - R)
x_espa_charging.jar (NL - O, AL - R)
x_espa_messaging.jar (NL - O, AL - R)
x_espa_messaging_ui.jar (NL - O, AL - R)
x_espa_subscriberprofile.jar (NL - O, AL - R)
x_espa_userlocation.jar (NL - O, AL - R)
x_espa_userstatus.jar (NL - O, AL - R)
x_sespa_access.jar (NL - R, AL - M)
x_sespa_callcontrol.jar (NL - R, AL - O)
x_sespa_callui.jar (NL - R, AL - O)
x_sespa_charging.jar (NL - R, AL - O)
x_sespa_messaging.jar (NL - R, AL - O)
x_sespa_messaging_ui.jar (NL - R, AL - O)
x_sespa_subscriberprofile.jar (NL - R, AL - O)
x_sespa_userlocation.jar (NL - R, AL - O)
x_sespa_userstatus.jar (NL - R, AL - O)
The following files are included as default in the directory /usr/local/slee//bin/autowar
mm7_vasp.war (AL - R, NL -Keep if MM7 plug-in is used)
parlayx.war (AL - Keep if Parlay X interface is used, NL -R)
wespa.war (AL - Keep if Extended Web Services interface is used, NL -R)