|Oracle® Communications Services Gatekeeper Installation Guide
Part Number E16615-02
This chapter describes the tasks necessary to install the Service Oriented Architecture (SOA) Facades for Oracle Communications Services Gatekeeper. It also describes the different deployment types.
The Services Gatekeeper SOA Facades integrate Services Gatekeeper with SOA environments. The SOA Facades are deployed in Oracle Service Bus (OSB) and expose an interface identical to the SOAP interfaces in the Web Services SOAP Facades. From an application point of view, there is no difference between interacting with a SOA Facade or a SOAP Facade.The SOA product must be installed in addition to Services Gatekeeper.
If you use clustering, each SOA Facade must be co-located with an Access Tier but nothing else. Network Tiers must be in a separate cluster.
Both Services Gatekeeper core and communication services are deployed in OSB servers. You use these Service Bus servers instead of Access Tier and Network Tier servers.
These are the main installation steps. They are described in detail in the sections that follow:
Install Services Gatekeeper on all servers, see Install Services Gatekeeper.
Install OSB on all servers, see Install Oracle Service Bus.
Configure the Domain for the SOA Facades. There are different ways to do this:
Add OSB settings to the domain configuration script. See Edit and Verify the Domain Configuration Settings.
Make sure that the Oracle WebLogic Server installation directory is set in the domain configuration file. See Verify the Domain Configuration Settings.
Note:After installing OSB on a UNIX or Linux system, make sure that the directory /tmp/alsbTempJars has the same access privileges as the Oracle WebLogic Server home directory. Alternatively, remove the directory /tmp/alsbTempJars after the installation if the directory exists.
(As needed) Upgrade your existing SOA facade projects to Services Gatekeeper 5.0 with the instructions in “Managing and Configuring SOA Facades” in System Administration Guide, another document in this set.
Install Services Gatekeeper normally. See "Installing Oracle Communications Services Gatekeeper". Do not configure a domain yet.
Install OSB on all Services Gatekeeper AT servers. See Oracle Fusion Middleware Installation Guide for Oracle SOA Suite 11g at
Use the same Oracle WebLogic Server home directory for OSB and Services Gatekeeper.
Follow the domain configuration in the section below that matches your implementation.
OSB domain configuration is similar to Services Gatekeeper domain configuration. See "Configuring a Domain With the Graphical Mode Configuration Wizard".
For information on how to start and use the Oracle Service Bus Domain Configuration Wizards, see Oracle Fusion Middleware Installation Guide for Oracle SOA Suite 11g at
Always use this configuration template during installation:
OCSG OSB Integration configuration
This configuration template is very similar to the template OCSG Domain with Access and Network Clusters. It contains a few specialized configuration settings which are described in "Configuring Domain Settings".
The Console Configuration Wizard is a text-based version of the Graphical Console Configuration Wizard.
For information on how to start and use the Oracle Service Bus Domain Configuration Wizards, see Oracle Fusion Middleware Installation Guide for Oracle Service Bus Suite at
For details, see Using the Console Configuration Wizard.
Add the Oracle Service Bus definitions to the set domain script (setDomainEnv.cmd or setDomainEnv.sh). The StartWeblogic.bat script uses these scripts to configure domains. Use either the Windows or Linux/UNIX instructions:
Edit the Domain_Home\bin\setDomainEnv.cmd script file as follows:
At the top of the script, add the following OSB information, where Service_Bus_Home is the installation directory for Oracle Service Bus on your system; for example
set COMMON_COMPONENTS_HOME=Services_Gatekeeper_home\oracle_common set ALSB_HOME=Service_Bus_Home for %%i in ("%ALSB_HOME%") do set ALSB_HOME=%%~fsi set ALSB_DEBUG_FLAG=true set ALSB_DEBUG_PORT=7453
Edit the Domain_Home/bin/setDomainEnv.sh script file as follows:
At the top of the script, add the following OSB information. Note that Service_Bus_Home is the installation directory for Oracle Service Bus on your system; for example /var/oracle/gatekeeper5.0
set COMMON_COMPONENTS_HOME=Services_Gatekeeper_home/oracle_common ALSB__HOME="Services_Gatekeeper_home/Service_Bus_Home" export ALSB_HOME ALSB_DEBUG_FLAG="true" export ALSB_DEBUG_FLAG ALSB_DEBUG_PORT="7453" export ALSB_DEBUG_PORT
Follow these steps to make sure that your settings are now correct:
Verify that the Service Bus installation directory is defined in the domain configuration file:
ALSB_INSTALL_DIR refers to the installation directory for Oracle Service bus, for example /var/oracle/osb_10.3.
(Windows only) Verify that your classpath matches the classpath in "Windows". To view the classpath:
Right click My Computer.
Select Properties ->Advanced ->Environment Variables.
In addition to configuring the domain and changing to the environment script, you must also configure the SOA Facades themselves. To do so, follow the information in “Managing and Configuring SOA Facades” in Services Gatekeeper System Administrator's Guide, another document in this set.