BEAWebLogic Network Gatekeeper€¦ · z“Document Scope and Audience” on page 1-2 ... zApplication —A TCP/IP based, telecom-enabled program accessed from either a telephony

BEAWebLogic Network Gatekeeper™

Installation Guide

Version 2.2Document Revised: May 15, 2006

CopyrightCopyright © 1995-2006 BEA Systems, Inc. All Rights Reserved.

Restricted Rights LegendThis software is protected by copyright, and may be protected by patent laws. No copying or other use of this software is permitted unless you have entered into a license agreement with BEA authorizing such use. This document is protected by copyright and may not be copied photocopied, reproduced, translated, or reduced to any electronic medium or machine readable form, in whole or in part, without prior consent, in writing, from BEA Systems, Inc.

Information in this document is subject to change without notice and does not represent a commitment on the part of BEA Systems. THE DOCUMENTATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. FURTHER, BEA SYSTEMS DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE DOCUMENT IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE.

Trademarks and Service MarksCopyright © 1995-2006 BEA Systems, Inc. All Rights Reserved. BEA, BEA JRockit, BEA WebLogic Portal, BEA WebLogic Server, BEA WebLogic Workshop, Built on BEA, Jolt, JoltBeans, SteelThread, Top End, Tuxedo, and WebLogic are registered trademarks of BEA Systems, Inc. BEA AquaLogic, BEA AquaLogic Data Services Platform, BEA AquaLogic Enterprise Security, BEA AquaLogic Interaction, BEA AquaLogic Interaction Analytics, BEA AquaLogic Interaction Collaboration, BEA AquaLogic Interaction Content Services, BEA AquaLogic Interaction Data Services, BEA AquaLogic Interaction Integration Services, BEA AquaLogic Interaction Process, BEA AquaLogic Interaction Publisher, BEA AquaLogic Interaction Studio, BEA AquaLogic Service Bus, BEA AquaLogic Service Registry, BEA Builder, BEA Campaign Manager for WebLogic, BEA eLink, BEA Kodo, BEA Liquid Data for WebLogic, BEA Manager, BEA MessageQ, BEA SALT, BEA Service Architecture Leveraging Tuxedo, BEA WebLogic Commerce Server, BEA WebLogic Communications Platform, BEA WebLogic Enterprise, BEA WebLogic Enterprise Platform, BEA WebLogic Enterprise Security, BEA WebLogic Express, BEA WebLogic Integration, BEA WebLogic Java Adapter for Mainframe, BEA WebLogic JDriver, BEA WebLogic Log Central, BEA WebLogic Mobility Server, BEA WebLogic Network Gatekeeper, BEA WebLogic Personalization Server, BEA WebLogic Personal Messaging API, BEA WebLogic Platform, BEA WebLogic Portlets for Groupware Integration, BEA WebLogic Real Time, BEA WebLogic RFID Compliance Express, BEA WebLogic RFID Edge Server, BEA WebLogic RFID Enterprise Server, BEA WebLogic Server Process Edition, BEA WebLogic SIP Server, BEA WebLogic WorkGroup Edition, BEA Workshop for WebLogic Platform, BEA Workshop JSP, BEA Workshop JSP Editor, BEA Workshop Struts, BEA Workshop Studio, Dev2Dev, Liquid Computing, and Think Liquid are trademarks of BEA Systems, Inc. Accelerated Knowledge Transfer, AKT, BEA Mission Critical Support, BEA Mission Critical Support Continuum, and BEA SOA Self Assessment are service marks of BEA Systems, Inc.

All other names and marks are property of their respective owners.

BEA WebLogic Network Gatekeeper Installation Guide 1

Contents

1. Document RoadmapDocument Scope and Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Guide to this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Other documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

2. Installing WebLogic Network GatekeeperStep 1: Prepare the installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Step 2: Install the software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Install on Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Install on HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Install on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Step 3. Install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Step 4. Provide the license key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Step 5. Install the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Install a MySQL database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Install an Oracle 10g RAC database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Install an Oracle 10g single instance database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

