Configuration Components
From GCube System
Revision as of 23:22, 1 June 2008 by Manuele.simi (Talk | contribs) (→Profiles, JNDIs & Descriptors)
[coming soon]
Contents
Configure What?
[coming soon]
Profiles, JNDIs & Descriptors
[coming soon]
JNDIs
Each context can be configured with a JNDI section automatically loaded by gCore. Following the stack of contexts, we can configure:
- the GHN Context
- the Service Context
- the port-type Context
While the first one is global for each node and its configuration is under the GHN manager responsibility, the others are service-specific and MUST be taken into consideration when developing a new gCore compliant service. Per each service, there are:
- one and only one ServiceContext
- several port-type Contexts, depending on the service architecture and needs
Both the Service Context and the port-type Contexts can be configured with a dedicated service
element in the file called deploy-jndi-config.xml and placed in the etc folder under the service location.
Configuring the ServiceContext
The ServiceContext....
It is initialised by the GCUBEStartupPortType when ...