 |
How to install the Parlay Resource Adaptor
Here is a short guide on how to install the Parlay Resource Adapter (RA). Only the Resource Adapter configuration stage is necessary for deployments.
It is assumed that the installer is already familiar with the concepts involved in installing JBoss and the mobicents SLEE. If not please read the MobicentsQuickStartGuide.
Resource Adapter configuration
The Parlay RA is configured using a standard java ".properties" file located in the source stream under $PROJECT_HOME/source/ra/src/java/org/mobicents/slee/resource/parlay/ParlayResourceAdapter.properties
Gateway Access
The first step is to configure the gateway location information. The Parlay RA supports the gateway location mechanisms supported by the main Parlay Gateway vendors
Using a well known Corba Naming Service
- Update the
org.mobicents.slee.resource.parlay.namingServiceIOR property with the appropriate value
- Update the
org.mobicents.slee.resource.parlay.ipInitialLocation property with the location of the "IpInitial" binding in the naming service
Using a well known host and port
- Update the
org.mobicents.slee.resource.parlay.ipInitialURL location with the well known address from which the naming service can be located
Using a well known IpInitial IOR
- Update the
org.mobicents.slee.resource.parlay.ipInitialIOR property with the appropriate value
The second step is to configure the RA appropriately for authenticating with the Parlay Gateway framework. To do this a domain ID, authentication sequence and
Parlay version must be specified. If the Parlay version is Parlay 4 a shared secret must also be specified e.g.
org.mobicents.slee.resource.parlay.domainID=1234
org.mobicents.slee.resource.parlay.authenticationSequence=TWO_WAY
org.mobicents.slee.resource.parlay.fw.parlayVersion=P_PARLAY_3
Test configuration
For test purposes it is also possible to configure the Parlay RA to bypass a gateway framework. This is useful for some test tools and may also be used in a real deployment
situation if a framework is not available. To do this a second configuration file is required. An example is located in $PROJECT_HOME/source/conf/ParlayRATest.properties.
By placing this file in your app server "conf" folder with the property org.mobicents.slee.resource.parlay.isByPassFwEnabled set to true the RA will bypass all framework interaction and attempt to locate service managers via IOR file references.
Note: In this mode the RA supports accessing only a single instance of each SCF type.
ORB Configuration
By default the Parlay RA has been configured to use JacORB. Other Orbs may also be used. Orb configuration will be loaded from the $PROJECT_HOME/source/conf/parlayra-orb.properties. Please consult the documentation for your chosen Orb.
Logging Configuration
The Parlay RA uses the apache commons-logging component for all log information. As all code is under the org.mobicents.slee.resource.parlay namespace logging can be enabled by adding this as an appender in your log4j.xml file.
Building and Installing
The RA can be build and installed using the provided and build.xml file in the mobicents-parlay-ra source stream. The following steps detail this process.
- Checkout the mobicents-parlay-ra source code from CVS
- Ensure
$JBOSS_HOME has been configured appropriately for your environment.
- Configure the RA as detailed in the instructions above
- From the top level directory in you checked out project type
ant deploy
Running and deploy will perform the following steps
- Build and package all RA code and type definitions
- Copy the RA to the Mobicents Slee installation
- Copy the RA beanshell deployment script to the Mobicents Slee installation.
The beanshell deployment script will then perform the following steps
- Install the RA
- Activate an RA Entity
- Create an Entity Link for services
-- Main.ivanmcshane - 27 Apr 2006
|