Step 6. Make scripts executable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Step 7. Encrypt database passwords (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

Step 8. Setup the WebLogic Network Gatekeeper software . . . . . . . . . . . . . . . . . . . . . . 2-12

2 BEA WebLogic Network Gatekeeper Installation Guide

1. Setup database connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

2. Edit the slee_properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

3. Create start-up scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

4. Finalize the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

5. Setup starting the Network Gatekeeper automatically at boot-time (optional) . . 2-16

Step 9. Delete unused services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

Step 10. Start the WebLogic Network Gatekeeper supervision process. . . . . . . . . . . . . 2-17

Step 11. Start Network Gatekeeper Management Tool. . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

Step 12. Configure WebLogic Network Gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

Step 13. Test the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18

A list of SLEE Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18

Directory _autoslee . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

Directory autosrv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

Directory autowar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21

3. Installing the Network Gatekeeper Management ToolAbout the Network Gatekeeper Management Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Installing the Network Gatekeeper Management Tool (Unix) . . . . . . . . . . . . . . . . . . . . . 3-1

Installing the Network Gatekeeper Management Tool (Windows 2000/XP) . . . . . . . . . . 3-2

4. Migrating WebLogic Network GatekeeperStep 1: Prepare for migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Download Network Gatekeeper installation files . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Prepare for migrating the database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Step 2: Backup software and database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Backup the database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Backup the software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Step 3: Install upgraded software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

BEA WebLogic Network Gatekeeper Installation Guide 3

Install Network Gatekeeper 2.2 software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Step 4: Shutdown all Network Gatekeeper SLEEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Step 5: Run migration scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Upgrade the Network Gatekeeper software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Step 6: Configure and start the upgraded SLEEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Rollback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Rollback the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Rollback the software installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

A. Directory Structure and ContentsInstallation CD and delivery structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1

Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1

Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2

Installed system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-3

Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-3

Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-3

B. References

4 BEA WebLogic Network Gatekeeper Installation Guide

BEA WebLogic Network Gatekeeper Installation Guide 1-1

C H A P T E R 1

Document Roadmap

The following sections describe the audience for, and organization of, this document:

“Document Scope and Audience” on page 1-2

“Guide to this Document” on page 1-2

“Terminology” on page 1-2

“Related Documentation” on page 1-6

Document Roadmap

1-2 BEA WebLogic Network Gatekeeper Installation Guide

Document Scope and AudienceThis document describes the initial installation and setup of BEA WebLogic Network Gatekeeper including:

Installation

Start up and configuration

This document is primarily for support engineers and system administrators working with BEA WebLogic Network Gatekeeper

Guide to this DocumentThe document contains the following chapters:

Chapter 1, “Document Roadmap:” This chapter

Chapter 2, “Installing WebLogic Network Gatekeeper:”Basic installation and configuration tasks for WebLogic Network Gatekeeper

Chapter 3, “Installing the Network Gatekeeper Management Tool:” Installation and basic use of the Network Gatekeeper Management Tool, employed for most WebLogic Network Gatekeeper OAM tasks

Chapter 4, “Migrating WebLogic Network Gatekeeper:” Migrating an existing WebLogic Network Gatekeeper

TerminologyThe following terms and acronyms are used this document:

API —Application Programming Interface

Application —A TCP/IP based, telecom-enabled program accessed from either a telephony terminal or a computer.

Application Developer —An organization or individual developing service provider applications

Application Service Provider —An organization offering application services to end users through a telephony network

AS—Application Server

Te rmino logy


ATE —Application Test Environment

CORBA —Common Object Request Broker Architecture. WebLogic Network Gatekeeper uses CORBA for its internal communication

End User—The ultimate consumer of the services that an application provides. An end user can be the same as the network subscriber, as in the case of a prepaid service or they can be a non-subscriber, as in the case of an automated mail-ordering application where the subscriber is the mail-order company and the end user is a customer to this company

Enterprise Operator —See Service Provider

ESPA—The core layer of the Service Capabilities module

Event—A trackable, expected occurrence in the system, of interest to the operator

GMLC—Gateway Mobile Location Centre

GMSC—Gateway Mobile Switching Centre

GUI—Graphical User Interface

HA—High Availability

HTML—Hypertext Markup Language

IDL—Interface Definition Language

IIOP —Internet Inter-ORB Protocol

INAP—Intelligent Network Application Part

IOR—Interoperable Object Reference

IP—Internet Protocol

JDBC—Java Database Connectivity, the Java API for database access

MAP—Mobile Application Part

MMS—Multimedia Message Service

MPC—Mobile Positioning Centre

MPP—Mobile Positioning Protocol

MTP—L3 Message Transfer Part Layer 3

Document Roadmap


Network Plug-in—The WebLogic Network Gatekeeper module that implements the interface to a network node or OSA/Parlay SCS through a specific protocol

Northbound Interface—The Application Services Provider facing interface

NS—Name Service or Network Simulator

OAM—Operation, Administration, and Maintenance

Operator—The party that manages the Network Gatekeeper. Usually the network operator

ORB—The CORBA Object Request Broker

OSA—Open Service Access

OSS—Operation Support System

PAP—Push Access Protocol

Plug-in—See Network Plug-in

Plug-in Manager—The Network Gatekeeper module charged with routing an application-initiated request from a service capability module to a network plug-in

Policy Engine—The Network Gatekeeper module charged with evaluating whether a particular request is acceptable under the rules

Rules—The customizable set of criteria - based on SLAs, subscriber profiles, and operator-desired additions - according to which requests are evaluated

SCCP—Signalling Connection Control Part

SCF—Service Capability Function or Service Control Function, in the OSA/Parlay sense.

SCS—Service Capability Server, in the OSA/Parlay sense. WebLogic Network Gatekeeper can interact with these on its southbound interface

SCS Plug-in—A network plug-in used to connect SCSes to the WebLogic Network Gatekeeper.

Service Capability—Support for a specific kind of traffic within WebLogic Network Gatekeeper. For example, the Messaging Service Capability processes SMS and MMS messages

Service Capability Manager—The Network Gatekeeper module charged with routing a network-triggered event from a network plug-in to an appropriate service capability module

Te rmino logy


SESPA—The top layer of the Service Capabilities module

SLA—Service Level Agreement

SLEE—Service Logic Execution Environment. The core modules in WebLogic Network Gatekeeper run in SLEE-based environments

SLEE Service—A software module that is designed to execute in the SLEE

SMPP—Short Message Peer-to-Peer Protocol

SMS—Short Message Service

SNMP—Simple Network Management Protocol

SOAP—Simple Object Access Protocol

Southbound Interface—The network-node facing interface. It may also interact with an OSA/Parlay gateway

SPA—Service Provider APIs

SPC—Signalling Point Code

SQL—Structured Query Language

SRF—Service Resource Function

SS7 —Signalling System 7

SSF —Service Switching Function

SSN —Sub System Number

Subscriber —A person or organization that subscribes for an application. The subscriber is charged for the service usage. Also see End User.

TCAP—Transaction Capability Application Part

TCP—Transmission Control Protocol

Traffic Path—The data flow of a particular request through WebLogic Network Gatekeeper

UDDI —Universal Description, Discovery and Integration

URL —Universal Resource Locator

Document Roadmap


User—A person working with OAM through the WebLogic Network Gatekeeper Management Tool that has an administrative user name and password. An application accessing services through one or more APIs and has a user name and a password.

VAS—Value Added Service

VLAN—Virtual Local Area Network

VPN—Virtual Private Network

WESPA—The Web Services aware layer in WebLogic Network Gatekeeper. It can be part of both northbound interfaces (facing Application Service Providers) and southbound interfaces (facing network nodes)

WSDL—Web Services Definition Language

XML—Extended Markup Language

Related DocumentationThis installation guide is a part of WebLogic Network Gatekeeper documentation set. The other documents are:

Architectural Overview - BEA WebLogic Network GatekeeperAn overview of BEA WebLogic Network Gatekeeper’s functions and system characteristics.

System Administrator’s Guide - BEA WebLogic Network GatekeeperA guide to the administrative tasks in running Network Gatekeeper.

Application Developer’s Guide - Parlay X Web Services for BEA WebLogic Network Gatekeeper

A guide to designing and implementing applications using the Parlay X 1.0 Web Services API

API Descriptions - Parlay X Web Services for BEA WebLogic Network Gatekeeper The Parlay X API reference for WebLobic Network Gatekeeper

Application Developer’s Guide - Extended Web Services for BEA WebLogic Network Gatekeeper

A guide to designing and implementing applications using the Extended Web Services API.

API Descriptions - Extended Web Services for BEA WebLogic Network GatekeeperThe Extended Web Services API reference for WebLogic Network Gatekeeper

Rela ted Documentat ion


User’s Guide - BEA WebLogic Network Gatekeeper Application Test EnvironmentA guide to using the WebLogic Network Gatekeeper ATE for pre-testing applications.

Integration Guidelines for Partner Relationship Management - BEA WebLogic Network Gatekeeper

A guide to using the WebLogic Network Gatekeeper PRM interfaces

Web Services API Description for Partner Relationship Management - BEA WebLogic Network Gatekeeper

The PRM Web Services API reference for WebLogic Network Gatekeeper

Other documentationThe third party documentation needed to operate and maintain BEA WebLogic Network Gatekeeper system is listed in “References” on page B-1.

Document Roadmap



C H A P T E R 2

Installing WebLogic Network Gatekeeper

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 must be performed in the order presented.

The installation procedure is described per server in the cluster: it must be done for each server in the cluster. The individual servers become aware of each other by using entries in a shared database. The individual entries for each server are automatically inserted into the database when the Network Gatekeeper is configured. Configuration data is fetched from the file slee_properties.xml, which is unique for each server.

Before starting installation, you should understand the basics of the Network Gatekeeper. These are covered in the Architectural Overview - BEA WebLogic Network Gatekeeper, a part of the Network Gatekeeper documentation set.

The instructions cover installation on RedHat Linux Advanced Server 3, HP-UX, and Sun Solaris. The paths to the installation files are described in “Installation CD and delivery structure” on page A-1 and the directory structure for an installed system is described in “Installed system” on page A-3.

Individual files names are given in the form: filename<version>.type. As an example, the file referred to as jrockit-j2sdk<version>.bin.gz could have the full name jrockit-j2sdk1.4.2_05-linux-ia32.bin.gz.

The installation consists of twelve major steps:

“Step 1: Prepare the installation” on page 2-2

“Step 2: Install the software” on page 2-3

Ins ta l l i ng WebLog ic Network Gatekeepe r


“Step 3: Install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files” on page 2-6

“Step 4: Install the database” on page 2-7

“Step 5: Make scripts executable” on page 2-11

“Step 6: Encrypt database passwords (optional)” on page 2-11

“Step 7: Setup the WebLogic Network Gatekeeper software” on page 2-12

“Step 8: Delete unused services” on page 2-16

“Step 9: Start the WebLogic Network Gatekeeper supervision process” on page 2-17

“Step 10: Start Network Gatekeeper Management Tool” on page 2-17

“Step 11: Configure WebLogic Network Gatekeeper” on page 2-17

“Step 12: Test the installation” on page 2-18

Step 1: Prepare the installationBefore starting installation, make sure the following prerequisites are met:

The server on which the Weblogic Network Gatekeeper target system is to be installed must be one of the types described in the Technical Specification section in the Architectural Overview - BEA WebLogic Network Gatekeeper unless it has been specified differently in cooperation with BEA.

You must have the root password to the server.

You must have a license key for the product. This license key is obtained from BEA.

You must have access to the product CDs or the Download Center.

If you are using Oracle as your database, you must have a dedicated server or cluster of servers running Oracle 10g or 10g RAC.

If you are using MySQL as a database, the binaries for MySQL must be downloaded. See the Release Notes for information on the exact version of MySQL. MySQL can be downloaded from http://www.mysql.com. In addition you must download a specific version of the JDBC-driver. This driver can be found at:http://dev.mysql.com/get/Downloads/Connector-J/mysql-connector-java-3.0

.10-stable.tar.gz/from/pick. Extract the mysql-connector-java-3.0.10-stable-bin.jar file.

Step 2 : Ins ta l l the so f tware


Warning: It is very important that this specific driver and no other is used by the Network Gatekeeper when connecting to the MySQL database.

The Java SDK for your platform must be installed. See the Release Notes for information on the exact version and manufacturer of the Java SDK.

The most recent operating system patches must be installed. See the Release Notes for information on required patch levels.

On Solaris, you need to use GNU tar to extract the deliverable since file names are longer than 100 characters. Information about GNU tar can be found at http://www.gnu.org/software/tar/ . Also see http://www.sun.com/software/solaris/freeware/.

Step 2: Install the software

Install on Linux

1. Login 1. Log in to the target server as root. All commands described in this section assume that you

have logged in as root user

2. Verify that the correct OS patches are installed. Refer to the Release Notes for a description of necessary patches.

2. Install the JRockit Java SDK For Linux systems, the JRockit Java SDK is used.

1. Download and install the JRockit Java SDK.

3. Configure the JVM1. Define the environment variable JAVA_HOME to the newly installed JDK:

JAVA_HOME=<Java installation path>/j2sdk<version>

2. Make JAVA_HOME first in the path:

PATH=$JAVA_HOME/bin:$PATH

3. Make sure the correct JVM is used. Issue the command:

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)

