Skip Headers
Oracle® Application Server Release Notes
10g Release 3 (10.1.3.1.0) for Microsoft Windows
B31012-02
  Go To Documentation Library
Home		 Go To Table Of Contents
Contents
Previous
Previous 		 Next
Next		  

9 Oracle Web Services Manager

This chapter describes issues associated with Oracle Web Services Manager (Oracle WSM). It includes the following topics:

9.1 General Issues and Workarounds

This section describes general issues and workaround. It includes the following topics:

9.1.1 Starting the Oracle WSM Server

There are two Readme files in the ORACLE_HOME directory: Readme.txt and OC4J_Readme.txt. There are instructions in the OC4J_Readme.txt file for starting the Oracle Application Server. If you have installed Oracle WSM as a standalone installation, these instructions will not start the Oracle WSM Server correctly.

For the standalone Oracle WSM installation, follow the instructions for starting the Oracle WSM Server in the file named Readme.txt, and refer to the Oracle Web Services Manager Administrator's Guide for additional information.

9.1.2 Error on Import Services Page

There is no User ID or Password field on the Web services Discovery page. However, you will see the following instruction on this page (Figure 9-1):

Please enter the URL to Discovery service. Provide User Id and Password if authentication is required.

Ignore the second sentence referring to the user ID and password.

Figure 9-1 Import Services Page

Description of Figure 9-1 follows
Description of "Figure 9-1 Import Services Page"

9.1.3 Step Instance Creates One or More Long-Lived Connection to the Directory

Each policy step instance creates one or two long-lived connection to the Active Directory or LDAP directory. In a production environment, this may cause connection overloading during user authentication against an LDAP or Active Directory server.

The default value of the connection lifetime parameter, 0 milliseconds, ensures that the connection is never timed out.

To provide a workaround for this behavior, you need to tune the connection lifetime parameter as follows:

  1. Open the following file:

    ORACLE_HOME/opmn/conf/opmn.xml

  2. Find the process-type id whose value is the name of the instance in which Oracle Web Services Manager is installed. This may be "home", or it could be another instance name. For example:

    
...

<ias-component id="default_group">

   <process-type id="home" module-id="OC4J" status="enabled">

...

  3. Find the data id="java-options" in the category id="start-parameters" section of the file.

    
...

<category id="start-parameters">

   <data id="java-options" value="-server -XX:MaxPermSize=128M .../>

</category>

...

  4. Add the connection lifetime parameter under java-options. For example:

    -Doracle.wsm.directory.timeout=3600000

    Talk to your Active Directory or LDAP system administrator for the value for timing out the connection.

  5. Restart the server for the configuration changes to take effect.

9.1.4 Deploying Oracle Web Services Manager Monitor

When you deploy the Oracle Web Services Manager Monitor on Linux, you get the following error: "Target 'install.deployCoreman' does not exist in this project. " The cause for this error is a typographical error in the Linux version of the Configuration Assistant (wsmadmin.sh). Edit the ORACLE_HOME/owsm/bin/wsmadmin.sh file, and replace both occurrences of the string "install.deployCoreman" with "install.deployMonitor". These should appear on lines 169 and 170 of the script.

This problem does not exist with the Windows version of the Configuration Assistant (wsmadmin.bat).

9.1.5 Accessing a Virtualized Web Service

When you try to access the WSDL for a Web service that has been virtualized by the Oracle Web Services Manager Gateway, you may get a "500 internal server error." This problem occurs if the gateway application is deployed with a new component ID. To correct this problem, restart the application server.

9.1.6 Valid User Names and Passwords

