A Managing and Configuring Application Server Control

A.1.1 Starting and Stopping the Application Server Control Console on UNIX

If you need to start or stop the Application Server Control Console on a UNIX system, use the emctl command shown in Table A-1.

The emctl command is available in the ORACLE_HOME/bin directory after you install Oracle Application Server.

You can verify the Application Server Control Console is started by pointing your browser to the Application Server Control Console URL:

http://hostname.domain:port

You can locate the Application Server Control Console port number in ORACLE_HOME/install/portlist.ini. For example:

http://hostname.domain:1810

A.1.2 Starting and Stopping the Application Server Control Console on Windows

To start or stop the Application Server Control Console on Windows systems:

1. Open the Services control panel.

   For example, on Windows NT, select Start > Settings > Control Panel and then double-click the Services icon.

   On Windows 2000, select Start > Administrative Tools > Services.

2. Locate the Application Server Control in the list of services.

   The name of the service is usually consists of "Oracle," followed by the name of the home directory you specified during the installation, followed by the word "ASControl." For example, if you specified AS10g as the Oracle Home, the Service name would be:

   OracleAS10gASControl
   
   

3. After you locate the service, you can use the Services control panel to start or stop the Application Server Control service.

   By default, the Application Server Control service is configured to start automatically when the system starts.

A.3.1 Changing the Password Using the Application Server Control Console

To change the ias_admin user password using the Oracle Enterprise Manager 10g Application Server Control Console:

1. Navigate to the Application Server home page and select Preferences in the top right corner of the page.

   Enterprise Manager displays the Change Password page.

2. Enter the current ias_admin password, the new password, the new password again for confirmation.

   The new password must be between 5 and 30 characters, it must begin with an alphabetic character, and it must contain at least one number.

3. Click OK to reset the ias_admin password for the current application server instance.

   The next time you log in, you must use the new password.

A.3.2 Changing the Password Using the emctl Command-Line Tool

To change the ias_admin user password using a command-line tool:

1. Enter the following command in the Oracle home of your Oracle Application Server installation:

   (UNIX) ORACLE_HOME/bin/emctl set password old_password new_password
   (Windows) ORACLE_HOME\bin\emctl set password old_password new_password
   
   

   For example:

   (UNIX) ORACLE_HOME/bin/emctl set password m5b8r5 b8s0d9
   (Windows) ORACLE_HOME\bin\emctl set password m5b8r5 b8s0d9
   
   

2. Restart the Application Server Control Console.

   
   

   See Also: "Starting and Stopping the Application Server Control"

   
   

A.5.1 Modifying the Application Server Control Logging Properties

To configure the Application Server Control to support ODL:

1. Use a text editor to edit the following file in the Oracle Application Server home directory:

   (UNIX) ORACLE_HOME/sysman/config/emiasconsolelogging.properties
   (Windows) ORACLE_HOME\sysman\config\emiasconsolelogging.properties
   
   

2. Follow the instructions in the file to replace the default properties with those that are commented by default.

   Example A-3 shows the properties in the emiasconsolelogging.properties file that enable ODL for the Application Server Control log file.

   Table A-3 describes the logging properties available in the emiasconsolelogging.properties file.

3. Save and close the emiasconsolelogging.properties file.

4. Restart Application Server Control.

# To support the ODL log appender, replace the lines above
# with the following and restart EM.  The resulting ODL log files
#  will be read by the Log Loader and written to the Log Repository.
#
# log4j.appender.emiaslogAppender=oracle.core.ojdl.log4j.OracleAppender
# log4j.appender.emiaslogAppender.ComponentId=EM
# log4j.appender.emiaslogAppender.LogDirectory=/private/904_shiphomes/m21_infra/sysman/log
# log4j.appender.emiaslogAppender.MaxSize=20000000
# log4j.appender.emiaslogAppender.MaxSegmentSize=5000000

A.5.2 More About the Application Server Control Console Log File Properties

When you enable ODL, the resulting log.xml file increases in size over time as information is written to the file. The file is designed to reach a maximum size, determined by the MaxSegmentSize property shown in Example A-3. When the file reaches the predefined maximum size, Application Server Control renames (or rolls) the logging or trace information to a new file name and starts a new log or trace file. This process keeps the log file from growing too large.

To be sure you have access to important log information, Application Server Control will rollover the log.xml file until the log file and its rollover files consume a predefined, maximum amount of disk space, determined by the MaxSize property shown in Example A-3. When the log file and its rollover files reach this predefined target, Application Server Control deletes the oldest rollover file.

As a result, you will often see multiple log files in the log directory. The following example shows three Application Server Control rollover files and the current log file in the log directory:

log.xml
log1.xml
log2.xml
log3.xml

A.6.1 Making HTML Pages More Accessible

Enterprise Manager takes advantage of user interface development technologies that improve the responsiveness some user operations. For example, when you navigate to a new record set in a table, Enterprise Manager does not redisplay the entire HTML page.

However, this performance-improving technology is generally not supported by screen readers. When you enable accessibility mode, you disable this feature, and as a result, make the Enterprise Manager HTML pages more accessible for disabled users.

A.6.2 Providing Textual Descriptions of Enterprise Manager Charts

Throughout Enterprise Manager, charts are used to display performance data. For most users, these charts provide a valuable graphical view of the data that can reveal trends and help identify minimum and maximum values for performance metrics.

However, charts do not convey information in a manner that can be read by a screen reader. To remedy this problem, you can configure Enterprise Manager to provide a complete textual representation of each performance chart. When you enable accessibility mode, Enterprise Manager displays a small icon for each chart that can be used as a drill-down link to the textual representation.

Figure A-1 shows an example of the icon that appears below each chart after you enable accessibility mode.

Figure A-1 Icon Representing the Textual Representation of a Chart

Description of the illustration ias_accessible_chart.gif

A.6.3 Modifying the uix-config.xml File to Enable Accessibility Mode

1. Locate the uix-config.xml configuration file in the Oracle Application Server home directory:

   (UNIX) ORACLE_HOME/sysman/webapps/emd/WEB-INF
   (Windows) ORACLE_HOME\sysman\webapps\emd\WEB-INF
   
   

2. Open the uix-config.xml file using your favorite text editor and locate the following entry:

   <!-- An alternate configuration that disables accessibility features  -->
   <default-configuration>
     <accessibility-mode>inaccessible</accessibility-mode>
   </default-configuration>
   
   

3. Change the value of the accessibility-mode property from inaccessible to accessible.

4. Save and close the file.

5. Restart the Application Server Control Console.