4. Extract the Weblogic Network Gatekeeper software for Linux1. Copy the file wlng22_linux_ia32.tar.gz from the CD or the Download Center to

/usr/local on the local file system.

2. Extract the file.

3. Files are extracted to the local file system in the subdirectory ./slee

4. Continue with “Step 3: Install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files” on page 2-6.

Install on HP-UX




2. Install the Java™ for HP-UX 11i Out-of-Box toolFor HP-UX systems, the HP-UX Java™ for HP-UX 11i Out-of-Box tool is used. You must use the distribution for Itanium.

1. Download and install Java™ for HP-UX 11i Out-of-Box tool.

2. Download and install the HP-UX JDK.

3. Configure the JVM1. Define the environment variable:

JAVA_HOME=/opt/java1.4

Step 2 : Ins ta l l the so f tware


2. Make JAVAHOME first in the PATHPATH=$JAVA_HOME/bin:$PATH

3. Make sure the correct JVM is used. Issue the command: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)

4. Extract the Weblogic Network Gatekeeper software for HP-UX1. Copy, from the CD or the Download Center, the file wlng22_hpux_ia64.tar to


2. Extract the file.



Install on Solaris




2. Install the Sun Solaris Java SDKFor Sun Solaris, the Sun Solaris Java SDK is used.

1. Download and install Sun Solaris Java SDK.



3. Extract the Weblogic Network Gatekeeper software for Solaris1. Copy the file wlng22_solaris_sparc.tar.gz from the CD or the Download Center to


2. Extract the file using GNU tar.


4. Configure the JVM1. Define the environment variable JAVA_HOME to the newly installed JDK:

JAVA_HOME=<Java installation path>/j2sdk<version>

2. Make JAVA_HOME first in the path:

PATH=$JAVA_HOME/bin:$PATH

3. Make sure the correct JVM is used. Issue the command:

java -version

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

java version "1.4.2_05"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04)

Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)


Step 3: Install the 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 that imposes no restrictions on cryptographic strengths is available on the Java 2 SDK web site for those living in eligible countries.

1. Download the 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.

Step 4 : Ins ta l l the database


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

2. Replace the local_policy.jar and US_export_policy.jar files in the directory <$JAVA_HOME>/jre/lib/security with the files included in the downloaded zip file.

Step 4: Install the database

Install a MySQL databaseFollow the instructions in this section if you are using MySQL as your database.

MySQL can be installed either on the servers in the cluster building up the WebLogic Network Gatekeeper or on separate servers. If you choose to install it on servers in the cluster that also run Network Gatekeeper, it should be installed on servers in the Network Layer of the cluster.

1. Copy the installation file for MySQL to the directory /usr/local

2. Unpack the installation file.

3. Follow the MySQL installation instructions. They are found in:

/usr/local/mysql-<version>/INSTALL-BINARY

Below is a summary of the commands used to install MySQL. Refer to the actual installation instructions for a description of each command.

groupadd mysqluseradd -g mysql mysqlcd /usr/localln -s /usr/local/mysql-standard-<version> mysqlcd mysqlscripts/mysql_install_db --user=mysqlchown -R root .chown -R mysql datachgrp -R mysql .bin/mysqld_safe --user=mysql &

4. Setting MySQL to autostart on reboot is recommended. Refer to the instructions for MySQL and the operating system.

5. All servers that run Network Gatekeeper except for the Network Gatekeeper servers that also run the database must be granted privileges on the database. For each of these servers execute the SQL command GRANT ALL ON *.* TO <database user>@'<ip-address>' IDENTIFIED BY '<password>';



6. If the database does not run on a server on which Network Gatekeeper also runs:

a. Create a database named slee_db.

b. Set up replication between the database servers so that:

– On MySQL Server A, server A is Master and server B is Slave.

