InfoCenter Home > 6.6.0.2.1.1.1: XMLConfig - Example of a full exportThe following example export shows the XML elements for each object type in the WebSphere administrative domain. It is a full export of the administrative repository of a Standard Edition installation featuring the default administrative configuration. To produce a similar export, you would issue the command: XMLConfig -adminNodeName buccaneer -export export.xmlwhere the hostname of the machine containing the administrative server is "buccaneer" and the output will be directed to a file named export.xml.
Also, this example was obtained from a system that used the default configuration, and might vary slightly from actual output due to changes on your particular system. It is recommended you try the export command yourself to see exactly the output that is produced. <?xml version="1.0"?> <!DOCTYPE websphere-sa-config SYSTEM "$server_root$$dsep$bin$dsep$xmlconfig.dtd" > <websphere-sa-config> The above tags mark the beginning of the export. The following part of the export contains a tag for the default virtual host, default_host, in the administrative domain. The default host recognizes several MIME types, which are listed as part of a MIME table in the virtual-host tag. In fact, there are so many MIME types that some are omitted from the example code below. The MIME types are followed by the URIs (also known as Web resources) hosted by default_host: <virtual-host name="default_host" action="update"> <mime-table> <mime type="audio/x-wav"> <ext>wav</ext> </mime> <mime type="application/x-sv4cpio"> <ext>sv4cpio</ext> </mime> <mime type="text/x-ssi-html"> <ext>htmls</ext> <ext>shtml</ext> </mime> ... ... <mime type="application/x-netcdf"> <ext>nc</ext> <ext>cdf</ext> </mime> <mime type="video/x-motion-jpeg"> <ext>mjpg</ext> </mime> </mime-table> <alias-list> <alias>localhost</alias> <alias>127.0.0.1</alias> <alias>buccaneer.raleigh.ibm.com</alias> <alias>buccaneer</alias> <alias>9.67.127.58</alias> </alias-list> <uri name="/" rootURI="/" action="create"/> <uri name="/servlet/snoop" rootURI="/" action="create"/> <uri name="/servlet/snoop2" rootURI="/" action="create"/> <uri name="/servlet/hello" rootURI="/" action="create"/> <uri name="/ErrorReporter" rootURI="/" action="create"/> <uri name="/servlet" rootURI="/" action="create"/> <uri name="/*.jsp" rootURI="/" action="create"/> <uri name="/*.jsv" rootURI="/" action="create"/> <uri name="/*.jsw" rootURI="/" action="create"/> <uri name="/admin" rootURI="/admin" action="create"/> <uri name="/admin/install" rootURI="/admin" action="create"/> <uri name="/admin/*.jsp" rootURI="/admin" action="create"/> <uri name="/admin/*.jsv" rootURI="/admin" action="create"/> <uri name="/admin/*.jsw" rootURI="/admin" action="create"/> <uri name="/admin/" rootURI="/admin" action="create"/> <uri name="/admin/servlet" rootURI="/admin" action="create"/> <uri name="/admin/ErrorReporter" rootURI="/admin" action="create"/> <uri name="/webapp/examples" rootURI="/webapp/examples" action="create"/> <uri name="/webapp/examples/simpleJSP.servlet" rootURI="/webapp/examples" action="create"/> <uri name="/webapp/examples/simpleJSP" rootURI="/webapp/examples" action="create"/> <uri name="/webapp/examples/ErrorServlet" rootURI="/webapp/examples" action="create"/> <uri name="/webapp/examples/ping" rootURI="/webapp/examples" action="create"/> <uri name="/webapp/examples/SourceCodeViewer" rootURI="/webapp/examples" action="create"/> <uri name="/webapp/examples/showCfg" rootURI="/webapp/examples" action="create"/> <uri name="/webapp/examples/ShowCfg" rootURI="/webapp/examples" action="create"/> <uri name="/webapp/examples/showConfig" rootURI="/webapp/examples" action="create"/> <uri name="/webapp/examples/ShowConfig" rootURI="/webapp/examples" action="create"/> <uri name="/webapp/examples/HitCount" rootURI="/webapp/examples" action="create"/> <uri name="/webapp/examples/verify" rootURI="/webapp/examples" action="create"/> <uri name="/webapp/examples/*.jsp" rootURI="/webapp/examples" action="create"/> <uri name="/webapp/examples/*.jsv" rootURI="/webapp/examples" action="create"/> <uri name="/webapp/examples/*.jsw" rootURI="/webapp/examples" action="create"/> <uri name="/webapp/examples/" rootURI="/webapp/examples" action="create"/> <uri name="/webapp/examples/HelloPervasive" rootURI="/webapp/examples" action="create"/> <uri name="/webapp/examples/StockQuote" rootURI="/webapp/examples" action="create"/> <uri name="/webapp/examples/BeenThere" rootURI="/webapp/examples" action="create"/> </virtual-host>The next section contains the database driver and data source information : <jdbc-driver name="Admin DB Driver" action="update"> <implementation-class>jdbc.idbDriver</implementation-class> <url-prefix>jdbc:idb</url-prefix> <jta-enabled>false</jta-enabled> <install-info> <node-name>buccaneer</node-name> <jdbc-zipfile-location>/usr/WebSphere/AppServer//lib/idb.jar</jdbc-zipfile-location> </install-info> </jdbc-driver> <jdbc-driver name="AccountDB2Driver" action="update"> <implementation-class>com.ibm.db2.jdbc.app.DB2Driver</implementation-class> <url-prefix>jdbc:db2</url-prefix> <jta-enabled>false</jta-enabled> <install-info> <node-name>buccaneer</node-name> <jdbc-zipfile-location>/home/db2as/sqllib/java/db2java.zip</jdbc-zipfile-location> </install-info> </jdbc-driver> <data-source name="Sample Datasource" action="update"> <database-name>/usr/WebSphere/AppServer/bin/myidb.prp</database-name> <jdbc-driver-name>Admin DB Driver</jdbc-driver-name> <minimum-pool-size>1</minimum-pool-size> <maximum-pool-size>10</maximum-pool-size> <connection-timeout>120000</connection-timeout> <idle-timeout>180000</idle-timeout> <orphan-timeout>1800000</orphan-timeout>The following section contains the node, or physical machine, in the administrative domain. Its hostname is buccaneer: <node name="buccaneer" action="update"> <deployed-jar-directory>/usr/WebSphere/AppServer/deployedEJBs</deployed-jar-directory> <dependent-classpath></dependent-classpath> Next there is an application server. In this case, it is the default application server, "Default Server": <application-server name="Default Server" action="update"> <executable>java</executable> <command-line-arguments/> <environment/> <user-id></user-id> <group-id></group-id> <working-directory></working-directory> <umask>18</umask> <stdin></stdin> <stdout>/usr/WebSphere/AppServer/logs/default_server_stdout.log</stdout> <stderr>/usr/WebSphere/AppServer/logs/default_server_stderr.log</stderr> <process-priority>20</process-priority> <maximum-startup-attempts>2</maximum-startup-attempts> <ping-interval>60</ping-interval> <ping-timeout>200</ping-timeout> <ping-initial-timeout>300</ping-initial-timeout> <selection-policy>roundrobinpreferlocal</selection-policy> <trace-specification></trace-specification> <trace-output></trace-output> <transaction-log-file></transaction-log-file> <system-properties/> <debug-enabled>false</debug-enabled> <transaction-timeout>120</transaction-timeout> <transaction-inactivity-timeout>60000</transaction-inactivity-timeout> <thread-pool-size>20</thread-pool-size> <security-enabled>false</security-enabled>In the Advanced edition, the application server maintains a container for the EJBs (only one EJB is shown in the example): <container name="Default Container" action="update"> <user-id></user-id> <password></password> <cache-config> <size>2047</size> <soft-limit>2000</soft-limit> <hard-limit>2047</hard-limit> <sweep-interval>1000</sweep-interval> <passivation-directory></passivation-directory> </cache-config> <ejb name="HitCount Bean" action="update"> <jar-file>/usr/WebSphere/AppServer/deployedEJBs/_wlm_Inc.jar</jar-file> <home-name>IncBean</home-name> <user-id></user-id> <password></password> <create-db-table>false</create-db-table> <find-for-update>true</find-for-update> <minimum-pool-size>5</minimum-pool-size> <maximum-pool-size>500</maximum-pool-size> <primary-key-check>true</primary-key-check> <db-exclusive-access>false</db-exclusive-access> <data-source name="Sample Datasource"/> </ejb> The application server also contains a servlet engine <servlet-engine name="Default Servlet Engine" action="update"> <maximum-connections>25</maximum-connections> <transport-port>-1</transport-port> <servlet-mode>1</servlet-mode> <transport-type name="ose"> <ose-transport> <link-type>local</link-type> <log-file-mask trace="false" inform="false" warning="false" error="true"/> <queue-name>ibmoselink</queue-name> <clone-index>1</clone-index> <native-log-file>native.log</native-log-file> </ose-transport> </transport-type> <isclone>false</isclone>In turn, the servlet engine contains a few Web applications. Two are omitted from this example. The third (shown here) is named "examples": <web-application name="examples" action="update"> <description>Useful Example Servlets</description> <document-root>/usr/WebSphere/AppServer/hosts/default_host/examples/web</document-root> <classpath> <path value="/usr/WebSphere/AppServer/hosts/default_host/examples/servlets"/> </classpath> <error-page>/debug_error.jsp</error-page> <session-config>The example app contains several servlets. The first one is administered by the name "simpleJSP": <servlet name="simpleJSP" action="update"> <description>Simple JSP Servlet</description> <code>SimpleJSPServlet</code> <init-parameters> <parameter name="" value=""/> </init-parameters> <load-at-startup>false</load-at-startup> <debug-mode>false</debug-mode> <uri-paths> <uri value="/simpleJSP.servlet"/> <uri value="/simpleJSP"/> </uri-paths> <enabled>true</enabled> <isclone>false</isclone> </servlet>The Web application contains some other servlets that are not listed here. The Web application ends: </web-application>Now, a session manager follows. Recall, the tag for the servlet engine is still open, indicating that all of these objects are contained by the servlet engine: <session-manager name="Session Manager" action="update"> <enable-sessions>true</enable-sessions> <enable-url-rewriting>false</enable-url-rewriting> <enable-cookies>true</enable-cookies> <enable-protocol-switch-rewriting>false</enable-protocol-switch-rewriting> <cookie name="sesessionid"> <comment>servlet session support</comment> <domain></domain> <maximum>-1</maximum> <path>/</path> <secure>false</secure> </cookie> <interval-invalidation-time>1800</interval-invalidation-time> <persistent-sessions>false</persistent-sessions> <persistence-type>directodb</persistence-type> <database location="jdbc:db2:was"> <driver>COM.ibm.db2.jdbc.app.DB2Driver</driver> <user-id></user-id> <password></password> <number-of-connections>30</number-of-connections> </database> <enable-stat-collection>true</enable-stat-collection> <using-cache>false</using-cache> <using-multi-row>false</using-multi-row> <using-manual-update>false</using-manual-update> <using-native-access>false</using-native-access> <base-memory-size>1000</base-memory-size> <allow-overflow>true</allow-overflow> <data-source name=""/> </session-manager>Next, the servlet engine contains a user profile manager: <user-profile-manager name="User Profile Manager" action="update"> <enable-user-profile>false</enable-user-profile> <data-wrapper>com.ibm.servlet.personalization.userprofile.UserProfile</data-wrapper> <remote-interface-ro>com.ibm.servlet.personalization.userprofile.UP_ReadOnly</remote-interface-ro> <remote-interface-rw>com.ibm.servlet.personalization.userprofile.UP_ReadWrite</remote-interface-rw> <home-interface-ro>com.ibm.servlet.personalization.userprofile.UP_ReadOnlyHome</home-interface-ro> <home-interface-rw>com.ibm.servlet.personalization.userprofile.UP_ReadWriteHome</home-interface-rw> <jndi-name-ro>UP_ReadOnlyHome</jndi-name-ro> <jndi-name-rw>UP_ReadWriteHome</jndi-name-rw> </user-profile-manager>The user profile manager is the last object in the servlet engine and the application server. The end tags for each are displayed: </servlet-engine> </application-server> The servlet redirector portion comes next: <servlet-redirector name="Remote Servlet Redirector" action="update"> <executable>java</executable> <command-line-arguments/> <environment/> <user-id></user-id> <group-id></group-id> <working-directory></working-directory> <umask>18</umask> <stdin></stdin> <stdout>/usr/WebSphere/AppServer/logs/redirector_stdout.log</stdout> <stderr>/usr/WebSphere/AppServer/logs/redirector_stderr.log</stderr> <process-priority>20</process-priority> <maximum-startup-attempts>2</maximum-startup-attempts> <ping-interval>60</ping-interval> <ping-timeout>200</ping-timeout> <ping-initial-timeout>300</ping-initial-timeout> <selection-policy>roundrobin</selection-policy> <trace-specification>*=all=disabled</trace-specification> <trace-output></trace-output> <system-properties/> <transport-port>9357</transport-port> <max-con>50</max-con> <enabled>false</enabled> <transport-type name="ose"> <ose-transport> <link-type>local</link-type> <log-file-mask trace="false" inform="false" warning="false" error="true"/> <queue-name>redirector</queue-name> <clone-index>1</clone-index> <native-log-file>redirector.log</native-log-file> </ose-transport> </transport-type> </servlet-redirector> Then the end tag for the node is placed, indicating that all the elements pertaining to the node have been addressed: </node> Several enterprise application entries come after this (only the first is shown here): <enterprise-application name="AdminApplication" action="create"> <uri name="/admin"/> <web-application name="admin"/> </enterprise-application> Followed by several URI security entries (only one is shown): <uri-security> <uri name="/admin"/> <method-group-mapping method="HTTP_GET" method-group="ReadMethods"/> <method-group-mapping method="HTTP_POST" method-group="ReadMethods"/> <method-group-mapping method="HTTP_PUT" method-group="WriteMethods"/> <method-group-mapping method="HTTP_DELETE" method-group="RemoveMethods"/> </uri-security> Followed by the server security configuration: <security-config security-enabled="false" security-cache-timeout="600"> <app-security-defaults> <realm-name>raleigh.ibm.com</realm-name> <challenge-type ssl-enabled="false"> <basic-challenge/> </challenge-type> </app-security-defaults> <auth-mechanism> <localos> <user-id>root</user-id> <password>$server-password$</password> </localos> </auth-mechanism> </security-config> The last set of tags defines the method groups: <method-group>ReadMethods</method-group> <method-group>WriteMethods</method-group> <method-group>RemoveMethods</method-group> <method-group>CreateMethods</method-group> <method-group>ExecuteMethods</method-group> <method-group>FinderMethods</method-group>The last item is the end tag for export itself: </websphere-sa-config> |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|