4.4.3 Configuration and definition information used during migration
This subsection describes the contents output when you use the cmx_export_model command to output the settings of the already set up system.
- Organization of this subsection
(1) Version of XML schema
The latest version of XML schema is output. If settings of the systems set up by using the older versions of Easy Setup definition file are output, the tag names are converted to the latest names as per the latest version of XML schema.
(2) Configuration of the physical tier
If you use the Smart Composer functionality for setting up the system, the settings are output in the physical tier (combined-tier, http-tier, j2ee-tier, or ctm-tier) defined in the Easy Setup definition file. If you do not use Smart Composer functionality for setting up the system, the settings are output in the free-tier. For example, if system is set up using the management portal, the settings are output in the free-tier. The following logical servers are output in the free-tier depending on the system configuration:
-
Logical Web server
-
Logical J2EE server
-
Logical performance tracer
-
Logical CTM domain manager
-
Logical CTM
-
Logical smart agent
-
Logical user server
-
Logical Naming Service
For parameters of the logical server that are output, see 4.8.1 Building a system for executing J2EE applications in the uCosminexus Application Server Definition Reference Guide.
(3) Parameters set in configuration of the logical server
- Output rules
-
-
Deprecated parameters are converted to recommended parameters.
-
Parameters with the specified value are output. Parameters without a specified value are not output.
-
If default values are set for the parameters in Easy Setup definition file, or if default values are set for the keys in the management portal, those parameters are output.
-
- Output order
-
The output order depends on the type of the parameters for each type of logical servers. Further, the parameters with the same type are output in the order of parameter names. The following table describes the output order of the parameters:
Table 4‒27: Output order of the parameters Server for setting the parameter
Output order
Parameter type
J2EE server
1
Parameters that can be specified in common to all the logical servers
2
Option definition parameters for the J2EE server
3
User property parameters for the J2EE server
Web server
1
Parameters that can be specified in common to all logical servers
2
Cosminexus HTTP Server definition parameters
Other logical server
1
Parameters that can be specified in common to all the logical servers
2
Parameters of the corresponding logical server
- Setting destination
-
The setting destination of the parameters differs depending on the logical server of the set up system. The following table describes the settings destination of parameters. Note that in free-tier, the parameters cannot be set in the physical tier definition. Hence all the parameters are set in the service unit definition.
Table 4‒28: Setting destination of parameters Number of same type of logical servers
Values specified in the parameters
Setting destination of the parameters
1
--
Definition of the physical tier
2 to n
Same for all the logical servers
Definition of the physical tier
Different for each logical server
Definition of the service unit
(4) Output example
Output example of Easy Setup definition file is as follows.
This example describes the output example of the system settings where the management portal is used to add the host (host1), the logical J2EE server (j2ee01) and the logical performance tracer (prf01) to the combined-tier configuration system set up using Easy Setup definition file.
- Output example of the Easy Setup definition file
<?xml version="1.0" encoding="UTF-8" ?> <model-definition xmlns="http://www.cosminexus.com/mngsvr/schema/ModelDefinition-2.5"> <web-system> <name>sample-system</name> <tier> <tier-type>combined-tier</tier-type> <configuration> <logical-server-type>j2ee-server</logical-server-type> <param> <param-name>ejbserver.http.port</param-name> <param-value>8085</param-value> </param> </configuration> </tier> <unit> <name>unit1</name> <allocated-host> <host-ref>apsv1</host-ref> <hosts-for>combined-tier</hosts-for> </allocated-host> </unit> </web-system> <web-system>#1 <tier> <tier-type>free-tier#2</tier-type> </tier> <unit>#1 <allocated-host> <host-ref>host1</host-ref> <hosts-for>free-tier</hosts-for> <define-server> <logical-server-name>prf01</logical-server-name> <logical-server-type>performance-tracer</logical-server-type> </define-server> <define-server> <logical-server-name>j2ee01</logical-server-name> <logical-server-type>j2ee-server</logical-server-type> <configuration> <param>#3 <param-name>ejbserver.server.prf.PRFID</param-name> <param-value>PRF_ID</param-value> </param> </configuration> </define-server> </allocated-host> </unit> </web-system> <host> <host-name>apsv1</host-name> </host> <host> <host-name>host1</host-name> </host> </model-definition>
- #1
-
free-tier does not include Web system name and the service unit name.
- #2
-
If a system has a configuration that does not fit into any other physical tier configuration, that particular configuration is output as free-tier configuration.
- #3
-
In free-tier, as the parameters cannot be set in the tier definition, those are set in the service unit definition.