– On MySQL Server B, Server B is Master and server A is Slave.

c. Edit the file /usr/local/mysql/data/my.cnf on both servers so that max_connections is at least 152 times the number of Network Gatekeeper servers in the cluster.

7. Restart MySQL.

8. Go on to “Step 5: Make scripts executable” on page 2-11

Install an Oracle 10g RAC databaseFollow the instructions in this section if you are using Oracle 10g RAC as your database.

1. Set up the base configurationOracle 10g RAC must be installed on dedicated servers not running in the cluster building up the WebLogic Network Gatekeeper.

1. Install the Oracle 10g RAC database software using the instructions provided by Oracle.

2. Make sure that there is a public virtual IP address defined for the RAC instances. Network Gatekeeper uses the public virtual IP addresses instead of the actual IP addresses when connecting to the RAC.

3. Download and install the latest patch set. This is important because significant improvements have been made with regards to fail-over.

4. Configure Oracle Notification Service (ONS) on all RAC instances. Add all node host names and ports to the nodes parameter in the ONS configuration file <ORACLE_HOME>/opmn/conf/ons.config. This means that all nodes, both RAC instances and Network Gatekeeper servers, must be listed. An example configuration file for a system with two Network Gatekeeper servers and two RAC instances is given below.

localport=6100remoteport=6200nodes=rac_host_1:6200,rac_host_2:6200,wlng_host_1:6200,wlng_host_2:6200

Step 4 : Ins ta l l the database


5. Restart the ONS daemons using the command <ORACLE_HOME>/bin/onsctl.

2. Use these recommended configuration options1. Create the database using the Transaction Processing template.

2. Use Automatic Storage Management.

3. Use the Dedicated Server Mode for the database.

4. Change the following parameters:

– Set the parameter open_cursors. Define number of cursors to be more than 300.

– Set the parameter processes. Define number or of processes to be (MaxCapacity + 2) times the number of Network Gatekeeper servers in the cluster. MaxCapacity is defined as a parameter to the JDBC driver. Normally this value is 150.

3. Define a database user1. Create a database user for Network Gatekeeper with an unlimited quota and a default

tablespace users. The user name and password for the user are later defined in each Network Gatekeeper Server.

2. The user must be granted the following privileges:

– CREATE SESSION

– CREATE TABLE

Network Gatekeeper must be configured with an additional set of parameters to make it work correctly with the database. This action is performed during the configuration of WebLogic Network Gatekeeper software as described in “Step 7: Setup the WebLogic Network Gatekeeper software” on page 2-12

3. Use the Dedicated Server Mode for the database.






4. Configure the Oracle database for backup1. Configure the Oracle database for backup as described in “Backing Up and Restoring

WebLogic Network Gatekeeper” in the System Administrator’s Guide - BEA WebLogic Network Gatekeeper.


Install an Oracle 10g single instance databaseFollow the instructions in this section if you are using a single Oracle 10g instance as your database.

Warning: Single instance Oracle configurations must not be used in production systems.

1. Set up the base configurationThe Oracle 10g instance must be installed on a dedicated server not running in the cluster building up the WebLogic Network Gatekeeper.

1. Install the Oracle 10g database software using the instructions provided by Oracle.

2. Use these recommended configuration options1. Create the database using the Transaction Processing template.

2. Use Automatic Storage Management.

3. Use Dedicated Server Mode for the database.




3. Define a database user1. Create a database user for Network Gatekeeper with an unlimited quota and a default

tablespace users. The user name and password for the user are later defined in each Network Gatekeeper Server.

Step 5 : Make sc r ip ts executab le


2. The user must be granted the following privileges:

– CREATE SESSION

– CREATE TABLE

Network Gatekeeper must be configured with an additional set of parameters to make it work correctly with the database. This action is performed during the configuration of WebLogic Network Gatekeeper software as described in “Step 7: Setup the WebLogic Network Gatekeeper software” on page 2-12.

4. Configure the Oracle database for backup1. Configure the Oracle database for backup as described in “Backing Up and Restoring

WebLogic Network Gatekeeper” in the System Administrator’s Guide - BEA WebLogic Network Gatekeeper.


Step 5: Make scripts executableYou must make sure all Network Gatekeeper scripts are executable:

1. Change directory to the installation directory of the WebLogic Network Gatekeeper: /usr/local/slee/bin

2. Make sure all scripts are executable by issuing the command:

chmod u+x *.sh

Step 6: Encrypt database passwords (optional)An encrypted version of the database password may be defined in the configuration file for Network Gatekeeper.

Note: The password must be encrypted on the same server on which it is to be used. The password generator must be run by the same user that runs the Network Gatekeeper. This procedure is optional. Non-encrypted passwords can also be used.

Follow the instructions below to encrypt the database password:

1. Execute the script /usr/local/slee/bin/encryptPassword.sh

2. When prompted, enter the database password as defined when installing the database.



The encrypted version of the password is displayed, as, for example:{ENC}441619E218071179E0C03186EEB2513F

3. Make a note of the encrypted password as it will be used when configuring the JDBC connection for Network Gatekeeper.

Step 7: Setup the WebLogic Network Gatekeeper software

1. Setup database connectivity

Using MySQL1. Copy the file mysql-connector-java-3.0.10-stable-bin.jar that you downloaded as

a prerequisite to installation to the directory /user/local/slee/lib See “Step 1: Prepare the installation” on page 2-2 for more information.

2. In the directory /user/local/slee/lib, rename the file mysql-connector-java-3.0.10-stable-bin.jar to mysql.jar.

3. Go on to “2. Edit the slee_properties file” on page 2-13

Using Oracle RAC 1. Install the Oracle Database 10g Client package. Make sure to install Oracle Notification

Service (ONS), which is used both in the RAC instances and in the Network Gatekeeper servers and the thin JDBC driver.

Warning: Install Oracle Database 10g Client package logged in as the same user who is the owner of Network Gatekeeper and who will be running the Network Gatekeeper software, not as an Oracle user as stated in the Oracle installation instructions. This is necessary because the Network Gatekeeper supervisor process also supervises the ONS processes and restarts them if necessary.

2. Copy the JDBC-driver that was installed when installing the Oracle Database 10g Client package from <ORACLE_HOME>/jdbc/lib/ojdbc14.jar to /usr/local/slee/lib.

3. Configure Oracle Notification Service (ONS). The configuration is done by adding all node host names and ports to the nodes parameter in the ONS configuration file <ORACLE_HOME>/opmn/conf/ons.config. This means that all nodes, both RAC instances and Network Gatekeeper servers, must be listed. An example of a configuration file for a system with two Network Gatekeeper servers and two RAC instances:

Step 7 : Setup the WebLog ic Netwo rk Gatekeepe r so f tware


localport=6100remoteport=6200nodes=rac_host_1:6200,rac_host_2:6200,wlng_host_1:6200,wlng_host_2:6200

4. Restart the ONS daemons using the command <ORACLE_HOME>/bin/onsctl.

5. Copy the file ons.jar from <ORACLE_HOME>/opmn/lib/ to <installation path>/slee/lib.

