WO2005054987A2 - Systemes, procedes et logiciel pour configurer et gerer un systeme de telecommunication - Google Patents

Systemes, procedes et logiciel pour configurer et gerer un systeme de telecommunication Download PDF

Info

Publication number
WO2005054987A2
WO2005054987A2 PCT/US2004/038970 US2004038970W WO2005054987A2 WO 2005054987 A2 WO2005054987 A2 WO 2005054987A2 US 2004038970 W US2004038970 W US 2004038970W WO 2005054987 A2 WO2005054987 A2 WO 2005054987A2
Authority
WO
WIPO (PCT)
Prior art keywords
configuration
software
telecommunications
server
data
Prior art date
Application number
PCT/US2004/038970
Other languages
English (en)
Other versions
WO2005054987A3 (fr
Inventor
Brett Watson-Luke
Nigel Waddington
Original Assignee
Intec Telecom Systems Plc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US10/723,612 external-priority patent/US20050114692A1/en
Priority claimed from US10/723,246 external-priority patent/US20050114642A1/en
Priority claimed from US10/723,243 external-priority patent/US20050114851A1/en
Priority claimed from US10/723,582 external-priority patent/US20050114240A1/en
Priority claimed from US10/723,581 external-priority patent/US20050114479A1/en
Application filed by Intec Telecom Systems Plc filed Critical Intec Telecom Systems Plc
Priority to EP04811659A priority Critical patent/EP1687691A2/fr
Publication of WO2005054987A2 publication Critical patent/WO2005054987A2/fr
Publication of WO2005054987A3 publication Critical patent/WO2005054987A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management

Definitions

  • This invention relates generally to the field of telecommunications, and more particularly to software and hardware used to configure and support telecommunications software and equipment.
  • Telecommunications service providers typically use several different software systems to provide provisioning, billing and customer support. These systems are typically developed by a vendor in one or more "generic" forms, and then custom configured to support the particular product or service offerings of a particular telecommunications service provider.
  • FIG. 1 to 5 depicts an example embodiment according to the inventive subject matter described herein.
  • J2EE Java 2 enterprise edition A specification for an execution environment for enterprise applications written in Java. It includes EJB and JMS.
  • XML Schema A W3C recommendation for expressing schemas (structure and valid content) of XML documents.
  • FIG. 1 depicts an example embodiment according to the inventive subject matter described herein.
  • Components 100 include data-stores 110, server components 120, file-based data 130, and configuration tools (alternately referred to as the "configuration toolkit") 140.
  • APIs exist within the convergent billing (CB) 122 and customer management ⁇ (CM) 124 OSS components for manipulation of the configuration.
  • CB convergent billing
  • CM customer management ⁇
  • CM customer management ⁇
  • the nature of the APIs varies between these systems and depending on the configuration item, but they provide the ability to create, update and delete or obsolete configuration items in these systems.
  • These APIs may be, however, low level — they deal with configuration in the terms of the OSS components.
  • a function of LMS 140 is to provide higher-level configuration items, such as the high-level product catalog items (that span multiple OSS components), or configuration policies and composite configuration items.
  • the configuration server 126 stores these higher level representations of configuration. It can be used to query the configuration in the OSS components, and to update it. It sends messages to OSS components when configuration data is updated.
  • Tools 144 may be provided that can extract configuration from these systems, to an external file-based form, where it may easily be manipulated using file-based tools and to load the configuration from its file-based representation back into the OSS components. These are part of the configuration tools user interface. These tools 144 interact with the OSS components via the configuration server 126. In order to manage the configuration effectively, version control tools 142 may be provided.
  • a workbench development tool (shown in block 144) may be provided.
  • This GUI application can work either off a file- based representation of the product definitions, or by communicating with the configuration server 126, via its APIs.
  • the XML schemata 132 depicted as "interacting" with the file-based representation of the configuration 134 are the documents that define the structure of the configuration data in its file-based form. Tools and developers can use the knowledge embedded in these schemas in order to assist them in reading or processing the configuration.
  • Figure 1 further depicts additional tools 146 interacting with the file-based representation of the configuration.
  • Configuration APIs provide access to the configuration data in CB 122 and CM 124 .
  • the configuration server 126 provides a unified API for accessing the configuration in the OSS.
  • the API is, in one example embodiment, required to provide:
  • the CB 122 and CM 124 configuration APIs may be part of the CB 122 and CM 124 servers, and may execute on any platform on which these OSS components are available.
  • the general configuration API may be part of the configuration server 126, and executes on the supported platforms for the configuration server 126.
  • OSS Import and Export Overview The terms import and export are used, respectively, to mean obtaining configuration data from the OSS so that it can be placed into the configuration repository, and to load the configuration data back into the OSS.
  • requirements for these components include the following functionality: • The ability to perform export operations on groups of configuration items. The ability to support multiple versions of OSS components. In various embodiments, supported versions of CB 122 and CM 124 are supported by the import and export tools. The implications of this may be significant: The configuration items that apply for the various versions of the product 5 differ between releases. The attributes of some configuration items differ between releases. Validations and business rules that apply to various configuration items differ between releases.
  • the API for accessing the configuration items can vary between releases. 10 • The transport mechanism for API calls varies between the releases. (Note that the variations may not be just between major releases. Minor • . . ⁇ • • - releases and maintenance releases may. also introduce changes of this nature.)
  • the import and export functionality may be met in part by functionality provided by the configuration server 126 and in part by functionality provided by the configuration tools GUI.
  • the configuration server 126 provides an API that allows clients to directly obtain 0 or update a file-based, which in one example embodiment is an XML representation, of the configuration items stored in CB 122 and CM 124 . It shall be understood, however, that XML is just one type of file-based form that can be used for this purpose, and that the inventive subject matter hereof is in no way limited to XML file formats.
  • the import and export operations may be performed by 5 components called publishers. These are described in the Configuration Server section herein.
  • the GUI provides file/folder explorer views of the configuration server 126 repository that allow imports and exports via menu actions, and allow items to be sent to the OSS via file copy-and-paste operations.
  • the configuration server 126 file system0 module that provides this functionality is described in the Configuration GUI section herein.
  • An additional module may be provided that makes it easy to move configuration between repositories.
  • This synchronization module is described in the Configuration GUI section herein. When used in conjunction with the configuration server 126 file system module this allows sophisticated selection of configuration to be imported/exported.
  • the configuration server 126 administration console also provides commands for import/export, and is described in the Configuration GUI section herein.
  • the import may be to an XML format
  • the export may be from the XML 10 format (for CB, CM 124 and product catalog configuration).
  • the product catalog format may be specified as a set of related XML Schemas for _•__., ⁇ the catalogs, categories, charge types and components.
  • the product catalog schemas ⁇ tiay be extensible.
  • the import and export related functionality is provided in the configuration server 126 and configuration tools UL
  • the implementation of the version control system is based on CVS.
  • CVS Web site http://www.cvshome.org for documentation on CVS.
  • L The implementation consists of the 25 following components: CVS server software, for managing the version control repository.
  • CVS client software for accessing the version control repository. Additional support for determining the differences between configuration items in the repository and local changes and for assisting the user to 30 merge them.
  • These operations may be provided in the configuration GUI by the Netbeans modules 510 for CVS. See the Configuration GUI section herein. Support for grouping configuration, and applying version control operations to the groups.
  • An API is provided to perform grouping operations.
  • a visual representation of groups may be required for usability purposes.
  • CVS Server In CVS embodiments, CVS provides the core version control facilities, and the management of the version control repository:
  • CVS Client There may be numerous CVS client applications and libraries available for accessing CVS.
  • the configuration tools GUI is required to interact with the version control system, and so the CVS client facilities provided is based on the needs of the GUI.
  • Grouping API Support for version control operations on groups of configuration are typically required. In order to support these operations, a grouping API is provided, and actions are provided in the configuration tools GUI for performing version control operations on these groups. See the Configuration GUI section herein for details.
  • the grouping API provides Java classes for manipulating grouping information, and serialization to XML form, and instantiation from XML form.
  • the following facilities are provided: JavaBeans may be provided for representing grouping information.
  • an XML form is used for grouping information. • The ability to select items from a group in the GUI and apply CVS operations on them. LThe ability to select items from a group in the GUI and import or export
  • Execution Environment LThe version control server 128 can be run on any platform that CVS can be ported to. LThe following platforms are supported in the distributed toolkit: Solaris, ALX, HP/UX. In some embodiments, the version control client tools require the following execution environment: a system with the JRE version 1.4.1 or later.
  • the configuration server 126 is responsible for: Providing a centralized location that can be queried or accessed to update configuration in the OSS. Ensuring that configuration is changed consistently across the OSS. Auditing changes to configuration across the OSS. Providing notifications to interested parties when configuration changes. Enforcing security on changes to the configuration. • Enforcing locking on configuration items.
  • the configuration server 126 may store these higher-level configuration items, and may propagate changes to these items to the OSS in the form of the lower level configuration items that may be used to implement the abstractions.
  • requirements are specified for a catalog component. According to one example embodiment it is responsible for: • . Providing transactional updates to the catalog. • Managing the persistence of the catalog. Validating updates to the catalog. Enforcing security on catalog updates and reads. Auditing catalog changes. Providing mechanisms for publishing the catalog into OSS systems. Notifying clients when the catalog changes so they can reflect these changes. Providing facilities for clients to search the catalog.
  • the catalog requirements and the configuration server 126 requirements may be practically the same - the commerce index merely represents a subset of the configuration data.
  • the major components of the CS are: .
  • LThe CS runs inside an EJB container. This provides: A standardized application environment, with proven portability. Transaction support, including two-phase commit (if required). • Choice in application servers (There may be a multitude of vendors with tested J2EE conformance. See http://java.sun.com/j2ee/compatibility.html).
  • Security container managed authorization).
  • Server 126 includes a configuration server 210 having components 21 Oa, 21 Ob, 210c and 21 Od..
  • a catalog database 220 is also included, along with clients 230. Further included are a convergent billing server 212 and a customer management server 214. Note that the set of clients is illustrative only. Only the configuration tools GUI, workbench, and administration console may be part of the LMS according to one example embodiment of the inventive subject matter disclosed herein. LThe follow sections describe the structure of the server in more detail.
  • entity beans 210b are used to represent the following information in the configuration server 126: • All OSS configuration. items. Categories Components Catalogs Charge types
  • Data access objects may be used to actually read and write the configuration items to persistent storage.
  • DAO 210C Data access objects
  • the system may initially use a RDBMS, but might use an XML database in order to provide faster searching.
  • the delivered LMS product uses Oracle 9i as the DBMS, as described below.
  • Validation Updates to the entities invoke validation classes that ensure that the constraints on the configuration items may be satisfied. All validations adhere to a common interface. The validations are not a fixed set, but may be capable of being augmented by customers deploying the server. LThey are not statically specified, but may be dynamically located, so that the set of validations can be extended to suit customer requirements (providing validations for additional catalog extensions, for example). In some embodiments, this is achieved as follows: LThe session interface class that handles requests to update configuration (see further below) has an environment entry that specifies the validations. LThe validations may be specified as a list of environment references that can be looked up to locate additional session objects whose primary purpose is to validate configuration items.
  • the client session bean uses this interface. Additional validations may be added simply by registering new validation classes using the standard EJB deployment tools, and by adjusting the environment entry that specifies the home interfaces of these classes.
  • the configuration server 126 can be made to use these validations by writing validation classes that call appropriate validation logic in the various OSS components. These calls would be made as part of any change transaction. If they fail, the transaction would fail, and if the required OSS system was not available, the transaction would also not be able to proceed. Of course, other validations will be performed when the configuration change is published into each part of the OSS.
  • Session Facades Although entity beans exist for the configuration and catalog items, they are not accessed directly by any client. Instead, clients access the data through what is known as a "session facade". See the facade pattern in Design Patterns, Elements of Reusable 5 Object-Oriented Software, ISBN: 0-201-63361-2 and discussions of session facade in a J2EE context in J2EE Blueprints http://java.sun.comj2ee/blueprints/index.html and Core J2EE Patterns, Best Practices and Design Strategies, ISBN: 0-13-064884-1.
  • the session facade provides a business process interface to the configuration server 126 and catalog, while the entity beans map to the data elements.
  • Using session facades has 10 several advantages: LThe session can perform a number of create, read, update, and delete : . -. operations on behalf of a remote client, .reducing network traffic. LThe session serves as a transactional fa ade, ensuring that transactions occur on the server, rather than being managed by clients. 5 A full discussion of this design pattern can be found in (Core J2EE Patterns, Best Practices and Design Strategies, ISBN: 0-13-064884-1). LThe session facades access the CS entities using a local interface.
  • An important aspect of using a session facade to access the CS is that clients call the session or retrieve from the session value objects that represent the configuration items. This is in contrast to having direct access to the entity beans that represent the5 configuration item, or passing many arguments to the session beans 210a. See (J2EE Blueprints http://java.sun.com/j2ee/blueprints/index.html) for a discussion of value objects.
  • the value objects Are Serializable objects (so they can be used in method calls and return values).0 • Are representations of the entity beans (domain objects) of the configuration/catalog, and hence can be referred to as domain value objects.
  • Aggregate value objects are provided that contain multiple related value objects. E.g. a composite catalog which contains a catalog, all its categories, charge types, and components.
  • the session facade acts as a value object factory- that is, it creates value objects corresponding to configuration items and returns them to clients. It also updates configuration entities based on the value objects sent to it by clients.
  • the session facade may be a limited amount of client state required: • User locale information (for returned messages/errors). OSS authentication details for the user. , User licenses. ,, _
  • the business processes supported by the configuration server 126/catalog typically involve only a single method call to complete (i.e. they are not conversational). For this reason, the configuration server 126 session beans 210a may be stateless, apart from a bean that stores the limited amount of user state.
  • session beans 210a are created to group together logical groups of business processes.
  • session beans 210a are provided for the following groups of interactions: Configuration client interactions. Catalog client interactions. Administration interactions.
  • Figure 3 illustrates how the session beans 210a collaborate with the entity beans to perform the work required by a user interaction. The activities in 1.1 , 1.2, and 1.3 all occur within the same transaction.
  • Value list handlers may be used to handle search results efficiently. See (Core J2EE Patterns, Best Practices and Design Strategies, ISBN: 0-13-064884-1). LThey provide an easy to use interface for the client to iterate through search results, while ensuring that clients do not retrieve full results sets over the network when this might be unnecessary. LThey may be backed using stateful session beans 210a on the server, to hold the search results sets.
  • L The OSS systems cannot all participate in a single update transaction, due to the lack of 2 phase commit across the OSS. It may be desired to integrate use the routing and workflow facilities of some 3rd party message-oriented middleware component to integrate with other systems. Typically the message based notification mechanism cannot be synchronous, and must allow for the notifications to be stored in a persistent store when the systems to be notified may be unavailable. Other features that may be useful (or essential to a robust solution) include: The ability to filter notifications, so systems only receive notifications of interest to them. (LThis reduces network traffic). Transactional support for notifications: notifications may only be removed from the persistent store when the system has successfully processed them. The mechanism for performing these notifications may be the Java messaging service (JMS).
  • JMS Java messaging service
  • JMS is a messaging API that was originally designed to wrap existing message oriented middleware (MOM). Since its introduction a significant number of pure Java implementations of JMS have been provided. JMS is part of J2EE 1.3. By utilizing messaging in this way there may be created an appropriately looser coupling between the configuration server 126 and the other components. Using JMS also has another advantage in the OSS. JMS has been widely adopted by both newcomers to the MOM arena and established players. Where MOM is used in an OSS integration there may be a significant advantage in using a widely used and implemented mechanism.
  • EJB 2.0 introduced Message Driven Beans (MDB). These may be server side objects (that run in the EJB application server) that may be invoked by the server to handle messages delivered via JMS. The server may be responsible for the life cycle of the MDBs. Connecting MDBs with a particular JMS queue or topic is a deployment task, carried out by modifying the EJB deployment XML files.
  • MDB Message Driven Beans
  • JMS supports two types of communication: point-to-point and publish and subscribe. Publish and subscribe is the appropriate form for configuration change notifications: one notification maybe made available to multiple OSS systems and other interested clients. Message publishers write messages to a topic, and message consumers read messages from a topic. For reliable delivery of messages, JMS supports: Message persistence: messages, may be maintained in a persistent form until they have been processed by a message consumer.
  • Durable subscriptions JMS retains records of durable subscriptions and ensures thalall messages from the topics publishers may be retained until they may be acknowledged by the durable subscriber (even if the subscriber is temporarily unavailable), or until the messages expire (message expiry is specified when the message is created).
  • the parties that are interested in notifications referred to as listeners in this document.
  • Listeners may be used to describe clients or systems that are interested in changes to the configuration, but that do not need to participate in the configuration change process within the configuration server 126 (validating the change or applying it to an OSS component).
  • tools for editing the configuration may benefit from knowledge of changes to the CS content, but need not necessarily be guaranteed that they receive all updates. These are also not normally durable subscriptions - because the notifications are only required for the period when the configuration maintenance tool is actually being run.
  • Third parties may want to be notified about configuration changes. LThis can be achieved by registering to receive notifications. Notifications could then be sent as SOAP messages, delivered either by HTTP or via SMTP. Because acknowledgement of these notifications is not necessarily required, these maybe not guaranteed reliable notifications. If guaranteed notification was required there would be a need to provide mechanisms to re-send notifications that had not been acknowledged.
  • Message Structure and Content JMS allows for a variety of message formats including text, a map of name value pairs, bytes (i.e. some raw format), or serializable Java objects. Serializable objects may be used to communicate configuration item changes, and also to communicate audit records. (LJliis is described. further elsewhere in.the following with details of discussion of auditing).
  • the message contains a header that describes aspects of the message. In addition to the mandatory header content, message publishers can provide additional header fields. Since the updates may incorporate changes to a number of configuration items (the CS has been updated using the configuration export tool), the update messages incorporate details of changes to a number of configuration items. LThis may be required because there can be circular dependencies between configuration items. The listeners may therefore need to deal with the configuration as a group.
  • the messages contain the following information: Type of configuration entities changed. E.g. catalog details, category, or component. The IDs of the entities that have been changed. • LThe type of changes: create, update, delete.
  • the message consumers can receive a filtered set of the messages, by configuring message selectors.
  • the message selectors utilize a subset of the SQL92 expression syntax. This is apart of the JMS standard.
  • Publishers The components that push configuration changes into the OSS may be referred to as publishers. LThe publishers maybe implemented as session beans 210a. Essentially each publisher knows how to process configuration change method calls in order to update the OSS component for which it is designed. A publisher may only be interested in certain types of configuration changes. For example the CB 122 publisher may be only interested in CB 122 configuration items and not CM 124 configuration items or product catalog items. The publishers also provide support for validating configuration changes prior to the change being committed to the configuration server 126 database and being sent to all publishers.
  • LThe configuration server 126 supports ordering configuration changes so that the publisher for one system (e.g. CB) may be invoked before the publisher for another system (e.g. CM 124 ). LThe ordering policy can differ depending on the configuration item type.
  • the configuration server 126 records details of the configuration data stored by each publisher, including the OSS specific identifiers for configuration items.
  • An administration function can be used to locate these failed updates. LThe administrator can then deal with this situation as they see fit (e.g. remove the item if necessary, or correct whatever causes it not to be published in particular systems). The emphasis here is on providing mechanisms to find and fix errors, which should generally occur infrequently due to the validations that may be applied before committing any configuration.
  • the administration console described the Configuration GUI section herein, may be used to find these incomplete updates.
  • the publishers also support importing configuration from the OSS components that they handle, and reporting on the potential impacts of proposed configuration changes.
  • the configuration server 126 can import configuration from an OSS component and compare it with the copy that is stored within the configuration server 126 database. In this way a report of differences between the configuration server 126 copy of the configuration and the OSS is provided. LThis function may be accessible from the configuration server 126 administration console.
  • Oracle may be used to store the CS data. However, other similar databases can be used. XML databases can also be used for this purpose and may be desirable because of their support for validating XML and XML searching. Oracle provides a range of support for XML storage. See (Oracle 9i Application
  • XMLType has member functions you can use to access, extract, and query the XML data using XPath expressions.
  • XPath is another standard developed by the W3C committee to traverse XML documents.
  • Oracle XMLType functions support a subset of the W3C XPath expressions.
  • Oracle also provides a set of SQL functions (including SYS_XMLGEN and SYS_XMLAGG) and PL/SQL packages (including DBMS_XMLGEN) to create XMLType values from existing relational or object relational data.
  • XMLType is a system-defined type, so you can use it as an argument of a function or as the data type of a table or view column.
  • Oracle internally uses a CLOB to store the actual XML data associated with this column. As may be true for all CLOB data, you can make updates only to the entire XML document.
  • the authentication mechanisms available in an EJB application server may be vendor specific.
  • the Java authentication and authorization service (JAAS) provides APIs for authentication and authorization, and supports pluggable authentication modules. It is an extension in J2SE 1.3, and fully integrated in J2SE 1.4. See JavaTM Authentication and Authorization Service (JAAS) Reference Guide http://java.sun.eom/j2se/l .4/docs/guide/security/jaas/J AASRefGuide.html for coverage of JAAS.
  • J2EE vendors may not be required to support it, and at this time only some do.
  • J2SE 1.4 there are login (authentication) modules for: JNDI: Can obtain login username/password from a directory service available via JNDI (e.g. LDAP). Kerberos • NT login Unix login Using a keystore. It is possible to support single sign-on using Kerberos, as described in Single Sign-on Using Kerberos in Java http://java.sun.eom/j2se/l.4/docs/guide/security/jgss/single-signon.html.
  • the configuration server 126 defers to the application server for provision of authentication services.
  • Specific support may be provided for using JAAS for authentication when running the configuration server 126 under WebLogic server.
  • Authorization In the J2EE architecture, the EJB and servlet containers act as authorization boundaries between callers, and the components that they host. Permission based access control may be supported by compliant EJB and servlet containers.
  • LThe deployment descriptor defines logical security roles and associates them with components (web resources (servlets), bean methods) to define the privileges that may be required to access components.
  • the application assembler and deployer can use the declarative EJB deployment descriptors to define: • .. - . - The privileges required to access components. LThe correspondence between the security attributes presented by callers ___ .. and the container privileges.
  • Additional programmatic authorization can be performed in an EJB by obtaining the role of the caller, via a standard API. LThe declarative authorization mechanisms of *
  • EJB 2.0 may be sufficient to support the authorization requirements specified for LMS (along with appropriate API design for the session beans 210a). Future requirements, e.g. for B2B partners accessing the catalog, may necessitate programmatic authorization • checks as well and data-level authorization.
  • the configuration server 126 may be packaged with deployment descriptors that specify roles for the API that will be appropriate for most deployments. Additional programmatic authorization checks may be performed for create/update/delete operations to ensure that users have appropriate create/update/delete roles.
  • Auditing J2EE containers may not be required to provide auditing facilities, and there may not be any standard auditing interfaces for containers to implement. Generally those that do provide auditing facilities actually normally only provide a basic level of functionality, namely logging security exceptions (authorization failures) and successful and unsuccessful authentications. For this reason facilities were created in the configuration server 126 in some embodiments. Audit records may be written to a database table in the configuration server 126 database. (Notifications of the audit events may also be sent via JMS, as further described herein). The table contains: The type of the configuration entity updated. The id of the entity updated. The type of operation (create, update or delete). LThe date/time at which the change was made. • . The XML representation of the item before (and after) the update.
  • the administration session bean provides an ALPI or reading audit records.
  • The" administration console provides commands for searching for and viewing audit records.
  • Locking The configuration server 126 supports locking of configuration. LThis is intended to allow a single configuration server 126 and related OSS components to be effectively used by a team of configuration developers. LThe server can be set to require that a user must have a lock on any data that they wish to update in the configuration server 126 before the update will be allowed to proceed. LThis includes updates sent to the server by a client as well as updates to configuration via importing from an OSS component. Details of the locks on configuration items may be stored in the configuration server 126 database.
  • LThe session beans 210a described in the Configuration Server section herein provide APIs for user level changes to locks (lock and unlock items) and' administrative access to locks (revoke and reassign locks).
  • CB 122 can be made to enforce the locks maintained by the configuration server 126. This may be achieved via database commit triggers on the CB 122 tables which in turn query the configuration server 126 to determine if the updates should be allowed to proceed.
  • Configuration Translation and Generation In order to support the mapping of product dat to low level CB 122 and CM 124 configuration, the configuration server 126 supports translating or generating configuration. LThe set of configuration generators is extensible.
  • a configuration generator may be provided that uses XSLT stylesheets to perform the mapping.
  • the stylesheets may be stored in the configuration server 126 database, in much the same way as other configuration items.
  • a single stylesheet can product multiple configuration items.
  • Stylesheets can source other configuration items from the configuration server 126 database. This may be achieved by providing a special XML * resolver that understands how to locate items in the configuration server 126 database. LThis resolver can also obtain old versions of configuration items. An extension function may be provided for searching the configuration server 126 database for configuration items that match specific (XPath) criteria.
  • stylesheets may be provided for translating product catalog XML into CB 122 and CM 124 configuration suitable for use in a system using the EICP and CCITG configurations. Sample stylesheets may also be provided for some demonstration content-type products.
  • Execution Environment The configuration server 126 component requires the following execution environment: A system with the JRE version 1.3.1 or later. • A J2EE server, supporting version 1.3 of the J2EE specification. A J2EE server supporting JAAS for authentication and authorization.
  • WebLogic Server 7.0 is the only certified J2EE server for initial release. EJB clients of the configuration server 126 require the following execution environment: - A system with J2SE version 1.4.1 or later.
  • the workbench 144 component is a GUI for creating, updating, deleting and viewing product definitions. It is intended, in one example embodiment, to reduce the complexity of product management. While the workbench 144 may be the only GUI component specified in on example embodiment for the LMS, future versions of the LMS may include GUIs for maintaining many other configuration items. The architecture takes this into account, by building on a framework into which other configuration management UI components can be added.
  • the LMS provides a GUI for performing import/export of configuration between repositories, searching configuration, configuration editing, and version control operations.
  • LThis is called the configuration tools GUI.
  • the workbench and configuration tools GUI 144 may be built on the NetBeans Open IDE framework, as depicted in Figure 5.
  • LThe figure depicts a system composed of a number of related modules 500, including Netbeans modules 510, product catalog modules 520, infrastructure modules 530 and configuration server modules 540. All run on top of the NetBeans OpenAPI framework.
  • Modules 510 include a version control module 510a, a XML editor 510b, a Diff module 510c and a utilities module 51 Od.
  • Modules 520 include catalog datatypes 520a, catalog wizards 520b and business user interface 520c.
  • Modules 530 include configuration datatypes 530a, wizards 530b, branding 530c, help 530d, libraries 530e, groups 530f, synchronization 530h, and searches 530i.
  • Modules 540 include CS file system 540a, CS administration 540b and configuration server communications 540c.
  • LThe NetBeans Open IDE framework provides the following core facilities: Modules: Allows modular development of functionality, and plugging it into the framework. Modules can add items to menus, toolbars, help, add support for recognizing new types of files and actions appropriate to those, such as new edit components. LThis makes the configuration UI extensible.
  • FileSystems Abstract from access to file systems. Can be used to represent data retrieved from configuration server or configuration repository.
  • Data Types Recognition of types of data. Nodes: Used to represent data elements (configuration items, products, categories etc) and attach appropriate actions to them based on data type.
  • Explorer Used to easily develop explorer interfaces, in conjunction with the nodes API.
  • Actions Add menu and toolbar items for performing actions on the configuration items.
  • Editor An editor may be built-in.
  • Window System Provides window management facilities. Allows the user to run the application in multiple document interface or single document interface mode. Options: Provides a mechanism for specifying configuration items for modules.
  • Utilities Various useful utility classes.
  • Netbeans Modules 510 Several of the standard Netbeans modules 510 may be included in the release of the configuration tools GUI or workbench. These may be: Version control modules 510a: which provide support for CVS, and a generic VC system support that can be used to access configuration repositories.
  • Version control modules 510a which provide support for CVS, and a generic VC system support that can be used to access configuration repositories.
  • XML module 51 Ob Which provides support for editing and validation of ' • • • -. ⁇ - . . XML. - • Editor module 51 Ob: Useful for editing HTML or text documents which could accompany configuration. • Diff module 150c: Which provides support-for comparison of files.
  • Utilities module 51 Od Which provides support for searching files.
  • the configuration tools GUI and workbench contain a number of modules that may be useful with all configuration data to be handled by the LMS, rather than just the product data. They may be: Configuration item datatypes module 530a: Provides support for recognizing flavors of XML. Configurable searches module 53 Oi: Provides support for searching for configuration items containing specific data. Configurable wizard module 530b: Provides a framework for specifying wizard interfaces, using XML. Grouping module 53 Of: Provides facilities for specifying groups of configuration data, and performing actions on the groups of configuration data. Synchronization module 530g: Provides support for synchronizing files between repositories. Taskbar module 530h. These modules are described in more detail in the following sections.
  • the configuration item datatypes module provides support for reco nizing the various types of XML configuration item. It is then possible to associate appropriate icons and actions with the datatypes, and wizards suitable for editing the types of data. This module also provides support for searching for specific types of configuration item.
  • the datatypes module provides the ability to show the references between configuration items in explorer views, and to create and delete references. There is also support for finding items that contain references to other items that do not exist in the repository.
  • Configurable Search Module 530i LThe configurable search module provides support for searching for particular configuration items based on their content. (LThe NetBeans utility module provides the ability to search based on simple text content, modification date, and version control status). LThis search allows users to search for named fields in the configuration XML containing specified values. (Or starting or ending with specified values, or matching a regular expression). The searches may be implemented using XPath. The displayed names of the searches, fields and XPath expressions may be specified in XML configuration files.
  • the Configurable Wizards Module 530b provides support for defining wizards.
  • the wizards are intended to create or modify XML for configuration entities.
  • the creation or update of configuration XML for a particular type of configuration item may be basically viewed as involving the following activities: 1. Collecting sufficient information to describe the required configuration. 2. Placing that information in the required XML structure. 3. Saving that configuration data, exporting the data to the OSS, or sending the data to a server via API calls.
  • the data to be collected may be described in a wizard definition.
  • the definition contains steps, which in turn contain fields.
  • Each field represents an XML fragment, as does a wizard.
  • a wizard can be used as sub-wizards, or initiated from other wizards to build up complicated XML).
  • these fields and sub-wizards provide arbitrary XML fragments that can be composed, with the aid of a template, to create the desired XML.
  • the output XML may need to contain values derived from the XML " fragments collected, and this may be done by applying expressions to the collected fields. LThis may be done using expression languages.
  • the primary supported expression language may be XPath, an expression language specifically designed for dealing with XML See XPath Specification at http://www.w3.org/TR/xpath. It would be possible to add support for other scripting languages that run in a JVM. For example, JavaScript, Python, etc - see list of scripting languages available for Java: http://grunge.cs.tu- berlin.de/ ⁇ tolk/vmlanguages.html. Wizards vary their behavior based on information that has been previously entered. LThis may be accomplished by skipping steps or sub-wizards based on expressions (using the built-in expression support) calculated from previous inputs. Input data may be validated at the field, step and wizard level.
  • Validations may be either plugged in Java classes that conform to an interface, or classes that implement their validation using one of the supported expression languages.
  • T L he wizard definition must includes additional information: Display names and descriptions for the wizards, steps and fields. It may be possible to translate these into multiple languages and render the wizard using the users language of choice. • Help details for the wizards, steps and fields so that appropriate online help can be displayed.
  • LThis may be achieved by plugging in a Java class that conforms to a standard interface. For the product builder, classes may be provided to save the XML to a repository.
  • the grouping module builds on the datatypes, searches and wizard modules. It provides: - Support for recognizing group XML files. Support for viewing the items referenced by groups and actions to add and remove items from a group. - Wizards for creating and editing groups. Searches for finding groups containing specific data.
  • the synchronization module provides a wizard that allows users to synchronize some or all of the configuration held in two different configuration repositories. It allows the user to select the repositories to be synchronized, and presents them with explorer views containing the contents of each repository and a merged view that indicates the differences between the repositories. Using these view users can select configuration to be synchronized. The ability to search for configuration or select configuration that the user has locked, or simply all configuration data that differs between the repositories may be also provided.
  • Taskbar Module 530h The taskbar module provides a simple to use interface for launching tasks such as creating a product catalog or catalog item, or searching for a particular item.
  • a product catalog specific module provides actions that appear in the taskbar.
  • Product catalog modules 520 The following modules implement the remainder of the functionality supported by the workbench 144: Product catalog datatypes module 520a. • Product catalog wizards module 520b
  • the product datatypes module contains the configuration required to recognize the product catalog configuration items using the datatypes module. That is, the catalog, category, charge type and component configuration items.
  • LThe product catalog datatypes module provides actions associated with the product catalog datatypes, including the ability to launch a catalog explorer view. " This may be an explorer view with an attached property sheet. LThe explorer view has product catalogs as root elements. It allows users to view the associated product categories and products (components) and charges as children of the catalog. Details of items selected in the explorer view as shown in the property sheet.
  • the product catalog wizards module contains the XML files that specify the wizards for manipulating CI data.
  • sample wizards for editing some types of EICP products may be provided.
  • Configuration Server Modules 540 L The following modules implement the client functionality for accessing and managing the configuration server: Configuration server file system module 540a configuration server administration module 540b
  • the configuration server file system module 540a represents the contents of the configuration server 126 as a virtual file system (or repository), in the same way that other repositories such as CVS or local directories may be presented to the user. LThis allows users to examine the server contents via an explorer view (of folders and files) and to copy and paste configuration data between repositories.
  • the configuration server file system annotates configuration items with their status in the server (such as revision number and lock details). It may be kept in sync with the server by responding to configuration change notifications sent by the server. It caches the server contents locally to avoid repeated fetches of the same data from the server.
  • the file system module 540a makes use of the client stubs and business delegates for calling the configuration server 126.
  • the configuration server administration console may be launched via an action provided in the configuration server file system module 540a. It provides a user-interface for administration of various aspects of the configuration server 126. It should be noted that tools for administration of the application may be split based on the lines of responsibility for provision of services. That is, many services may be provided by the application server, or by other servers (such as an LDAP or Kerberos server providing user authentication support). Management of these "parts" of the configuration server 126 may be performed using whatever tools are provided by the vendors the supply these components. No attempt has been made to wrap their functionality in an over-arching management user interface.
  • the administration console 540b provides what may be essentially a command line interface (albeit in a GUI window).
  • LThe commands it supports include: • LThe capability to view the contents of the configuration server 126 (files and revisions), and the updates that have been applied to the server. LThe ability to update configuration stored in the server. LThis includes updating from local files and updating from the OSS. LThe ability to update the OSS from the data stored in the server. • LThe capability to find and view audit records stored in the server. The ability to modify various server settings: e.g. trace, locking, auditing, server name and description. LThe ability to obtain composite product catalog definitions. LThe ability to lock and unlock configuration items. • Update the set of stylesheets used for configuration generation. Set the update ordering that controls the order that configuration is sent to the various publishers.
  • the configuration server console can also be run standalone in a terminal window. LThis version may be packaged with the configuration server 126.
  • Execution Environment L The configuration tools GUI and workbench components require the following execution environment: - A system with the J2SE version 1.4.1.
  • License Management Licensing information may be specified for both the client GUIs and configuration server 126.
  • the client licensing may be on a module basis.
  • the server licensing may restrict the number of connected users, the systems that a configuration server 126 can be connected to and the features of the configuration server 126 that clients can use.
  • License information may be encapsulated in an XML file format, which may be cryptographically signed to prevent tampering.
  • the license file In the GUIs the license file may be read, and modules may be enabled/disabled based on its contents. Clients must have a copy of a valid license in the installation directory of the client.
  • LThe configuration server 126 may communicate with a separate license process. LThis may be a separate process that counts connected users across multiple instances.
  • a single license server can be used for multiple configuration servers 126.
  • LThe configuration server 126 may communicate with the license manager via remote method invocation, and obtain a handle to the license manager via the Java naming and directory interface.
  • clients when clients connect to the configuration server 126 they request the client licenses that they need (basic configuration license or product catalog license).
  • LThe server also checks the license when publishers are invoked to import/export configuration.
  • Execution Environment L The license server requires the following execution environment: A system with the J2SE version 1.3.1.
  • RelGen RelGen is a release management system. It manages items that are to be included in a release, and creates a release package that includes these items or the deliverable items created from the managed items. RelGen maybe used to release CB 122 configuration. It uses the CB 122 archiver. RelGen is, in one example embodiment, adapted to support: Releasing configuration in XML format from a version control system (CVS) or local file system. This may be implemented via RelGen plugin modules. - Installing configuration in XML format via a configuration server 126. Release of configuration as a CB 122 archive by first loading the configuration into CB 122 via a configuration server 126. Supporting the use of group files to select configuration to be released.
  • CVS version control system
  • RelGen may be written in Perl the implementation of these RelGen plugins requires that the configuration server 126 API and configuration groups API described in the Configuration Server section herein and be made available in Perl. LThe Perl wrappers for the Java APIs are implemented using JPL.
  • One possible modification to the NetBeans CVS module may provide hooks that can be used to update the RelGen database when configuration items are committed to CVS.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Stored Programmes (AREA)
  • User Interface Of Digital Computer (AREA)
  • Digital Computer Display Output (AREA)
  • Machine Translation (AREA)

Abstract

Une suite de gestion du cycle de vie (LMS), selon un mode de réalisation présenté à titre d'exemple, comprend un magasin de données, un serveur, des données orientées fichier et des composants d'outils de configuration. Des interfaces de programmation API existent dans les composants de systèmes de soutien à l'exploitation OSS de gestion client et de facturation convergente (CB) pour la manipulation de la configuration. La nature des API change entre ces systèmes et dépend de l'article de configuration, mais ces API permettent de créer, mettre à jour, supprimer ou rendre désuets des articles de configuration dans ces systèmes. Ces API peuvent être néanmoins de bas niveau et traitent la configuration en termes de composants OSS. La fonction globale des outils de configuration consiste à fournir des articles de configuration de niveau plus élevé, tels que des articles de catalogue de produits de haut niveau (couvrant les multiples composants OSS), ou des polices de configuration et des articles de configuration composites. Le serveur de configuration mémorise ces représentations de configuration de niveau supérieur. Il peut être utilisé pour rechercher la configuration dans les composants OSS et pour la mettre à jour. Il envoie des messages aux composants OSS lorsque les données de configuration sont mises à jour. Des outils pouvant extraire la configuration de ces systèmes sont prévus, sous une forme externe orientée fichier, dans laquelle elle peut être manipulée facilement au moyen d'outils de fichier et pour charger la configuration de sa représentation orientée fichier vers les composants OSS. Ces derniers font partie de l'interface utilisateur des outils de configuration. Ces outils interagissent avec les composants OSS par l'intermédiaire du serveur de configuration. Afin de gérer la configuration de manière efficace, des outils de commande de version peuvent être fournis. Ils sont appliqués à la représentation/données orientées fichier de la configuration. Ils comprennent des outils de base pour conserver les changements apportés à la configuration, visualiser les différences de configuration, grouper les articles de configuration à des fins de commande de version. Afin de permettre le développement de produits rapidement et simplement, un outil de développement sur banc de travail peut être fourni. Cette application GUI peut fonctionner, soit séparément d'une représentation orientée fichier des définitions de produit, soit par communication avec le serveur de configuration, par l'intermédiaire de ses API.
PCT/US2004/038970 2003-11-26 2004-11-19 Systemes, procedes et logiciel pour configurer et gerer un systeme de telecommunication WO2005054987A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP04811659A EP1687691A2 (fr) 2003-11-26 2004-11-19 Systemes, procedes et logiciel pour configurer et gerer un systeme de telecommunication

Applications Claiming Priority (12)

Application Number Priority Date Filing Date Title
US52533103P 2003-11-26 2003-11-26
US10/723,246 2003-11-26
US10/723,243 2003-11-26
US10/723,612 US20050114692A1 (en) 2003-11-26 2003-11-26 Systems, methods and software to configure and support a telecommunications system
US10/723,246 US20050114642A1 (en) 2003-11-26 2003-11-26 System and method for managing OSS component configuration
US10/723,581 2003-11-26
US10/723,243 US20050114851A1 (en) 2003-11-26 2003-11-26 System and method for configuring a graphical user interface based on data type
US10/723,612 2003-11-26
US10/723,582 US20050114240A1 (en) 2003-11-26 2003-11-26 Bidirectional interfaces for configuring OSS components
US60/525,331 2003-11-26
US10/723,582 2003-11-26
US10/723,581 US20050114479A1 (en) 2003-11-26 2003-11-26 System and method for hierarchically representing configuration items

Publications (2)

Publication Number Publication Date
WO2005054987A2 true WO2005054987A2 (fr) 2005-06-16
WO2005054987A3 WO2005054987A3 (fr) 2007-07-19

Family

ID=34658299

Family Applications (5)

Application Number Title Priority Date Filing Date
PCT/US2004/039107 WO2005054989A2 (fr) 2003-11-26 2004-11-19 Interfaces bidirectionnelles permettant de configurer des composants de systemes de soutien a l'exploitation (oss)
PCT/US2004/038763 WO2005055561A2 (fr) 2003-11-26 2004-11-19 Systeme et procede de gestion de la configuration de composants de systemes de support d'operations
PCT/US2004/038970 WO2005054987A2 (fr) 2003-11-26 2004-11-19 Systemes, procedes et logiciel pour configurer et gerer un systeme de telecommunication
PCT/US2004/039082 WO2005054988A2 (fr) 2003-11-26 2004-11-19 Systeme et procede de configuration d'une interface utilisateur graphique en fonction d'un type de donnees
PCT/US2004/038835 WO2005055491A2 (fr) 2003-11-26 2004-11-19 Systeme et procede pour representation hierarchique d'articles de configuration

Family Applications Before (2)

Application Number Title Priority Date Filing Date
PCT/US2004/039107 WO2005054989A2 (fr) 2003-11-26 2004-11-19 Interfaces bidirectionnelles permettant de configurer des composants de systemes de soutien a l'exploitation (oss)
PCT/US2004/038763 WO2005055561A2 (fr) 2003-11-26 2004-11-19 Systeme et procede de gestion de la configuration de composants de systemes de support d'operations

Family Applications After (2)

Application Number Title Priority Date Filing Date
PCT/US2004/039082 WO2005054988A2 (fr) 2003-11-26 2004-11-19 Systeme et procede de configuration d'une interface utilisateur graphique en fonction d'un type de donnees
PCT/US2004/038835 WO2005055491A2 (fr) 2003-11-26 2004-11-19 Systeme et procede pour representation hierarchique d'articles de configuration

Country Status (2)

Country Link
EP (5) EP1706805A2 (fr)
WO (5) WO2005054989A2 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9531589B2 (en) 2014-05-30 2016-12-27 Cisco Technology, Inc. Automating monitoring using configuration event triggers in a network environment
CN113656347A (zh) * 2021-08-17 2021-11-16 成都统信软件技术有限公司 文件目录导出方法、文件目录导入方法及计算设备

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB9603582D0 (en) 1996-02-20 1996-04-17 Hewlett Packard Co Method of accessing service resource items that are for use in a telecommunications system
US7240068B2 (en) * 2002-09-06 2007-07-03 Truetel Communications, Inc. Service logic execution environment (SLEE) that is running on a device, supporting a plurality of services and that is compliant with a telecommunications computing standard for SLEES
US7803203B2 (en) * 2005-09-26 2010-09-28 Cabot Microelectronics Corporation Compositions and methods for CMP of semiconductor materials
US9122719B2 (en) * 2006-04-28 2015-09-01 Bmc Software, Inc. Database application federation
US8238538B2 (en) 2009-05-28 2012-08-07 Comcast Cable Communications, Llc Stateful home phone service
US8671036B2 (en) * 2009-11-06 2014-03-11 Microsoft Corporation User interface for defining account dimension combinations
US11611473B2 (en) 2014-01-14 2023-03-21 Zixcorp Systems, Inc. Provisioning a service using file distribution technology
US11436197B2 (en) * 2020-07-29 2022-09-06 Zixcorp Systems, Inc. Asynchronous method for provisioning a service using file distribution technology

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6154738A (en) * 1998-03-27 2000-11-28 Call; Charles Gainor Methods and apparatus for disseminating product information via the internet using universal product codes
US20030158919A1 (en) * 2002-02-20 2003-08-21 Sun Microsystems, Inc., A Delaware Corporation Method for deploying version control system server software having remote access capability
US20040194069A1 (en) * 2003-03-27 2004-09-30 Surasinghe Lakshitha C. System and method for dynamic business logic rule integration

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5175800A (en) * 1987-03-23 1992-12-29 Case Group Plc Expert and data base system and method for communications network
US5103421A (en) * 1988-11-29 1992-04-07 Massachusetts Institute Of Technology Process and apparatus for designing a system made of components
US5579384A (en) * 1995-02-17 1996-11-26 Bellsouth Corporation Telecommunications network service central management system interfacing with protocol specific regional stations providing services to subscribers
US5805602A (en) * 1995-09-25 1998-09-08 Bell Atlantic Network Services, Inc. Network monitoring system for cell delay variation
US6772396B1 (en) * 1999-10-07 2004-08-03 Microsoft Corporation Content distribution system for network environments
US6449624B1 (en) * 1999-10-18 2002-09-10 Fisher-Rosemount Systems, Inc. Version control and audit trail in a process control system
US7150037B2 (en) * 2001-03-21 2006-12-12 Intelliden, Inc. Network configuration manager
US6889172B2 (en) * 2001-08-15 2005-05-03 National Instruments Corporation Network-based system for configuring a measurement system using software programs generated based on a user specification
US20040205562A1 (en) * 2001-12-27 2004-10-14 G.E. Information Services, Inc. System and method for transforming documents to and from an XML format
US7082460B2 (en) * 2002-04-19 2006-07-25 Axeda Corporation Configuring a network gateway
US20050089027A1 (en) * 2002-06-18 2005-04-28 Colton John R. Intelligent optical data switching system
US8073935B2 (en) * 2002-07-25 2011-12-06 Oracle America, Inc. Pluggable semantic verification and validation of configuration data
US7398307B2 (en) * 2003-04-30 2008-07-08 Hewlett-Packard Development Company, L.P. Method and system for managing a network
US7444376B2 (en) * 2003-05-22 2008-10-28 Hewlett-Packard Development Company, L.P. Techniques for creating an activation solution for providing commercial network services
US20050091346A1 (en) * 2003-10-23 2005-04-28 Brijesh Krishnaswami Settings management infrastructure

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6154738A (en) * 1998-03-27 2000-11-28 Call; Charles Gainor Methods and apparatus for disseminating product information via the internet using universal product codes
US20030158919A1 (en) * 2002-02-20 2003-08-21 Sun Microsystems, Inc., A Delaware Corporation Method for deploying version control system server software having remote access capability
US20040194069A1 (en) * 2003-03-27 2004-09-30 Surasinghe Lakshitha C. System and method for dynamic business logic rule integration

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9531589B2 (en) 2014-05-30 2016-12-27 Cisco Technology, Inc. Automating monitoring using configuration event triggers in a network environment
CN113656347A (zh) * 2021-08-17 2021-11-16 成都统信软件技术有限公司 文件目录导出方法、文件目录导入方法及计算设备
CN113656347B (zh) * 2021-08-17 2023-12-05 成都统信软件技术有限公司 文件目录导出方法、文件目录导入方法及计算设备

Also Published As

Publication number Publication date
EP1687691A2 (fr) 2006-08-09
EP1687925A2 (fr) 2006-08-09
EP1706805A2 (fr) 2006-10-04
WO2005054988A2 (fr) 2005-06-16
EP1716493A2 (fr) 2006-11-02
WO2005055491A3 (fr) 2006-12-07
WO2005055561A2 (fr) 2005-06-16
WO2005054989A2 (fr) 2005-06-16
WO2005055491A2 (fr) 2005-06-16
WO2005054987A3 (fr) 2007-07-19
WO2005054988A3 (fr) 2007-06-07
WO2005054989A3 (fr) 2006-05-11
EP1687731A2 (fr) 2006-08-09
WO2005055561A3 (fr) 2006-03-09

Similar Documents

Publication Publication Date Title
US10324690B2 (en) Automated enterprise software development
US7895566B2 (en) System and method for building a deployable component based application
US7941784B2 (en) System and method for generating component based applications
Ferguson et al. Service-oriented architecture: Programming model and product architecture
US8086995B2 (en) System and method for flexible visual representation of device fonts
US20060248121A1 (en) System and method for supporting packaging, publishing and republishing of wireless component applications
US20050114692A1 (en) Systems, methods and software to configure and support a telecommunications system
US20050114240A1 (en) Bidirectional interfaces for configuring OSS components
EP1687691A2 (fr) Systemes, procedes et logiciel pour configurer et gerer un systeme de telecommunication
CA2538861C (fr) Systeme et methode de creation d'une application deployable basee sur les composantes
US20050114642A1 (en) System and method for managing OSS component configuration
EP1712995B1 (fr) Système et méthode pour supporter l'assemblage, la publication et la re-publication d'applications sans fil à composantes
Srinivasmurthy et al. Web2exchange: A model-based service transformation and integration environment
Wetherbee et al. Beginning EJB 3: Java EE 7 Edition
Judd et al. Pro Eclipse JST
Lloyd et al. Expresso developer’s guide
Dallermassl Aspects of integration of heterogenous server systems in Intranets: the Java approach
Gilda et al. JBoss Enterprise Application Platform 6 Development Guide
Kozakov et al. OSGi Enablement in UIMA Framework
Hasegawa Oracle Fusion Middleware Migration Guide for Oracle Application Integration Architecture, 11g Release 1 (11.1. 1.4. 0) E17361-02
Annex GCSS-AF
Bandy et al. Oracle Application Server Concepts, 10g Release 2 (10.1. 2) B13994-02
Davies et al. Administration, Operations, and Management
Block Other Application Blocks and Advanced Configuration
Franchitti Application Servers G22. 3033-011

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2004811659

Country of ref document: EP

NENP Non-entry into the national phase in:

Ref country code: DE

WWW Wipo information: withdrawn in national office

Country of ref document: DE

WWP Wipo information: published in national office

Ref document number: 2004811659

Country of ref document: EP