Using non-alphanumeric characters in user names, user passwords, and group IDs may cause errors. For example, backslashes (\) and single quotes (') are invalid characters. Therefore, Oracle recommends using only alphanumeric characters in user name, user passwords, and group IDs.

9.1.7 Multibyte User Names and Passwords

There is a limitation on the character set encoding of characters in the property files. You may use characters that belong to the ISO 8859-1 character set in the property files. If you want to use characters that belong to any other character set, you must convert them to escaped UTF-8 characters. For example, to use a multibyte character in a user name or password, you must convert the multibyte character to an escaped UTF-8 character. If you do not convert characters, you will not get the intended result.

9.1.8 Date and Time Format

Date and time format are not localized on the following pages of the Web Services Manager Control Console:

  • Alarm List

  • Stress Report

  • Flow Detail

  • My Views

Date and time always appear in the U.S. English locale. There is no workaround for this.

9.2 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It includes the following topics:

9.2.1 XE DB Settings

Using an Oracle XE database with Oracle WSM may present connection problems. This is a known error that sometimes occurs with Oracle XE database client, but presents an intermittent problem for Oracle WSM.

To work around this limitation you may need to increase the value of the database parameter PROCESSES. The default value for this parameter setting is 40, but you may try to increase the value to 64. If required, you can further increase the value of this parameter.

9.2.2 Out of Memory Exception

You may get an out of memory exception if the Oracle WSM is configured so that its runtime memory requirements exceed the JVM default configuration. One known situation where this can occur is if you patch Oracle WSM 10.1.3 to 10.1.3.1.

To avoid this error, you need to increase the size of the Java heap.

To change the values of the Java heap

  1. Log in to Oracle Enterprise Manager 10g Application Server Control.

  2. In the Cluster Topology page, locate the Members section, and click home.

  3. Click Administration.

  4. Find Server Properties in the Task Name list, and click the Go to Task icon.

  5. Edit the values for Maximum heap size (1024 Mb) and Initial heap size (512 Mb).

  6. Add a row for the -XX:MaxPermSize (256 Mb) and -XX:PermSize (128 Mb) parameters and provide a value.

  7. Click Apply.

  8. Restart the server.


Note:

The values in parentheses are provided as an example only. These values were derived assuming that all components in the Oracle Application Server 10g Release 3 (10.1.3.1.0), also known as the Oracle SOA Suite (10.1.3.1.0), are installed. Consult your OC4J administrator and the Oracle Application Server Performance Guide for the appropriate settings for your environment.

9.2.3 Web Browser Times Out

In situations where there is high network latency between Oracle WSM and Oracle Database, the Web browser may time out before it can retrieve the data from the database.

To prevent the browser from timing out, modify the browser time out setting.

For Internet Explorer

  1. Edit the following registry key:

    HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Internet Settings

  2. Add the DWORD KeepAliveTimeout, and set the value in milliseconds.

For all other supported Web browsers, please consult the product documentation for the browser for information on setting the browser time out.

9.2.4 Oracle Access Manager SDK Path

When you configure the Oracle Access Manager Authenticate Authorize policy step, and you reconfigure the path to the Oracle Access Manager SDK, the new path does not take effect until you restart any agents or gateways that use this SDK.


Note:

Oracle Access Manager SDK is the same as what has previously been referred to as Access Server SDK.

9.3 Documentation Errata

This section describes documentation errata. It includes the following topic:

9.3.1 Exporting Data from the Database

The exportDBData operation is described in the Oracle Web Services Manager Deployment Guide, Appendix A, "Oracle Web Services Manager WSMADMIN commands." However, the procedure described in the Oracle Web Services Manager Deployment Guide is missing a step.

The following procedure clarifies this omission in the documentation:

  1. Perform the following operation:

    wsmadmin exportDBData database_server_password

  2. Press Enter to proceed with the export data operation.

    The system displays the following message:

    "Warning!!! The data in the input directory will be deleted. Are you sure to continue? Y-Yes N-No:"

  3. Select Y to proceed with the operation.

9.3.2 Correction to Command Syntax

There is an error in Oracle Web Services Manager Administrator's Guide, Chapter 6, "Monitoring Oracle Web Services Manager," in the section titled "Configuring Metrics Data Persistence."

In step 3 of the procedure, the correct command to redeploy the application is wsmadmin deploy application_server_password monitor.

9.3.3 Correction to Procedure for Deploying a Proxy Server

There is an error in Oracle Web Services Manager Deployment Guide, Chapter 2, "Implementing your Web Services Manager Deployment," in the section titled "Configuring Oracle WSM Behind a Proxy Server."

In the procedure, "To configure Oracle WSM behind a proxy when it is installed as part of the Oracle SOA Suite", steps 3 and 4 should be performed before step 2. The revised order for this procedure is as follows:

  1. Open the following file:

    ORACLE_HOME/opmn/conf/opmn.xml

  2. Find the process-type id whose value is the name of the instance in which Oracle Web Services Manager is installed. This may be "home", or it could be another instance name. For example:

    
...

<ias-component id="default_group">

   <process-type id="home" module-id="OC4J" status="enabled">

...

  3. Find the data id="java-options" in the category id="start-parameters" section of the file.

    
...

<category id="start-parameters">

   <data id="java-options" value="-server -XX:MaxPermSize=128M .../>

</category>

...

  4. Add the following parameters under java-options:

    Dhttp.proxySet = true

    Dhttp.proxyHost = proxy_server

    Dhttp.proxyPort = listen_port

    Dhttp.nonproxyHost = host_name

    Table 9-1 Parameter Settings for Oracle WSM installed as part of Oracle Application Server

    Parameter Value Description of Value

    true/false

    Set the value to true to enable the proxy server.

    proxy_server

    Name of the proxy server. For example, www-proxy.us.mycompany.com

    listen_port

    The port number on the proxy server where you wish to connect. For example, 80

    host_name

    Hosts that connect directly without intervention from the proxy server. This value can be a list of host names separated by a |, or *. For example, localhosts|*mycompany.com

  5. Restart the server for the configuration changes to take effect.

9.3.4 Correction to Information about importDBData

There is an error in Oracle Web Services Manager Deployment Guide, Appendix A, "Oracle Web Services Manager WSMADMIN Commands," in the section titled "importDBData."

The second bullet item under the heading "Usage" suggests that you "Ensure that the database schema is created before performing this operation." This suggestion is invalid, since the database schema is created during the importDBData operation.

  Previous
Previous 		 Next
Next
  Go To Documentation Library
Home		 Go To Table Of Contents
Contents