JDBC depends on Oracle Notification Service (ONS) to propagate database events and notify JDBC of them.


Using Oracle Single Instance1. Install the Oracle Database 10g Client package. Make sure to install the thin JDBC driver.

2. Copy the JDBC-driver that was installed when installing the Oracle Database 10g Client package from <ORACLE_HOME>/jdbc/lib/ojdbc14.jar to /usr/local/slee/lib.


2. Edit the slee_properties file1. Find the file <wlng-installation path>/bin/slee_properties.xml

2. In the <SLEE_PROPERTIES> element, define:

– the name attribute as the name you have chosen for the SLEE. It can have a maximum of 20 characters. No whitespaces or special characters are allowed.

3. If you are using Oracle 10g RAC, add the additionalJavaProps attribute to both the <SLEE_PROPERTIES> and <SLEE_AGENT> elements and define it as “-Doracle.ons.oraclehome=<ORACLE_HOME>”

4. In the <SLEE_HOST> element, define:

– the address attribute as the IP-address of the server.

5. In the <SLEE_PATH> element, define:

– the slee_install_path attribute as the path of the SLEE, normally /usr/local/slee

6. If you are using MySQL, in the <SLEE_PATH> element, define:



– the database_install attribute as the path of the MySQL installation. Ignore this attribute if you are not using MySQL.

7. If you are using MySQL:

In the <SLEE_DB_1> element, define:

– the user attribute as the Database username. Network Gatekeeper will connect to the database as this user. The user will be setup automatically.

– the pwd attribute as the Database password.

– the address IP attribute as the address of the server running the first database.

– the port attribute as the port number for the database on the first server.

In the <SLEE_DB_2> element, define:

– the user attribute as the Database username. Network Gatekeeper will connect to the database as this user. The user will be setup automatically.

– the pwd attribute as the Database password.

– the address IP attribute as the address of the server running the second database.

– the port attribute as the port number for the database on this server.

Note: When using MySQL as database, all servers in a cluster shall have identical values in <SLEE_DB_1> and <SLEE_DB_2>

8. If you are using Oracle RAC, add the <JDBCConnectionPool> element and define the attributes as follows:

– DriverName = "oracle.jdbc.pool.OracleDataSource"– Properties = "user=<Oracle user ID>;password=<Password for Oracle User ID>"

Use the database user created in Step 5B, “3. Define a database user” on page 2-9 and either the real password or an encrypted password if you have created one. See “Step 6: Encrypt database passwords (optional)” on page 2-11 for more information.

– MaxCapacity = "150"– URL = "jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<rac_host_1_vip>)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=<rac_host_2_vip>)(PORT=1521))

Step 7 : Setup the WebLog ic Netwo rk Gatekeepe r so f tware


(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=<svc_name>)))"

Below is a description of the parameters in the URL property:

– <rac_host_1_vip> is the public virtual IP address of one of the Oracle RAC server instances. This was setup during the installation of the Oracle cluster.

– <rac_host_2_vip> is the Virtual public IP address of the other Oracle RAC server instance. This was setup during the installation of the Oracle cluster.

Note: The RAC node public virtual IP addresses (<rac_host_1_vip> and <rac_host_2_vip>) must be used in the HOST parameters.

– <svc_name> is the Oracle RAC database service name setup during Oracle RAC database creation.

Note: The database service name, not the service ID, must be used in the in the SERVICE_NAME parameter.

9. If you are using an Oracle 10g single instance database, add the <JDBCConnectionPool> element and define the attributes as follows:

– DriverName="oracle.jdbc.pool.OracleDataSource"

– Properties="user=<Oracle user ID>;password=<Password for Oracle User

ID>"

Use the database user created in Step 5B, “3. Define a database user” on page 2-9 and either the real password or an encrypted password if you have created one. See “Step 6: Encrypt database passwords (optional)” on page 2-11 for more information.

– MaxCapacity = "150"– URL="jdbc:oracle:thin:@//<IP-address of server hosting Oracle database>:<port-number>/<database service name>"

Warning: The tags <SLEE_DB_1>,<SLEE_DB_2> and <JDBCConnectionPool> are mutually exclusive and cannot be present in the file at the same time.

There are other configuration options for memory size, garbage collection size, and CORBA configuration used to tune the system. These parameters are deployment specific and depend on the type of server, CPU and so on. The default values can be used.

3. Create start-up scripts Run the shell script./SLEEConfig.sh



4. Finalize the configurationRun the shell script ./postconfig.sh

This script sets up database users etc.

Note: MySQL only: If the MySQL admin/root password has been changed the user and password must be included when calling the postconfig script. Enter ./postconfig root <password>

5. Provide the license keyA license key must be provided to the Network Gatekeeper. The license key is provided by BEA.

1. Change directory to /usr/local/slee/bin.

2. Execute the script setLicenseKey.sh with the license key as an argument.

Note: It is only necessary to do this on one server in the cluster.

6. Setup starting the Network Gatekeeper automatically at boot-time (optional)If you would like the WebLogic Network Gatekeeper to start automatically at boot-time, copy the script /usr/local/slee/bin/sleeagent to the location where your system has its startup files:

For Linux and Solaris, the script usually is put in /etc/init.d (at least on machines SYSV R4 based systems) and linked to /etc/rc3.d/S99sleeagent.

For HP-UX, the script usually is put in /sbin/init.d (at least on machines SYSV R4 based systems) and linked to /sbin/rc3.d/S99sleeagent.

Note: The database must be started before this script is started.

Step 8: Delete unused servicesNot all services are relevant to all servers. Network Layer servers use a different subset of Network Gatekeeper services than Access Layer servers, and so forth. Unused services per server should be deleted. To see which services are tied to which server type, see “A list of SLEE Services” on page 2-18.

Step 9 : S ta r t the WebLogic Network Gatekeeper superv is i on p rocess


Step 9: 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:

./runAgent.sh &

It is important to start the supervision process in the background, so the supervision process will not be terminated if the shell it was started from is closed. It is a good idea to to redirect the output to a file, so output from the shell is not lost.

Step 10: Start Network Gatekeeper Management Tool1. If you are using a separate machine to run the Network Gatekeeper Management Tool, install

the Management software using the information in “Installing the Network Gatekeeper Management Tool” on page 3-1.

2. Login to the Management Tool, using the instructions in “Starting a Network Gatekeeper Management Tool and adding a SLEE” in the “Running WebLogic Network Gatekeeper - Overview” chapter in the System Administrator’s Guide - BEA WebLogic Network Gatekeeper. Both the default username and password are install.

3. Create a new user with administrative privileges. See “Managing Administrative Users” in the System Administrator’s Guide - BEA WebLogic Network Gatekeeper, for more information.

4. Remove the default user immediately after the login for the new user has proved successful.

Step 11: Configure WebLogic Network Gatekeeper1. Setup backup procedures as described in “Backing Up and Restoring WebLogic Network

Gatekeeper” in the System Administrator’s Guide - BEA WebLogic Network Gatekeeper.

2. Create administrative accounts as described in “Managing Administrative Users” in the System Administrator’s Guide - BEA WebLogic Network Gatekeeper.

