Skip navigation.

eDocs Home > BEA WebLogic Network Gatekeeper 1.0 Documentation > User's Guide > Installation

User's Guide

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents View as PDF  
Get
Adobe Reader

Installation

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:

 

Installation on Linux

Login

  1. Log in to the target server as root. All commands described in this section assumes that you log in as root user
  2. Verify that the correct OS patches are installed. Refer to the release notes for a description of necessary patches.

Extract the binaries for Linux

  1. Copy from the CD or the download directory, the file wng_linux.zip to the local file system.
  2. Extract the installation binaries by issuing the command:
    unzip wng_linux.zip
  3. Enter the password obtained from the BEA eLicense system.
  4. The installation files are extracted to the local file system in the subdirectory ./linux

Install the JRockit SDK

  1. Change directory to <path to installation files>/linux
  2. Decompress the files by issuing the command:
    3. gunzip jrockit-j2sdk<version>.bin.gz
  3. Make the file properties binary and executable by issuing the command: 
    4. chmod u+x jrockit-j2sdk<version>.bin
  4. Install the JDK by issuing the command:
    5. ./jrockit-j2sdk<version>.bin
  5. Follow the commands as prompted.

Configure the JVM

  1. Define the environment variable JAVA_HOME to the newly installed JDK:
    2. JAVA_HOME=<Java installation path>/j2sdk<version>
  2. Append JAVA_HOME first in the path:
    3. PATH=$JAVA_HOME/bin:$PATH
  3. Make sure the correct JVM is used. Issue the command:
    4. java -version

    The output should be (may differ slightly depending on version):

    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04)
    BEA WebLogic JRockit(TM) 1.4.2_05 JVM R24.4.0-1 (build ari-38120-20041118-1131-linux-ia32, Native Threads, GC strategy: parallel)

Install database

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.

  1. Change directory to /usr/local/
  2. Unpack the installation files for MySQL by issuing the command:
    3. gunzip -c <path to installation files>/linux/mysql-<version>.tar.gz | tar xvf -
  3. Follow the MySQL installation instruction. The instructions are found in
    4. /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 &

Unpack WebLogic Network Gatekeeper software

  1. Change directory to /usr/local
  2. Unpack the software by issuing the command:
    3. gunzip -c <path to installation files>/linux/wng_linux_i386.tar.gz | tar xvf -
  3. Continue with Installation of Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files.

 

Installation on HP-UX

Login

  1. Log in to the target server as root. All commands described in this section assumes that you log in as root user
  2. Verify that the correct OS patches are installed. Refer to the release notes for a description of necessary patches.

Extract the binaries for HP-UX

  1. Copy from the CD or the download directory, the file wng_linux.zip to the local file system.
  2. Extract the installation binaries by issuing the command:
    crypt < wng_hpux.tar.crypt | tar xvf -
  3. Enter the password obtained from the BEA eLicense system..
  4. The installation files are extracted to the local file system in the subdirectory ./hpux

Install patches

  1. Use swinstall to install Java-out-of the-box. The depot file is named
    <path to installation files>/wng/hpux/joob_<version>.depot
  2. Untar the OS patches in the file
    <path to installation files>/wng/hpux/patches/hpux_<version>.tar
  3. Create depots from the files in the previously un-tared files by executing the script./create_depot_hp-ux_11
  4. Use swinstall to install the created depot.

Install the Java SDK

  1. Install the JDK by issuing the command:
    2. swinstall -s <path to installation files>/wng/hpux/sdk<version>.depot\*

Configure the JVM

  1. Define the environment variable:
    2. JAVA_HOME=/opt/java1.4
  2. Append JAVAHOME first in the PATH
    3. PATH=$JAVA_HOME/bin:$PATH
  3. Make sure the correct JVM is used. Issue the command:
    4. java -version

    The output should be (may differ slightly depending on version):

    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2.03-040401-16:07)
    Java HotSpot(TM) Server VM (build 1.4.2 noubar:06.01.04-17:39 PA2.0 (aCC_AP), mixed mode)

