WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Configuring Parlay applications to behave as managed objects

The components and applications managed by the Application Manager are called managed objects. Every application that needs management events from the Application Manager must define a stateless bean implementing the ManagedObjectOperations interface. The bean must be deployed with a predefined JNDI name format. When this is done, the application becomes a managed object.

The Application Manager maintains the list of managed objects–that is, the list of Parlay applications that implement the ManagedObjectOperations interface–to which it will send the management events.

In previous versions of Telecom Web Services Server (through version 6.2), a list of EJB references was attached to the Application Manager deployment descriptor to provide EJB references to these managed object EJBs.

In Telecom Web Services Server version 7.1, the Application Manager looks for managed objects using a JNDI tree that has a specific namespace. The JNDI namespace for each managed object is in the following format:ejb/WAST/Application/sequence_number/parlay_connector_name/application_name/remote_interface_name

where

When a Parlay application defines a stateless EJB that is a managed object, it will define the JNDI name of the EJB using this format. The JNDI name should include the name of the Parlay Connector, which can be unique for each Parlay Connector instance. This enables the Application Manager to find all of the stateless EJBs that are managed objects for a given instance of the Parlay Connector.

The list of managed objects is displayed in the Parlay Administration Console when the Parlay Connector application EAR file has been started. It is always preferable to start the Parlay application EAR files before starting the Parlay Connector application EAR file. That way, the managed object registrations are complete and can be detected by the Application Manager.




Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.