3. Configure relevant network protocol plug-ins as described in “List of Configuration Parameters, Network plug-ins” in the System Administrator’s Guide - BEA WebLogic Network Gatekeeper .



4. Configure connections with OSA/Parlay gateways as described in “Connecting to OSA Gateways” in the System Administrator’s Guide - BEA WebLogic Network Gatekeeper

5. Configure Web Services ports as described in “Setting Up Application Connections - Web Services” in the System Administrator’s Guide - BEA WebLogic Network Gatekeeper.

6. Configure the Partner Relationship Management interfaces as described in the Integration Guidelines for Partner Relationship Management - BEA WebLogic Network Gatekeeper.

7. Create service provider and application accounts as described in “Enabling Service Providers and Applications” in the System Administrator’s Guide - BEA WebLogic Network Gatekeeper.

8. Create service provider and application SLAs as described in “Writing Service Level Agreements” in the System Administrator’s Guide - BEA WebLogic Network Gatekeeper.

9. Create network SLAs as described in “Writing Network SLA Files” and “Protecting the Network with Traffic SLAs” in the System Administrator’s Guide - BEA WebLogic Network Gatekeeper.

Step 12: Test the installationWhen all servers in the cluster have been installed and configured, the complete installation must be verified using test applications.

A list of SLEE ServicesThis section describes all the different SLEE services in the installation directory structure. It explains which files can be removed, depending on the type of server - Access Layer, Network Layer, and so forth - being installed. The following notation is used in this section:

AL —Access Layer server

NL —Network Layer server

PL —Partner Relationship Management Layer server

M —Mandatory

O —Optional

R —Remove

A l i s t o f SLEE Se rv ices


Directory _autosleeThe 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)

b_slee_edr.jar (M)

b_slee_global_store.jar (O)

c_slee_event.jar (M)

c_slee_snmp.jar (O. Keep for SNMP support)

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

d_slee_charging.jar (M)

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

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

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 autosrvThe 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_plugin_message_sender_pap.jar (NL - O, AL - R)

b_smpp_gms_resource.jar (NL - O, AL - R)

b_smpp_gms_resource_ussd.jar (NL - O, AL - R)

c_osa_nichs.jar (NL - O. Keep if call control is supported, AL - R)

cert_builder.jar (NL - O, 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_message_sender.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)

A l i s t o f SLEE Se rv ices


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_message_sender.jar (NL - R, AL - O)

x_sespa_messaging.jar (NL - R, AL - O)

x_sespa_messaging_ui.jar (NL - R, AL - O)

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

y_legacy_smpp.jar (NL - R, AL - O)

y_legacy_pap.jar (NL - R, AL - O)

y_legacy_mm7.jar (NL - R, AL - O)

z_pmt_op.jar (NL -O, AL -O, PL - M) -Deprecated

z_pmt_sp.jar (NL -O, AL -O, PL - M) -Deprecated

z_prm_op.jar (NL -O, AL -O, PL - M)

z_prm_sp.jar (NL -O, AL -O, PL - M)

Directory autowarThe following files are included as default in the directory /usr/local/slee/bin/autowar

legacy_mm7.war (NL - R, AL - O)

legacy_pap.war (NL - R, AL - O)

mlp_location_resource.war (NL - O, AL - R)

mm7_vasp.war (AL - R, NL -Keep if MM7 plug-in is used)



parlayx2.war (AL - Keep if Parlay X 2.1 interface is used, NL -R)

parlayx.war (AL - Keep if Parlay X 1.0 interface is used, NL -R)

wespa.war (AL - Keep if Extended Web Services interface is used, NL -R)

plugin_message_sender_pap.war (AL - R, NL -Keep if PAP plug-in is used)

wpmt.war (NL -O, AL -O, PL - M) -Deprecated

wprm.war (NL -O, AL -O, PL - M)


C H A P T E R 3

Installing the Network Gatekeeper Management Tool

The following sections describe the Network Gatekeeper Management Tool:

“About the Network Gatekeeper Management Tool” on page 3-1

“Installing the Network Gatekeeper Management Tool (Unix)” on page 3-1

“Installing the Network Gatekeeper Management Tool (Windows 2000/XP)” on page 3-2

About the Network Gatekeeper Management Tool WebLogic Network Gatekeeper is managed through the Network Gatekeeper Management Tool. The tool provides both a graphical and a text based interface. The Management Tool allows the operator to start, stop, and manipulate both the SLEEs, the Service Logic Execution Environment in which the core modules in Network Gatekeeper run, and the SLEE Services, which provide Network Gatekeeper with its core functionality.

Both the graphical and the text based interface tool can access the SLEEs through a CORBA connection and both support execution of OAM batch files (scripts). The text based management tool may also be used through a remote connection such as telnet.

For information on using the Network Gatekeeper Management Tool, see “Running WebLogic Network Gatekeeper - Overview” in the System Administrator’s Guide - BEA WebLogic Network Gatekeeper.

Ins ta l l i ng the Network Ga tekeeper Management Too l


Installing the Network Gatekeeper Management Tool (Unix)To install the Network Gatekeeper Management Tool on a Unix workstation, that is, a Unix machine that is not being used as a BEA WebLogic Network Gatekeeper:

Install the Java Runtime Environment1. Download Java 2 runtime environment, standard edition version 1.4.2.

2. Run the installation script.

3. Follow the instructions provided by the installation script. The default settings are recommended.

Install Network Gatekeeper Management Tool1. The Network Gatekeeper Management Tool software is contained in the software bundle for

WebLogic Network Gatekeeper.

2. Copy, from the CD or the Download Center, the file wlng22_manager.zip to the local file system.

3. Extract the installation binaries by issuing the command:unzip wlng22_manager.zip

4. The installation files are extracted to the local file system in the subdirectory ./manager

5. Change directory to <path to installation files>/manager

6. Run the installation script. Enter command:

./setup.sh

7. Follow the instructions provided by the installation script. The default settings are recommended.

Installing the Network Gatekeeper Management Tool (Windows 2000/XP)

To install the Network Gatekeeper Management Tool on a Windows PC, that is, a machine that is not being used as a BEA WebLogic Network Gatekeeper:

Ins ta l l ing the Network Gatekeepe r Management Too l (Windows 2000/XP)


Install the Java Runtime Environment1. Download Java 2 runtime environment, standard edition version 1.4.2 from:

http://java.sun.com/j2se

2. Run the installation wizard. The file name might differ depending on the current version available for download.

3. Follow the instructions provided by the installation wizard. The default settings are recommended.

Set system variables

1. Right-click on the My Computer icon and select Properties in the menu.

2. Click the Advanced tab

3. Click Environment Variables...

Note: Be careful when working with path variables; your computer may not work properly if existing variables are removed or altered.

4. In the System variables table, select the Path variable.

5. Click Edit...

6. In the Variable Value field, enter the full search path to Java.

7. Click OK.

8. In the System variables table, select the JAVA_HOME variable.

9. Click Edit...

If the JAVA_HOME variable does not exist, click New... to create it.