Install database

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.

  1. Change directory to /usr/local
  2. Unpack the installation files for MySQL by issuing the command:
    3. tar xvf <installation file directory>/wng/hpux/mysql-<version>
  3. Follow the MySQL installation instruction. The instructions are found in
    4. /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 &

Unpack WebLogic Network Gatekeeper software

  1. Change directory to /usr/local
  2. Unpack the software by issuing the command:
    3. tar xvf <path to installation files>/wng/hpux/wng_hpux_ia64.tar

 

Installation of Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files

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.

  1. Download Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. The files can be found at the download page for the J2SE used under the heading Other Downloads.

    2. Note: The version of the JCE Policy files must be correlated with the Java version installed.

  2. Replace the local_policy.jar and US_export_policy.jar files in the directory:

    3. Linux: <path to JRockit>/j2sdk<version>/jre/lib/security

    HP-UX: /opt/java1.4<version>/jre/lib/security

    with the files included in the downloaded zip file.

 

Configure WebLogic Network Gatekeeper software

  1. Edit the file <installation path>/bin/slee_properties.xml

    2. Modify in the <SLEE_PROPERTIES> tag:

    Modify in the <SLEE_HOST> tag:

    Modify in the <SLEE_PATH> tag:

    Modify in the <SLEE_DB_1> tag:

    Modify in the <SLEE_DB_2> tag:

    Modify in the <BACKUP> tag:

    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.

  2. Change directory to the installation directory of the WebLogic Network Gatekeeper: /usr/local/slee/bin
  3. Make sure all scripts are executable by issuing the command:
    4. chmod u+x *.sh
  4. Create start-up scripts by issuing the command:
    5. ./SLEEConfig.sh
  5. Finalize the configuration by issuing the command:
    6. ./postconfig.sh

    This command sets up database tables etc.

 

Delete unused services

Depending on the type of server being installed delete the service not relevant for the one being set up.

  1. See SLEE Services for all list of services and delete the unused accordingly.

 

Start the WebLogic Network Gatekeeper supervision process

  1. Change directory to the installation directory: /usr/local/slee/bin
  2. .Start the WebLogic Network Gatekeeper supervision process by issuing the command:
    3. ./runAgent.sh &

 

Start Network Gatekeeper Management Tool

  1. Follow the instructions in Starting an Network Gatekeeper Management Tool and adding a SLEE to start to configure the individual SLEEs in the WebLogic Network Gatekeeper.

 

Configure the WebLogic Network Gatekeeper

  1. It is recommended to autostart MySQL at reboot. Refer to the instructions for MySQL and the operating system.
  2. It is recommended to autostart the WebLogic Network Gatekeeper at reboot. Refer to the instructions for the operating system. The script to be autostarted is /usr/local/slee/bin/runAgent.sh

    3. Note: MySQL must be started before the WebLogic Network Gatekeeper is started.

  3. Setup backup procedures as described in System Backup and Restoration.
  4. Create administrative accounts as described in User Administration.
  5. Configure relevant network protocol plug-in as described in Network plug-ins.
  6. Configure Web Services ports as described in Application Connection - Web Services.
  7. Create service provider and application accounts as described in Service Provider and Application Administration.
  8. Create service provider and application SLAs as described in Writing Service Level Agreements.
  9. Create network SLAs as described in Writing Network SLA Files.

 

Test the installation

When all servers in the cluster have been installed and configured, the complete installation must be verified using test applications.

 

SLEE Services

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:

Directory _autoslee

The following files are included as default in the directory
/usr/local/slee/bin/_autoslee

a_slee_trace.jar (M)

b_event_channel.jar (M)

b_slee_alarm.jar (M)

c_slee_event.jar (M)

c_slee_snmp.jar (O. Keep for SNMP support)

d_slee_backup.jar (O. Keep on server running DB)

d_slee_charging.jar (M)

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.)

f_policy.jar (NL - M, AL - R)

g_slee_resource.jar (NL - M, AL - R)

h_slee_statistics.jar (NL - M, AL - R)

i_slee_common_loader.jar (M)

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)

Directory autosrv

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)

Directory autowar

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)

 

Skip navigation bar  Back to Top Previous Next