Configuring Oracle Application Server Wireless
9.4 OracleAS Wireless Attribute Descriptions
This section describes the attributes that are specific for OracleAS Wireless. The OracleAS Wireless attributes are described with the following format:
■ Title: This is the attribute name and value being defined. For example, id="wireless".
■ Required:This field defines whether or not the attribute is required in the
component definition.
■ Default: This defines the default value assigned to the attribute. The default value
appears in the installed version of the opmn.xml file or is assigned internally if the attribute is not present.
■ Valid values: If applicable, this field defines the valid values for the attribute. For
example, wireless.
■ Path: This field defines in which elements the attribute can appear. For example,
ias-component. id="wireless"
Required: true Default: none
Valid values: wireless
Path: ias-component
This id is required and cannot be changed. The name must match the targets.xml
module-id="notificationeventcollector"
Required: true Default: none
Path: ias-component/process-type
This module-id defines the type of process and associates this configuration with a process module. In Section 9.1, the nine OracleAS Wireless server types are associated with OracleAS Wireless process module.
module-id="datafeeder"
Required: true Default: none
Path: ias-component/process-type
This module-id defines the type of process and associates this configuration with a process module. In Section 9.1, the nine OracleAS Wireless server types are associated with OracleAS Wireless process module.
module-id="performance"
Required: true Default: none
Path: ias-component/process-type
This module-id defines the type of process and associates this configuration with a process module. In Section 9.1, the nine OracleAS Wireless server types are associated with OracleAS Wireless process module.
module-id="messaging"
Required: true Default: none
Path: ias-component/process-type
This module-id defines the type of process and associates this configuration with a process module. In Section 9.1, the nine OracleAS Wireless server types are associated with OracleAS Wireless process module.
module-id="notification"
Required: true Default: none
Path: ias-component/process-type
This module-id defines the type of process and associates this configuration with a process module. In Section 9.1, the nine OracleAS Wireless server types are associated with OracleAS Wireless process module.
module-id="location"
Required: true Default: none
Path: ias-component/process-type
This module-id defines the type of process and associates this configuration with a process module. In Section 9.1, the nine OracleAS Wireless server types are associated with OracleAS Wireless process module.
OracleAS Wireless Attribute Descriptions
module-id="telnetserver"
Required: true Default: none
Path: ias-component/process-type
This module-id defines the type of process and associates this configuration with a process module. In Section 9.1, the nine OracleAS Wireless server types are associated with OracleAS Wireless process module.
module-id="telnetdispatcher"
Required: true Default: none
Path: ias-component/process-type
This module-id defines the type of process and associates this configuration with a process module. In Section 9.1, the nine OracleAS Wireless server types are associated with OracleAS Wireless process module.
module-id="edgeserver"
Required: true Default: none
Path: ias-component/process-type
This module-id defines the type of process and associates this configuration with a process module. In Section 9.1, the nine OracleAS Wireless server types are associated with OracleAS Wireless process module.
numprocs="1"
Required: true Default: none Valid values: 1
Path: ias-component/process-type/process-set
This attribute gives the number of OracleAS Wireless instances started for this
process-set. The OracleAS Wireless module does not permit more than one instance with the same process-set. To start more than one processes for the same server type, put one process-set entry with one unique process-set id for each process.
For example:
<process-type id="datafeeder_server" module-id="datafeeder"> <process-set id="datafeeder_instance_1" numprocs="1"/> <process-set id="datafeeder_instance_2" numprocs="1"/> </process-type>
Do not create the following:
<process-type id="datafeeder_server" module-id="datafeeder"> <process-set id="datafeeder_instance_1" numprocs="2"/> </process-type>
id="start-parameters"
Required: false Default: none
category
This id indicates the configuration block for start-parameters category. This category contains data related to starting the module.
id="java-bin"
Required: false
Default: $ORACLE_HOME/jdk/bin/java
Valid values: Full path to java.exe
Path: ias-component/process-type/process-set/module-data/ category/data
You can specify alternate paths to the Java executable. However, a valid version of Java will have to be used for the process to start up and work correctly.
id="java-parameters"
Required: false
Default: -Doracle.wireless.instance=<id specified in process set> -Doracle.opmn.uid=<opmn assigned unique id>
Valid values: Any valid Java parameters
Path: ias-component/process-type/process-set/module-data/ category/data
This id enables you to specify any valid Java parameters. All specified Java parameters will be appended to the default values. OPMN derives some java parameters internally and additional parameters can be added with this attribute. If you specify "-Doracle.wireless.instance=<value>" or "-Doracle.opmn.uid=<value>", it will replace the default value.
id="class-name"
Required: false
Default: oracle.panama.sysmgmt.server.PanamaServer for start and
oracle.panama.sysmgmt.client.manager for stop
Valid values: Any valid Java class names
Path: ias-component/process-type/process-set/module-data/ category/data
This id enables you to specify a Java class name other than the default ones to start or stop a OracleAS Wireless process. Oracle recommends not changing this parameter; it is for internal use only.
id="application-parameters"
Required: false Default: none
Valid values: any valid Java application parameters
Path: ias-component/process-type/process-set/module-data/ category/data
This id enables you to put more application parameters in addition to the default one. The default one tells which OracleAS Wireless process-type to be started.
id="stop-parameters"
Required: false Default: none
OracleAS Wireless Attribute Descriptions
Path: ias-component/process-type/process-set/module-data/ category
This id indicates the configuration block for stop-parameters category. In this category, some stop related module data can be specified.
start timeout="<seconds>"
Required: false Default: 120
Valid values: A timeout value in seconds
Path: ias-component/process-type/process-set/module-data/category
This parameter notifies OPMN how long it should wait for the process to start. The default value is 180 seconds. However, when starting OracleAS Wireless processes, database access is required and it may take up to 5 minutes to signal a process to start.
stop timeout="<seconds>"
Required: false Default: 60
Valid values: A timeout value in seconds
Path: ias-component/process-type/process-set/module-data/category
This parameter notifies OPMN how long it should wait for the process to terminate. The default value is 180 seconds. However, when stopping OracleAS Wireless processes, database access is required and it may take up to 5 minutes to signal a process to terminate.
restart timeout="<seconds>"
Required: false Default: 180
Valid values: A timeout value in seconds
Path: ias-component/process-type/process-set/module-data/category
This parameter notifies OPMN how long it should wait for a process to restart. The default value is 180 seconds. However, a restart action is actually a stop and start, so the total value should be:
180 (for start) + 300 (for stop) =480 seconds.