10. In the Variable Value field, enter the full search path to Java. Click OK.

Install Network Gatekeeper Management Tool1. The Network Gatekeeper Management Tool software is contained in the software bundle for

WebLogic Network Gatekeeper.

2. Copy, from the CD or the Download Center, the file wlng22_manager.zip from that directory to local file system.

Ins ta l l i ng the Network Ga tekeeper Management Too l


3. Extract the file wlng22_manager.zip

4. The installation files are extracted to the local file system in the subdirectory manager

5. Change directory to <path to installation files>\manager

6. Run the Network Gatekeeper Management Tool set-up wizard. Double click on the file install.bat and follow the instructions in the wizard.


C H A P T E R 4

Upgrading WebLogic Network Gatekeeper

This chapter describes how to upgrade WebLogic Network Gatekeeper from version 2.1 to version 2.2 in a clustered environment. For a complete and successful upgrade, all sections and steps below must be performed in the order presented.

Before starting the upgrade, you should be very familiar whit operation and maintenance of Network Gatekeeper.

The instructions cover upgrade of Network Gatekeeper running on RedHat Linux Advanced Server 3, HP-UX, and Sun Solaris, using either Oracle or MYSQL as a database.

It is assumed that the installation to upgrade from is running and that the installation is correct and has been performed according to the installation instructions given for the 2.1 version of the product.

Note: The upgrade includes restart of the servers since database schema changes have been introduced. This means that the upgrade cannot be performed in-traffic using these instructions. In-traffic upgrades are not covered in these instructions.

The upgrade consists of a set of major steps:

“Step 1: Prepare for upgrade” on page 4-2

“Step 2: Backup software and database” on page 4-3

“Step 3: Install upgraded software” on page 4-3

“Step 4: Shutdown all Network Gatekeeper SLEEs” on page 4-4

“Step 5: Run upgrade scripts” on page 4-4

Upgrad ing WebLogic Network Gatekeeper


“Step 6: Configure and start the upgraded SLEEs” on page 4-5

Step 1: Prepare for upgradeBefore starting installation, make sure the following prerequisites are met:

The Network Gatekeeper cluster to be updated must be on version 2.1.

The servers on which the Network Gatekeeper target system is to be installed must be of one of the types described in the Technical Specification section in the Architectural Overview - BEA WebLogic Network Gatekeeper unless it has been specified differently in cooperation with BEA.

You must have access to the Network Gatekeeper 2.2 product CDs or the Download Center.

You must have the username and password for the database.

You must have a license key for the product. This license key is obtained from BEA.

The most recent operating system patches must be installed. See the Release Notes for information on required patch levels.

Download Network Gatekeeper installation filesRepeat these steps for all for all servers in the Network Gatekeeper cluster.

1. Copy the installation files for Network Gatekeeper 2.2 from the CD or the Download Center to /var/tmp/22 on the local file system.

– The installation file for HP-UX is wlng22_hpux_ia64.tar

– The installation file for Linux is wlng22_linux_ia32.tar.gz

– The installation file for Solaris is wlng22_solaris_sparc.tar.gz

Prepare for migrating the databaseRepeat these steps on the server that executes the database.

1. On the server that hosts the database, Copy the file wlng22_migration.tar from the CD or the Download Center to the local file system.

2. Extract the file wlng22_migration.tar to the directory <migration directory>.

3. If using Oracle as database:

Step 2 : Backup sof tware and database


a. Copy the file <ORACLE_HOME>/jdbc/lib/ojdbc14.jar to <migration directory>/lib

b. Make sure that the environment variable ORACLE_HOME points to the Oracle installation.

4. If using MySQL as database:

a. Copy the file mysql.jar to <migration directory>/lib. This file is found in /usr/local/slee/lib on any Network Gatekeeper server.

b. Make sure that the environment variable MYSQL_HOME points to the MySQL installation.

c. Check which server that holds the master database by using the method isLocalDatabaseMaster in the SLEE_backup service in the Management Tool. The information which database is the master is used when migrating the database.

5. Make sure that the environment variable JAVA_HOME points to the Java installation.

Step 2: Backup software and database

Backup the database1. Perform a database backup as described in chapter “Backing Up and Restoring WebLogic

Network Gatekeeper” in the System Administrator’s Guide.

Backup the softwarePerform the following procedure for all servers in the cluster:

1. Copy the directory, including all subdirectories, /usr/local/slee to /var/tmp/21/slee

Step 3: Install upgraded software

Install Network Gatekeeper 2.2 softwarePerform the following procedure for all servers in the cluster. It is assumed that the files are extracted in /var/tmp/22, and all paths are based on this assumption.

1. Change directory to /var/tmp/22.



2. Extract the installation file for Network Gatekeeper. Use the file that was downloaded when performing the instructions in “Download Network Gatekeeper installation files” on page 4-2.


4. Copy the file /usr/local/slee/bin/slee_properties.xml to /var/tmp/22/slee/bin.

5. Edit /var/tmp/22/slee/bin/slee_properties.xml to use the new configuration settings available in Network Gatekeeper 2.2. For a description of available settings, see section List of Configuration Parameters in the System Administrator’s guide.

6. Remove all unused SLEE services from slee/bin/autosrv and slee/bin/autowar.

Step 4: Shutdown all Network Gatekeeper SLEEsRepeat these steps for all for all servers in the Network Gatekeeper cluster.

1. Shutdown all Network Gatekeeper SLEEs servers in the clusters. Repeat the following steps using the Management tool:

a. Right-click on the symbol for the SLEE and select Shutdown SLEE.

b. When the status symbol turns yellow, which indicates that it is shutdown, right-click again and select Stop SLEE process.

When the status symbol turns red, the SLEE process is stopped.

2. Stop the SLEE agent by executing the script stopAgent.sh in the directory /usr/local/slee/bin. The script takes the arguments <user name> <password>, where username and password are the same as when logging in to the Management tool.

When the status symbol in the Management Tool turns black, the SLEE Agent process is stopped.

Step 5: Run upgrade scripts

Upgrade the Network Gatekeeper softwareRepeat these steps on the server that runs the database.

If using MySQL, log in to the server that runs the master database.

1. Extract the file wlng22_migration.tar to the directory <migration directory>.

Step 6 : Conf igure and s ta r t the upgraded SLEEs


2. If using Oracle as database, make sure that the environment variable ORACLE_HOME points to the Oracle installation.

3. If using MySQL as database, make sure that the environment variable MYSQL_HOME points to the MySQL installation.

4. Change directory to <migration directory>/bin.

5. If using Oracle as database, execute the upgrade script, enter the command: ./migration.sh oracle <database host> <Oracle Service Name> <database user ID> <DB user password>

– <database host> is the IP-address or host name of the server running the database.

– <Oracle Service Name> is the Oracle RAC database service name setup during Oracle RAC database creation.

– <database user ID> is the database user Network Gatekeeper uses to connect to the database, and <DB user password> is the password.

6. If using MySQL as database, execute the upgrade script, enter the command: ./migration.sh mysql <database host> slee_db <database user ID> <DB user password>

– <database host> is the IP-address or host name of the server running the database.

