Chapter 8   Service Deployment


Services that involve message interaction between one machine and another can be deployed by configuring them in terms of their class files that determine message protocol, the java code that defines the service itself together with some rulesets that define various authorisation mechanisms and a "tbasesvc.properties" file that allows the user to define configuration options for that particular service.

Overview of Deploying a Service

Deploying a service can involve any number of configuration features depending on what kind of service you have to build. Sometimes it may involve defining your own configuration options and in such circumstances you may wish to configure a Template option. In other cases you may require authenticating that service in which case you will have to select your Authorisation options.

Figure 8-1    Service Main Menu

There are essentially two main requirements for deploying a service:

• You deploy it by loading the services jar file into iPlanet Trustbase Transaction Manager.

• You then assign a role to authenticate the service, if necessary.

  
  

  ---

  Note

  Developing a service prior to deploying it involves a number of steps. Create your DTD definitions that specify the syntactic structure of the messages you wish to send round the system. These DTD's are thrown away once the class files are generated and messages are interpreted from the class files themselves. This has two main benefits: (a) its faster (b) its easier to develop. Use Classgen com.iplanet.trustbase.app.classgen.ClassGen to generate your java classes from your DTD definitions. Write the Java code for the service deploying the Identrus API that assists the Identrus processing and validating of messages, certificates, keys and digital signatures. Deploy the service within iPlanet Trustbase Transaction Manager by selecting the relevant configuration options as described below in this guide. Finally, once it has been deployed within iPlanet Trustbase Transaction Manager itself you can run your service. See the Developer Guide for more information on this.

  ---

  
  

Deploying

• You deploy it by selecting <Services><Deployment>

Figure 8-2    Service Deployment

• The attribute and value details are used during message routing to determine if a message should be routed to this service. If a particular message has an attribrute of the correct type and value then routing is passed to the service (or its corresponding rules).

• The Service is the service name

• The Version is the version of the service that is user defined

• The class is the main calling program

• The jar file that contains the service itself with all its associated data.

The service itself contains a jar file, placed in /opt/Trustbase/TTM/V2.2/deploy that has a list of classes that contain the java code associated with the service, the java code that defines the service and a .properties file that defines how the service should be configured. This is illustrated below.

Figure 8-3    Example jar file of service being deployed

• Figure 8-4 below illustrates a sample output from deploying a service. The effects of deploying a service only occur when iPlanet Trustbase Transaction Manager has been restarted.

Figure 8-4    Service Deployment Results

Authorisation Services

If it requires Authorisation you'll need to:

• Add the service by selecting <Add Service>

Figure 8-5    Add Service

• Create a new role for this service by selecting <Add Role>

Figure 8-6    Add Role

• Define some users for this role

Figure 8-7    Add User

• Make sure you select <Add> once you've allocated a role to a user

• Select <Submit>

• Add Certificate and associated Role

Figure 8-8    Add Certificate

• Make sure you select <Add> once you've allocated a role to a user

• Select <Submit>

Services not requiring Authorisation

---

If the service you wish to deploy does not require authorisation simply select the <services> <deployment> and don't follow the procedure to assign a role for the service.

Registered Services

---

Finally, you can see which services have been deployed by selecting <Services> <Service Registry> as illustrated below.

Figure 8-9    Service Registry