HP Integrity NonStop H-Series - Manual (Page 49)

proxy-conf.xml
This configuration file contains information about the binding port and connection address. The
bind port is indicated by the attribute localPort, and the address to which the Post Master
connects, is indicated by the attributes dstAddress and dstPort. The following is a snippet:
<?xml version="1.0" encoding="UTF-8"?>
<Server name="Proxy" port="3455" shutdown="SHUTDOWN">
<Proxy name="simple" localPort="3450" dstAddr="15.213.84.6" dstPort="3450" />
<Proxy name="web" localPort="3459" dstAddr="15.213.84.6" dstPort="3459" />
<Proxy name="webSecure" localPort="3460" dstAddr="15.213.84.6" dstPort="3460" />
In this snippet, the Post Master listens on the default local interface "0.0.0.0" and on the port
3450. It connects to the destination address "15.213.84.6:3450".
The ji.prop of the Post Master is used to configure the client socket connecting to the destination
address "15.154.120.44:3450" as a pathsend socket.
ji.prop
This is the configuration file used by JI to make Post Master behave like a pathsend client. There
is a single line of entry in this file, and is of the format client_socket-<host name>:<port
number> pathmon=<pmon name>:serverclass=<name of NSASJ SERVER
serverclass> .
where,
host name is the name of the host of the IP address indicated by dstAddress in
proxy-conf.xml .
port number this is the same as dstPort in proxy-conf.xml.
pmon name is the name of the pathmon where the NSASJ serverclasses are configured.
serverclass is the xx-SERVER serverclass.
CAUTION: This file is generated during NSASJ installation and hence, it is recommended not to
modify this file.
The following is a snippet:
client_socket-15.213.84.6:3450 pathmon=$NSASJ:serverclass=nsasj-SERVER
client_socket-15.213.84.6:3459 pathmon=$NSASJ:serverclass=nsasj-SERVER
client_socket-15.213.84.6:3460 pathmon=$NSASJ:serverclass=nsasj-SERVER
EE subsystem
The EE subsystem defines the execution environment of the container. The schema definition for
the subsystem can be found in the file jboss-as-ee_1_1.xsd in the docs/schema folder of
the installation. The following is a snippet from domain.xml:
<subsystem xmlns="urn:jboss:domain:ee:1.1">
<spec-descriptor-property-replacement>false</spec-descriptor-property-replacement>
<jboss-descriptor-property-replacement>true</jboss-descriptor-property-replacement>
</subsystem>
Table 11 (page 49) lists and explains the various elements of the EE subsystem.
Table 11 Elements of EE subsystem
Description Element
This can be used to define modules that are accessible to all deployments
on the container. The following example makes the module
com.hp.nsk.utils
available to all deployments:
<subsystem xmlns="urn:jboss:domain:ee:1.1">
global-modules
<global-modules>
<module name="com.hp.nsk.utils" slot="main" />
EE subsystem 49