– <database user ID> is the database user Network Gatekeeper uses to connect to the database, and <DB user password> is the password.

Step 6: Configure and start the upgraded SLEEsPerform the following steps on all Network Gatekeeper servers.

1. Change directory to /var/tmp/22.

2. Copy the slee directory to /usr/local/slee by issuing the commandcp slee /usr/local/slee.

3. If there are additional SLEE services, with extensions to the base product, used in the deployment, verify that these are present.

4. Change directory to /usr/local/slee/bin .

5. Execute the script SLEEConfig.sh to generate the startup scripts for the Network Gatekeeper.

6. Execute the script postconfig.sh.



7. A license key must be provided to the Network Gatekeeper. The license key is provided by BEA. Change directory to /usr/local/slee/bin and execute the script setLicenseKey.sh with the license key as an argument.

Note: It is only necessary to set the license key on one server in the cluster.

8. Start the SLEE by executing runAgent.sh.

9. In the Management Tool, right-click on the symbol for the newly started SLEE and choose Start SLEE.

RollbackDepending on which stage in the upgrade process the rollback shall be performed, different actions are necessary.

Rollback the databaseSee the chapter “Backing Up and Restoring WebLogic Network Gatekeeper” in the System Administrator’s Guide.

Rollback the software installationPerform the following steps on all Network Gatekeeper servers.

1. Copy the directory, including all sub-directories, from /var/tmp/21/slee to /usr/local/slee

2. Change directory to /usr/local/slee/bin, and start the SLEE by executing runAgent.sh.

3. In the Management Tool, right-click on the symbol for the newly started SLEE and choose Start SLEE.

BEA WebLogic Network Gatekeeper Installation Guide A-1

A P P E N D I X A

Directory Structure and Contents

The section describes the structure of a WebLogic Network Gatekeeper installation:

“Installation CD and delivery structure” on page A-1

“Installed system” on page A-3

Installation CD and delivery structure

StructureThe directory structure in Table 4-1 is found on the WebLogic Network Gatekeeper CD-ROM or the download area.Table 4-1 BEA WebLogic Network Gatekeeper CD-ROM directory structure

/ wlng/ wlng22_linux_ia32.tar.gz

wlng22_hpux_ia64.tar

wlng22_solaris_sparc.tar.gz

wlng22_manager.zip

wlng_dev/ wlng22_dev.zip

wlng_integ/ wlng22_integ.zip

Di rec to r y S t ruc tu re and Contents

A-2 BEA WebLogic Network Gatekeeper Installation Guide

ContentsA brief introduction to the contents of each directory is given below.

/wlng/wlng22_linux_ia32.tar.gz

Contains installation files for WebLogic Network Gatekeeper for Linux. It also includes installation files for WebLogic Network Gatekeeper Management Tool for Windows, HP-UX, Linux, and Solaris.

/wlng/wlng22_hpux_ia64.tar

Contains installation files for WebLogic Network Gatekeeper for HP-UX. It also includes installation files for WebLogic Network Gatekeeper Management Tool for Windows, HP-UX, Linux, and Solaris.

/wlng/wlng22_solaris_sparc.tar.gz

Contains installation files for WebLogic Network Gatekeeper for Solaris. It also includes installation files for WebLogic Network Gatekeeper Management Tool for Windows, HP-UX, Linux, and Solaris.

/wlng/wlng22_manager.zip

Contains installation files for WebLogic Network Gatekeeper Management Tool for Windows, HP-UX, Linux, and Solaris.

/wlng_dev/wlng22_dev.zip

Contains installation files for WebLogic Workshop Controls for WebLogic Network Gatekeeper for Windows 2000/XP, installation files for WebLogic Network Gatekeeper Application test environment for Windows2000/XP, and WSDL files for the Web Services interfaces.

/wlng_integ/wlng22_integ.zip

Contains files for WebLogic Workshop Controls for WebLogic Network Gatekeeper Partner Relationship Management interfaces, and WSDL files for the Partner Relationship Management Web Services interfaces.

Ins ta l l ed sys tem

BEA WebLogic Network Gatekeeper Installation Guide A-3

Installed system

StructureIn a standard Unix installation, the directory structure in Table 4-2 is created.

ContentsA brief introduction to the contents of each directory is given below. For information on which directories to backup at a system backup, see “About system backup” in the System Administrator’s Guide - BEA WebLogic Network Gatekeeper.

/usr/local/slee/

Contains all directories and files related to BEA WebLogic Network Gatekeeper SLEE.

/usr/local/slee/bin/

Contains start up scripts and reference files for the name service, repository, and trading service.

/usr/local/slee/bin/_autoslee/

Contains the jar files of the SLEE utility services.

/usr/local/slee/bin/autosrv/

Table 4-2 BEA WebLogic Network Gatekeeper Unix Directory Structure

/

usr/ local/

slee/ bin/ _autoslee

autosrv

policy

services

trace

lib

servlet_engine

Di rec to r y S t ruc tu re and Contents

A-4 BEA WebLogic Network Gatekeeper Installation Guide

Contains the jar files of the SLEE services (except the SLEE utility services) that will be automatically started when the SLEE is started or restarted.

/usr/local/slee/bin/policy/

Contains the policy rule files and a template for writing SLAs.

/usr/local/slee/bin/services/

The directory where SLEE services will be stored when they are installed in the SLEE: the services working directory.

/usr/local/slee/bin/trace/

Contains the trace files generated by the trace service.

/usr/local/slee/lib/

Contains BEA WebLogic Network Gatekeeper executables other than SLEE services, such as, for example, the SLEE itself.

/usr/local/slee/servlet_engine/

Contains all directories and files related to the Tomcat servlet engine.

BEA WebLogic Network Gatekeeper Installation Guide B-1

A P P E N D I X B

References

Architectural Overview - BEA WebLogic Network Gatekeeper

System Administrator’s Guide - BEA WebLogic Network Gatekeeper

Application Developer’s Guide - Parlay X Web Services for BEA WebLogic Network Gatekeeper

Application Developer’s Guide - Extended Web Services for BEA WebLogic Network Gatekeeper

API Descriptions - Parlay X Web Services for BEA WebLogic Network Gatekeeper

API Descriptions - Extended Web Services for BEA WebLogic Network Gatekeeper

System Administrator’s Guide - BEA WebLogic Network Gatekeeper

User’s Guide - BEA WebLogic Network Gatekeeper Application Test Environment

Integration Guidelines for Partner Relationship Management - BEA WebLogic Network Gatekeeper

Web Services API Description for Partner Relationship Management - BEA WebLogic Network Gatekeeper

Standards API specifications

Parlay X specifications

See http://www.parlay.org

Database

Refe rences

B-2 BEA WebLogic Network Gatekeeper Insatllation Guide

MySQL Reference Manual

Orb

ORBacus for C++ and Java

Servlet engine

Tomcat Servlet Engine documentation

BEAWebLogic Network Gatekeeper€¦ · z“Document Scope and Audience” on page 1-2 ... zApplication —A TCP/IP based, telecom-enabled program accessed from either a telephony

Documents