| Oracle® Application Server Release Notes 10g Release 3 (10.1.3.1.0) for Microsoft Windows B31012-02 |
|
 Previous |
 Next |
| Oracle® Application Server Release Notes 10g Release 3 (10.1.3.1.0) for Microsoft Windows B31012-02 |
|
Previous |
Next |
This chapter describes management and security issues associated with Oracle Application Server. It includes the following topics:
This section describes general management and security issues. It includes the following topics:
Section 4.1.1, "Limited Management Support for Multiple-JVM OC4J Instances"
Section 4.1.3, "Problem Removing a Property from a Native Data Source"
Section 4.1.4, "Use the Command-Line to Restart Standalone OC4J Instances"
Section 4.1.5, "TopLink Sessions Not Available in Application Server Control Console"
Section 4.1.6, "Unable to Receive MBean Notification Using OPMN to Start or Stop OC4J"
Section 4.1.7, "Using the Java Server Pages Standard Tag Libraries"
With Oracle Application Server 10g Release 3 (10.1.3.1.0), you can configure any OC4J instance to use multiple Java Virtual Machines (JVMs). You can perform this configuration change by using the Application Server Control Console or by setting the numprocs argument in the opmn.xml file to a number greater than one (1).
The opmn.xml file is located in the following directory in your Oracle Application Server Oracle home:
ORACLE_HOME\opmn\conf\
To set the number JVMs in the Application Server Control Console, see "Creating Additional JVMs for an OC4J Instance" in the Application Server Control online help.
To set the number of JVMs by editing the numprocs argument in the opmn.xml file, refer to the following example, which shows the numprocs entry you must modify:
<ias-component id="OC4J"> <process-type id="home" module-id="OC4J" status="enabled"> .
.
.
<process-set id="default_group" numprocs="2"/>
</process-type>
</ias-component>
Note, however, that this feature is not supported by Application Server Control. Specifically, Application Server Control (represented by the ascontrol application) cannot run on an OC4J instance that is running multiple JVMs. As a result, be sure that you do not configure multiple JVMs for the administration OC4J instance (the OC4J instance that is hosting the active ascontrol).If you choose to configure the number of JVMs for the administration OC4J to more than one (1), then you must use command line tools to manage your Oracle Application Server environment. For example, you must use:
admin_client.jar for deployment, re-deployment, undeployment, start and stop applications, and shared library management
Apache Ant for deployment, redeployment, and undeployment of your applications
opmnctl commands for starting, stopping, and other life cycle operations on the Oracle Application Server
Further, if you are using multiple JVMs on the administration OC4J and, as a result, the Application Server Control Console is not available, then you must make any Oracle Application Server instance configuration changes manually. Manual configuration changes often require you to shut down the Oracle Application Server instance, manually configure the relevant XML files, and then restart Oracle Application Server.
If you modify the name or the connection URL of a JDBC data source or JDBC connection pool, then you must restart the OC4J instance; otherwise the changes you make will not take effect.
For example, if you use the JDBC Resources page in the Application Server Control Console to change the connection URL of a JDBC connection pool, you will not be prompted to restart the OC4J instance, but the restart is required. If you do not restart the OC4J instance, any deployed applications that require the data source will attempt to use the original connection URL.
|
See Also: "Managing Data Sources and JDBC Connection Pools" in the Application Server Control online help |
If you use the Application Server Control Console to remove a property from a native data source, Enterprise Manager does not remove the property from the underlying connection factory. As a result, the property (and its current value) is not changed.
This is expected behavior. To set a value on the underlying connection factory, use the setProperty operation of the JDBCDataSource MBean for the native Data Source to do this. You can use the MBean Browser, which is available in the Application Server Control Console, to invoke an MBean operation.
|
See Also: "About the MBean Browser" in the Application Server Control online help |
Some OC4J configuration pages in the Application Server Control Console (including the JTA Administration and Oracle Internet Directory Association pages) require a restart of the OC4J instance for changes to take affect. Users are notified of this with on screen warnings during configuration operations on these components.
If are using the Application Server Control Console in a standalone OC4J environment, and you use the Restart link, which is displayed after applying changes to one of these pages, the operation may take a few minutes because it performs an internal restart of the OC4J instance. As a result, instead of using the Restart link, Oracle recommends that OC4J standalone users use the command line to restart the OC4J instance.
If the TopLink Sessions for a TopLink-enabled application are not available in Application Server Control Console, check to be sure the TopLink session is configured to create the MBeans at login time. This is done by ensuring that the application has a serverPlatform class defined, and that the ServerPlatform class has its is RuntimeServicesEnabled flag enabled.
For Oracle Application Server 10g Release 3 (10.1.3.1.0), you should be using the following platform class, which can be set in the sessions.xml or through the session API:
oracle.toplink.platform.server.oc4j.Oc4j_10_1_3_Platform
When developing a TopLink-enabled application using Oracle JDeveloper, make sure to use version 11 or higher.
|
See Also: "Configuring the Server Platform" in the Oracle TopLink Developer's Guide |
You will not be able to receive notification from the ias:j2eeType=J2EEServer,name... MBean entity if you start or stop Oracle Containers for J2EE (OC4J) using OPMN. This happens using either the Application Server Control or the opmnctl stop or opmnct start command from the command line.
There is presently no workaround for this issue.
The Java Server Pages Standard Tag Library (JSTL) makes use of Jaxp 1.2 classes that are packaged with Java Developer Kit 1.4.
Oracle Application Server 10g Release 3 (10.1.3.1.0) makes use of JDK 1.5 which uses Jaxp 1.3 classes. However, the JSTL still requires the Jaxp1.2 classes. If you run the JSTL with XML related tags in JDK 1.5 you may receive an error message similar to:
: missing class org.apache.xpath.encounter failure.
To avoid JSTL failure, include the xalan.jar file in the required .war file. Add the xalan.jar file into your /WEB-INF/lib directory with the .war file and then re-package.
For more information refer to the JSTL release notes at:
http://java.sun.com/webservices/docs/1.6/jstl/ReleaseNotes.html.
As documented in the Oracle Process Manager and Notification Server Administrator's Guide and functional specifications for Dynamic Resource Management (DRM), a Resource Management Directive (RMD) conditional can have a fully qualified path. However, the conditional may not evaluate at all. It may fail to trigger any action or exception even though the opmn.xml file is valid.
RMD definitions can be either:
Hierarchical: if defined at the ias-instance level or lower. Hierarchical RMDs assume an association within the OPMN configuration components in which they are defined.
Global: if defined at the process-manager level. Global RMDs require explicit OPMN component specifications.
If you are referencing a hierarchical RMD, instead of a fully qualified path use a hierarchical relative reference.
For example, if the average request time is greater than 500 milliseconds for at least 60 seconds and there are less then 4 processes running for the process-set at which the hierarchical RMD was configured for OC4J, you would use the following in the opmn.xml file:
([process].avgReqTime > 500 {duration(60)})&([process-set].numProcs < 4)
If you are referencing a global RMD use a global absolute reference.
For example, if the heap size of a Java Virtual Machine (JVM) has exceeded 500 MBs, you would use the following in the opmn.xml file:
[process-set=home][process].heapSize > 500000
Note that the opmn.xml file is located in the following directory in your Oracle Application Server Oracle home:
ORACLE_HOME\opmn\conf\
This section describes clustering and replication issues. It includes the following topic:
Oracle Universal Installer provides an example cluster discovery address as part of the advanced installation option. The provide example discovery address is 225.0.0.1:6789. This is not a recommended address; rather it is an example intended to provide the type of cluster discovery address users may ask for from their network administrator.
Because the cluster configuration of Oracle Application Server is fully dynamic it is possible for installations using the example cluster discovery address (225.0.0.1:6789) to be inadvertently clustered with other servers installed with the same example cluster discovery address.
The cluster discovery address of a specific Oracle Application Server instance can be set from the command line using the following opmnctl command:
> $ORACLE_HOME/opmn/bin/opmnctl config topology update discover=<cluster config address>
For example, to update a cluster discovery address in a specific Oracle Application Server instance to be 225.0.0.1:9876, the command would be:
> $ORACLE_HOME/opmn/bin/opmnctl config topology update discover="*225.0.0.1:9876"
Details on configuring topologies and the cluster discovery address can be found in Chapter 8, "Configuring and Managing Clusters" of the Oracle Containers for J2EE Configuration and Administration Guide.
The section describes documentation errata in management documentation. It includes the following topics:
The following topics in the Application Server Control online help incorrectly state the valid range of addresses you can use for a multicast address when configuring an Oracle Application Server 10g Release 3 (10.1.3.1.0) cluster topology:
"Tips When Configuring the Cluster Topology"
"Summary of the Supported Cluster Topologies"
The multicast address must be within the following range: 224.0.1.0 to 239.255.255.255.
To use the latest J2EE features of Oracle Application Server, 10g Release 3 (10.1.3.1.0), with existing Oracle Application Server, Release 2 (10.1.2), components and applications, you can use the Oracle HTTP Server from an Oracle Application Server, Release 2 (10.1.2), middle tier as the front-end for your Oracle Application Server, 10g Release 3 (10.1.3.1.0), middle tier. Section 6.4 of the Oracle Application Server Administrator's Guide describes how to do this.
However, in that section, the following command is incorrect:
ORACLE_HOME_SERVER2/opmn/bin/opmnctl config port update ias-component=OC4J process-type=instance name portid=default-web-site protocol=ajp
The command should be:
ORACLE_HOME_SERVER2/opmn/bin/opmnctl config port update ias-component=default_group process-type=instance name portid=default-web-site protocol=ajp range=12501-12600
If your environment includes Oracle Enterprise Service Bus, the following describes additional information that is not currently documented in Section 7.2.2 of the Oracle Application Server Administrator's Guide:
In Task 9, Step 1 describes editing the esbparam.properties file to change the DT_OC4J_HOST property. Additionally, if the port number changed, you must change the DT_OC4J_HTTP_PORT property.
After you import the esbparam.properties file as described in Step 3, you must redeploy all applications, including Oracle BPEL Process Manager applications.
If your environment includes Oracle Enterprise Service Bus, the following describes additional information that is not currently documented in Section 9.5.6 of the Oracle Application Server Administrator's Guide:
In the part that describes steps to take on the cloned instance, step 2 describes editing the esbparam.properties file on the cloned instance to change the DT_OC4J_HOST property to the new hostname. Note that if the cloned instance is located on a remote host, you must change both the DT_OC4J_HOST and DT_OC4J_HTTP_PORT properties. If the cloned instance is on the same node as the source instance, you must change the DT_OC4J_HTTP_PORT property.
After you import the esbparam.properties file as described in Step 4, you must redeploy all applications, including Oracle BPEL Process Manager applications.
