Browse Prior Art Database

Method for dynamic entry of JAIN TCAP service configuration data into persistent store

IP.com Disclosure Number: IPCOM000015485D
Original Publication Date: 2002-Jan-01
Included in the Prior Art Database: 2003-Jun-20
Document File: 3 page(s) / 44K

Publishing Venue

IBM

Abstract

Method for dynamic entry of JAIN TCAP service configuration data into persistent store Disclosed is a method for dynamic entry of Java Advanced Intelligent Network (JAIN*) Service Logic Execution Environment (SLEE) service configuration data into a persistent store. Dynamic data entry reduces the possibility of configuration errors. A Signaling System 7 (SS7) Transaction Capability Application Part (TCAP) service is used as an example to demonstrate this method. The service must have entries in the SLEE configuration file, the service’s configuration file and the persistent store. This method eliminates the need to manually enter configuration data service into the persistent store by 1. automatically parsing the SLEE configuration file for the names of services,

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 59% of the total text.

Page 1 of 3

Method for dynamic entry of JAIN TCAP service configuration data into persistent

store

Disclosed is a method for dynamic entry of Java Advanced Intelligent Network (JAIN*) Service Logic Execution Environment (SLEE) service configuration data into a persistent store. Dynamic data entry reduces the possibility of configuration errors. A Signaling System 7 (SS7) Transaction Capability Application Part (TCAP) service is used as an example to demonstrate this method. The service must have entries in the SLEE configuration file, the service's configuration file and the persistent store. This method eliminates the need to manually enter configuration data service into the persistent store by
1. automatically parsing the SLEE configuration file for the names of services,
2. automatically parsing each service's configuration file, and
3. generating and issuing the configuration commands.

    The service is identified in the SLEE configuration file, slee.xml, with this XML (Extensible Markup Language) element: <service location="services/calendar" /> The location attribute contains the name of the directory in which the service's configuration file is installed.

The "calendar" service's configuration file, service.xml, contains these elements:

<service-info>

<subscriber>calendar</subscriber>

<service-name>routeToLocation</service-name>

</service-info>

<env-entry>

<env-entry-name>tcap/provider/name</env-entry-name>

<env-entry-value>10-1-4:100</env-entry-value>

</env-entry>

The "c...