Hitachi

uCosminexus Application Server Application and Resource Definition Reference Guide


3.7.3 Mapping with cosminexus.xml

The following table describes the correspondence between the HITACHI WAR Property file and cosminexus.xml:

HITACHI WAR Property file

cosminexus.xml

Tag name

Occurrence pattern

Tag name

Occurrence pattern

<hitachi-war-property>

Once

<war>

Zero or more times

--

--

<module-name>#1

Once

(Omitted)

--

(Omitted)

--

<security-role>

Zero or more times

<security-role>

Zero or more times

<description>

Zero or more times

--

--

<role-name>

Once

<role-name>

Once

<linked-to>

Zero or once

<linked-to>#2

Once

(Omitted)

--

(Omitted)

--

<ejb-ref>

Zero or more times

--

--

<destination>

Zero or more times

--

--

<ejb-ref-name>

Once

--

--

<ejb-ref-type>

Once

--

--

<home>

Once

--

--

<remote>

Once

--

--

<ejb-link>

Zero or once

--

--

<resource-ref>

Zero or more times

<resource-ref>

Zero or more times

<description>

Zero or more times

--

--

<res-ref-name>

Once

<res-ref-name>

Once

<res-type>

Once

--

--

<res-auth>

Once

--

--

<linked-to>

Zero or once

<linked-to>#2

Once

<resource-env-ref>

Zero or more times

<resource-env-ref>

Zero or more times

<description>

Zero or once

--

--

<resource-env-ref-name>

Once

<resource-env-ref-name>

Once

<resource-env-ref-type>

Once

--

--

<linked-queue>

Zero or once

<linked-queue>#2

Once

<resource-adapter>#3

Once

<resource-adapter>

Once

<queue>#3

Once

<queue>

Once

<linked-adminobject>

Zero or once

<linked-adminobject>#2

Once

<resourceadapter-name>#4

Once

<resourceadapter-name>

Once

<adminobject-name>#4

Once

<adminobject-name>

Once

<linked-to>

Zero or once

<linked-to>#2

Once

<runtime>

Zero or once

--

--

<context-root>

Once

--

--

<thread-control>

Zero or once

<thread-control>

Zero or once

<thread-control-max-threads>

Once

<thread-control-max-threads>

Once

<thread-control-exclusive-threads>

Once

<thread-control-exclusive-threads>#2

Zero or once

<thread-control-queue-size>

Once

<thread-control-queue-size>

Once

<thread-control-stats-monitor>

Once

<thread-control-stats-monitor>

Zero or once

<whole-waiting-request-count>

Once

<whole-waiting-request-count>

Once

<enabled>

Once

<enabled>

Zero or once

<high-threshold>

Once

<high-threshold>

Zero or once

<low-threshold>

Once

<low-threshold>

Zero or once

<waiting-request-count>

Once

<waiting-request-count>

Once

<enabled>

Once

<enabled>

Zero or once

<high-threshold>

Once

<high-threshold>

Zero or once

<low-threshold>

Once

<low-threshold>

Zero or once

<resource-watcher>

Once

<resource-watcher>

Once

<watcher-threshold>

Once

<watcher-threshold>

Once

<watcher-interval>

Once

<watcher-interval>

Once

<watcher-enabled>

Once

<watcher-enabled>

Once

<watcher-writefile-enabled>

Once

<watcher-writefile-enabled>

Once

<urlgroup-thread-control>

Zero or more times

<urlgroup-thread-control>

Zero or more times

<urlgroup-thread-control-name>

Once

<urlgroup-thread-control-name>

Once

<urlgroup-thread-control-max-threads>

Once

<urlgroup-thread-control-max-threads>

Once

<urlgroup-thread-control-exclusive-threads>

Once

<urlgroup-thread-control-exclusive-threads>#2

Zero or once

<urlgroup-thread-control-queue-size>

Once

<urlgroup-thread-control-queue-size>

Once

<urlgroup-thread-control-mapping>

Zero or more times

<urlgroup-thread-control-mapping>

Zero or more times

<url-pattern>

Once

<url-pattern>

Once

<stats-monitor>

Once

<stats-monitor>

Once

<waiting-request-count>

Once

<waiting-request-count>

Once

<enabled>

Once

<enabled>

Once

<high-threshold>

Once

<high-threshold>

Once

<low-threshold>

Once

<low-threshold>

Once

<http-request>

Zero or once

<http-request>

Zero or once

<encoding>

Zero or once

<encoding>#2

Once

<http-response>

Zero or once

<http-response>

Zero or once

<encoding>

Zero or once

<encoding>#2

Once

<jsp>

Zero or once

<jsp>

Zero or once

<page-encoding>

Zero or once

<page-encoding>#2

Once

<http-session>

Zero or once

<http-session>

Zero or once

<http-session-max-number>

Once

<http-session-max-number>#2

Zero or once

<resource-watcher>

Once

<resource-watcher>

Once

<watcher-threshold>

Once

<watcher-threshold>

Once

<watcher-interval>

Once

<watcher-interval>

Once

<watcher-enabled>

Once

<watcher-interval>

Once

<watcher-writefile-enabled>

Once

<watcher-writefile-enabled>

Once

<dbsfo>

Zero or once

<dbsfo>

Zero or once

<enabled>

Zero or once

<enabled>

Zero or once

<application-id>

Zero or once

<application-id>

Zero or once

<attribute-data-size-max>

Zero or once

<attribute-data-size-max>

Zero or once

<exclude-extensions>

Zero or once

<exclude-extensions>

Zero or once

<start-notify-error>

Zero or once

<start-notify-error>

Zero or once

<start-order>

Zero or once

<start-order>

Zero or once

--

--

--

--

Legend:

--: No corresponding tag. Alternatively, the description of the occurrence pattern is omitted because the corresponding tag does not exist or the tag is omitted.

(Omitted): The tag is omitted.

#1

This tag corresponds to <application>-<module>-<web>-<web-uri> in the application.xml and does not exist in the property file, however, the tag is unique to cosminexus.xml. This tag is the key for identifying WAR files.

#2

The occurrence pattern is different from the property file because only the elements to be customized are coded in cosminexus.xml.

#3

Enter the resource adapter display name in resource-adapter and the QUEUE name in <queue>.

#4

Enter the resource adapter display name in <resourceadapter-name> and the administered object name in <adminobject-name>.