| Summary | Use the deployment descriptor to check the services deployed in an Orbix environment. |
|---|---|
| Article Number | 29241 |
| Environment | Orbix 6.x All Supported Platforms |
| Question/Problem Description |
How is it possible to check what Orbix services are configured, and on which machines they run? |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | |
| Resolution | The Orbix deployment descriptor lists the Orbix services which are deployed, and the hosts and ports on which they are deployed. Some services run on a random port, in this case the port will not be given. The deployment descriptor is contained in a file named <domain name>_dd.xml. This file is generally located in the directory <orbix install>/etc/domains/<domain name>. If you are running in a CFR environment then you can also list the contents of the domain descriptor by using the command: itadmin variable show deployer:descriptor In this file, each dd:profile tag has an id attribute which references the host that this section of the document correspond to. Inside each dd:profile tag are listed the services running on a certain host machine. The dd:service tags reference each individual service. If a dd:service tag contains a dd:endpoint tag then this service will run on the port referenced by the port attribute, if this does not exist it will start on a random port. The endpoint tag also defines the protocol as referenced by the protocol attribute. By looking at the protocol we can see if a port is using secure communications (iiops) or not (iiop). Each service may contain multiple endpoints. |
| Workaround | |
| Notes | Here is an example domain descriptor with the services cfr, locator, node daemon and a naming service which will be launched by the node daemon:
<?xml version="1.0" encoding="UTF-8"?>
<dd:descriptor xmlns:dd="http://ns.iona.com/orbix/schema/dd/1.2">
<!--This deployment descriptor version 1.2.0 has been generated by Orbix tools-->
<dd:configuration>
<dd:domain>sample-domain</dd:domain>
<dd:source>cfr</dd:source>
<dd:location_domain>sample-domain.location</dd:location_domain>
</dd:configuration>
<!--Concrete node information for this deployment-->
<dd:nodes>
<dd:node name="hostname" ip="1.2.3.4" profile="hostname" />
</dd:nodes>
<!--The following profiles will be deployed-->
<dd:profile id="hostname">
<dd:service name="cfr" link="false">
<dd:activation mode="manual" />
<dd:run mode="direct_persistent" instrumented="false" proxified="false" managed="false" authenticated="false" perflog="false" dynlog="false" />
<dd:endpoint protocol="iiop" port="3076" />
</dd:service>
<dd:service name="node_daemon" link="false">
<dd:activation mode="manual" />
<dd:run mode="direct_persistent" instrumented="false" proxified="false" managed="false" authenticated="false" perflog="false" dynlog="false" />
<dd:endpoint protocol="iiop" port="53079" />
</dd:service>
<dd:service name="locator" link="false">
<dd:activation mode="manual" />
<dd:run mode="direct_persistent" instrumented="false" proxified="false" managed="false" authenticated="false" perflog="false" dynlog="false" />
<dd:endpoint protocol="iiop" port="3075" />
</dd:service>
<dd:service name="naming" link="false">
<dd:activation mode="on_demand" />
<dd:run mode="indirect_persistent" instrumented="false" proxified="false" managed="false" authenticated="false" perflog="false" dynlog="false" />
<dd:endpoint protocol="iiop" />
</dd:service>
</dd:profile>
</dd:descriptor>
|
| Attachment |
| Created date: | 27 February 2012 |
|---|---|
| Last Modified: | 13 February 2013 |
| Last Published: | 09 March 2012 |
| First Published date: | 09 March 2012 |
#KnowledgeDocs
#Orbix
