Skip Headers
Oracle® Application Server Release Notes and New Features
10g Release 3 (10.1.3.5.1)
Part Number E15342-03
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
View PDF

7 Oracle Web Services Manager

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

7.1 Prevention of Messages Being Lost When Database Goes Down Intermittently

Previously, there were no retry attempts for database message logging when logging was configured in asynchronous mode and the database failed or was restarted.

This was resolved by implementing retry logic at the time of database failure or restart when the DBMessageLogWriter parameter is in asynchronous mode. There are also new configurable parameters for tuning the retry attempts:

7.2 Requests Without Security Header Allowed When Signing/Encryption Is Not Enforced

Previously, users received errors about a "Missing Security Header" even when the enforceSigning and enforceEncription parameters were not enabled. A code change was implemented so that if neither the enforceSigning nor enforceEncription parameter is set, then requests without security headers can still pass without throwing this error message.

7.3 Best Practices for Secure Use of Keytool

In "Administering Web Services Security" in Oracle Application Server Web Services Security Guide 10g, the examples provide for the keytool should be updated so that the password is not specified on the command line. This is a security vulnerability.

If you do not specify the password on the command line, then the keytool prompts you to input the password.

7.4 WSE 3.0 Interoperability for Oracle WSM Signed Messages

A Transform step has been added after the "Sign Message" step to correct the order of the Binary Security Token (BST) and the Security Token Reference (STR) elements in the WS-Security element, per the WS-Security specification, for WSE 3.0 (Microsoft.NET) clients.

7.5 Alarm Rule Name Limited to 35 Characters

Alarm rule processing creation no longer fails silently for component names with more than 35 characters. The 35-character limit is now enforced by the Oracle WSM UI.

7.6 Service Registration Page Now Handles WSDLs With Multiple Endpoints Properly

When entering a WSDL with more than one endpoint on the Add New Service page, the ensuing page now populates the correct service URL.

7.7 BPEL Web Service Names Shown Correctly On Statistic Pages For Server Agent

On Oracle WSM statistic pages for a server agent, the service name for BPEL Web Services now correctly shows all the file parts of the BPEL URL. For example: /orabpel/default/HelloWilli2/v2008_07_18__35620.

7.8 Workaround for Oracle WSM Hanging When Firewall With Time-out Configured Between IAS and the Database

Oracle WSM would hang when there was a firewall with a time-out configured between IAS and the database. This occurred because the database connection was closed by the firewall and the application hangs until the socket time-out.

As a workaround for this issue, follow these steps:

  1. The following properties for handling the eviction pool mechanism:

    cfluent.db.minEvictableIdleTimeMillis=1800000
cfluent.db.timeBetweenEvictionRunsMillis=-1

    Must be added to these files:

    $ORACLE_HOME/owsm/config/ccore/policyui-config-installer.properties
$ORACLE_HOME/owsm/templates/ccore/ui-config-installer.properties
$ORACLE_HOME/owsm/config/clientagent/clientagent-config-installer.properties
$ORACLE_HOME/owsm/config/coreman/monitor-config-installer.properties
$ORACLE_HOME/owsm/config/gateway/gateway-config-installer.properties
$ORACLE_HOME/owsm/config/policymanager/policymanager-config-installer.properties
$ORACLE_HOME/owsm/config/serveragent/serveragent-config-installer.properties

  2. Then all OWSM components must be redeployed, as follows:

    cd $ORACLE_HOME/owsm/bin
wsmadmin undeploy all
wsmadmin deploy all

  3. If a firewall is configured between IAS and a database, then the cfluent.db.timeBetweenEvictionRunsMillis parameter should be smaller then the time-out of the firewall in milliseconds.

7.9 Passing an Encrypted oc4j Password In the topology.properties File

When cloning an Oracle WSM application at the destination, run the wsmadmin.sh applyTopology command with the encrypted oc4jAdminPassword property added in the topology.properties file.

7.10 The wsmadmin Script Requests Passwords As Input Only and Not On the Command-line

The wsmadmin script now requests passwords as input, not via the command-line. This prevents passwords from being stored in plaintext in a log file, which might then be available to local users via the ps command, etc.

7.11 Oracle WSM Service Detail Pages Do Not Show Links For Downloading WSDLs

Oracle WSM has four Web Services: application ccore, coreman, policymanager, and gateway. Details of these services can be viewed using following URL:

http://<host>:<port>/<appication name>/services

Previously, all service detail pages were showing links to download WSDLs, and clicking those links would result in an exception with system directory information. The WSDL links are no longer displayed.

7.12 Option To Remove Oracle WSM Samples From Installation

A command-line interface, wsmadmin deleteSamples, allows users to delete samples that were installed during 10.1.3.5.1 installation.

7.13 ExportDBData Backup Works With Oracle Lite DB

The ExportDBData utility can be used to back up Oracle WSM data on an Oracle Lite database.

7.14 REST POST/GET Support Added to Test Web Service Page

The Invoke REST POST and Invoke REST GET buttons have been added to the Test Web Service page of Oracle WSM Control.

7.15 Migrating Oracle Web Service Objects

When migrating Oracle Web services objects, as described in "Migrating Oracle Web Services Objects" in Oracle Web Services Manager Administrator's Guide 10g (10.1.3.4), please note the following:

See also Section 7.16, "Using the Oracle WSM Horizontal Migration Wizard".

7.16 Using the Oracle WSM Horizontal Migration Wizard

Note:

The following section should be appended as a subsection to "Migrating Oracle Web Services Objects" in Oracle Web Services Manager Administrator's Guide 10g (10.1.3.4). The section describes how to use the Oracle WSM Horizontal Migration wizard to generate the LMTInstructions.xml files and migrate Oracle WSM objects quickly and easily.

You can continue to develop the LMTInstruction.xml files manually, if you prefer. The wizard provides you with another, simpler option.

The Oracle WSM Horizontal Migration wizard facilitates the horizontal migration of the following objects:

You can migrate one or more of the objects simultaneously between your development, test, and production environments using the Oracle WSM Horizontal Migration wizard by performing the following steps.

  1. Generate the export file.

    This file defines the Oracle WSM objects that you might want to migrate to the destination environment. It serves as a template to use when you are generating the import file in the next step.

    The file is named LMTExportInstructions<timestamp>.xml and is saved to your local directory on the source machine from where you want to export objects in a location that you specify.

    For more information, see Section 7.16.3, "Step 1: Generate the Export File".

  2. Generate the import file.

    You select the specific objects that will be migrated and configure properties, as required, in this step. The list of objects from which you can select are defined by the export file, created in Step 1. Before generating this file, you need to copy the export file, created in Step 1, to the destination machine.

    The file is named LMTImportInstructions<timestamp>.xml and is saved to your local directory on the destination machine from where you want to import objects in a location that you specify. The wizard uses the destination machine configuration details during the import file generation.

    For more information, see Section 7.16.4, "Step 2: Generate the Import File".

  3. Export the objects from the source environment using the export file created in Step 1.

    For more information, see Section 7.16.5, "Step 3: Export the Oracle WSM Objects".

  4. Import the objects to the destination environment using the import file created in Step 2.

    For more information, see Section 7.16.6, "Step 4: Import the Oracle WSM Objects".

  5. If you are migrating custom steps, copy the relevant JAR files from the source to the destination machine.

    For more information, see Section 7.16.7, "Step 5: Copy Custom Step JAR Files to Destination Machine (Optional)".

To save time if you are migrating to multiple environments, you can export all objects to generate one export XML file (in Step 1), and then selectively import the objects required to each destination machine. This way, a single export file can meet the requirements of multiple machines.

Note:

If you want to migrate all Oracle WSM objects and all data in the Oracle WSM Database, then use the Oracle WSM cloning feature described in "Cloning Oracle Web Services Manager".

7.16.1 Before You Migrate Oracle WSM Objects

Before you migrate Oracle WSM objects, verify that you have installed Oracle Application Sever 10g Release 3 (10.1.3.5.1) on both the source and destination machines.

The Oracle WSM Horizontal Migration wizard is configured using the coresv.properties file located in the ORACLE_HOME/owsm/bin directory, where ORACLE_HOME indicates the location where Oracle Application Server 10g is installed.

In this release, the following property has been added to the coresv.properties file to enable you configure the location of the log file to capture all steps and errors related to running the wizard:

lmt.logfile.directory = C:/LMT.log

7.16.2 Invoking the Oracle WSM Horizontal Migration Wizard

To invoke the Oracle WSM Horizontal Migration wizard:

  1. Open a command line interface.

  2. Navigate to the ORACLE_HOME/owsm/bin directory, where ORACLE_HOME indicates the location where Oracle Application Server 10g is installed.

  3. Enter one of the following commands:

    On Windows: wsmadmin.bat startHorizontalMigrationTool

    On Linux: wsmadmin.sh startHorizontalMigrationTool

7.16.3 Step 1: Generate the Export File

The Oracle WSM Horizontal Migration wizard enables you to generate quickly and easily the export file that defines the Oracle WSM objects that you want to migrate to another environment.

The file is saved to your local directory in a location that you specify, and is named as follows: LMTExportInstructions<timestamp>.xml. For example: LMTExportInstructions17Jul2009-08-50-07AM.xml.

For an example of the XML file format, see Example 10-1 "Example LMTInstructions.xml File Used to Export Objects" in "Migrating Oracle Web Services Objects" in Oracle Web Services Manager Administrator's Guide 10g (10.1.3.4).

To generate the export file:

  1. Start the Oracle WSM Horizontal Migration wizard on the source machine, as described in Section 7.16.2, "Invoking the Oracle WSM Horizontal Migration Wizard".

  2. Choose Generate export transferable objects xml and click Next.

    The ID and name of the components—Oracle WSM Gateways and Agents—that exist in the source environment are displayed.

  3. Click the check box next to each component that you want to export and click Next.

    The ID and description for the services that are active in the source environment are displayed.

  4. Click the check box next to each service that you want to export, if applicable, and click Next.

    The ID and name of each custom step defined in the source environment are displayed.

  5. Click the check box next to each custom step that you want to export, if applicable, and click Next.

    You are prompted to specify a location to save the export file.

  6. Click Include pipeline parameters with display name only flag if you want to show the display name only.

  7. Click Browse, navigate to the location where you want to save the export file, and click OK.

  8. Click Finish.

    The export file is generated and a message displays in the wizard to indicate where the file has been saved.

  9. Click Close to close the wizard.

7.16.4 Step 2: Generate the Import File

The Oracle WSM Horizontal Migration wizard enables you to generate quickly and easily the import file that defines the Oracle WSM objects that you want to migrate to the destination environment.

The file is saved to your local directory in a location that you specify, and is named as follows: LMTImportInstructions<timestamp>.xml. For example: LMTImportInstructions17Jul2009-09-14-59AM.xml.

For an example of the XML format, see Example 10-2 "Example LMTInstructions.xml File Used to Import Objects" in "Migrating Oracle Web Services Objects" in Oracle Web Services Manager Administrator's Guide 10g (10.1.3.4).

To generate the import file:

  1. Copy the export file (created in Section 7.16.3, "Step 1: Generate the Export File") from the source machine to the destination machine.

  2. Start the Oracle WSM Horizontal Migration wizard on the destination machine, as described in Section 7.16.2, "Invoking the Oracle WSM Horizontal Migration Wizard".

  3. Choose Generate import transferable objects xml and click Next.

  4. Click Browse, navigate to the location of the export file that you copied in Step 1, and click OK.

  5. Click Next.

    The ID and name of the components—Oracle WSM Gateways and Agents—and the properties that can be set for each are displayed.

    For an Oracle WSM Gateway, you can edit the following properties:

    • Import name—Name of the Gateway. The value defaults to the name of the Gateway originally specified in the export file.

    • Import URL—URL of the Gateway. The value defaults to the URL of the Gateway originally specified in the export file.

    • Create new—Flag that specifies whether to generate a new Gateway. This value defaults to true.

    • ID—This field is valid only if "Create new" is set to false. ID of the Gateway on the target machine to which the selected Gateway will be mapped. Select a value from the drop-down list.

    For an Oracle WSM Agent, you can set the following property:

    • Import name—Edit the name of the Agent, as required. The value defaults to the name of the Agent originally specified in the export file.

  6. Click the check box next to each component that you want to import, set the properties as required, and click Next.

    The ID and description of the services and the properties that can be set for each are displayed (if applicable).

    If a WSDL is defined for the service, you can set the following properties:

    • Import name—Name of the service. The value defaults to the name of the service originally specified in the export file.

    • Import URL—URL of the service. The value defaults to the URL of the service specified in the WSDL.

    • WSDL URL—URL of the WSDL file.

    For a WSDL is not defined for the service, you can set the following properties:

    • Import name—Name of the service. The value defaults to the name of the Agent originally specified in the export file.

    • Import URL—URL of the service. The value defaults to the URL of the service specified in the service pipeline property file.

  7. Click the check box next to each service that you want to import, set the properties as required, and click Next.

    The pipeline properties corresponding to the selected components and services are displayed (if applicable).

  8. Click the check box next to each property that you want to edit, modify the value as required, and click Next.

    The ID and name of the custom steps and the properties that can be set for each are displayed (if applicable).

    For a custom step, you can edit the following properties:

    • Import name—Name of the custom step. The value defaults to the name of the custom step originally specified in the export file.

    • Import ID—ID of the custom step. The value defaults to the ID of the custom step originally specified in the export file. During the import, all IDs are automatically generated except the custom step Import ID. If the custom step Import ID already exists on the destination machine, the import operation will fail. You must specify a custom step Import ID that is unique on the destination machine.

  9. Click the check box next to each custom step that you want to import, set the properties as required, and click Next.

  10. Click Browse, navigate to the location where you want to save the import file, and click OK.

  11. Click Finish.

    The import file is generated and a message displays in the wizard to indicate where the file has been saved.

  12. Click Close to close the wizard.

7.16.5 Step 3: Export the Oracle WSM Objects

After you generate the export file in Section 7.16.3, "Step 1: Generate the Export File", you can use it to export the Oracle WSM objects.

To export the Oracle WSM objects:

  1. Start the Oracle WSM Horizontal Migration wizard on the source machine, as described in Section 7.16.2, "Invoking the Oracle WSM Horizontal Migration Wizard".

  2. Choose Export objects and click Next.

    You are prompted to specify the location of the export file and the location where you want to export the objects.

  3. Click Browse, navigate to the location of the export file (created in Section 7.16.3, "Step 1: Generate the Export File"), and click OK.

  4. Click Browse, navigate to the location where you want to export the data, and click OK.

  5. Click Finish.

    The Oracle WSM objects are exported and a message displays in the wizard to indicate where data has been exported and where to access the log files.

  6. Click Close to close the wizard.

7.16.6 Step 4: Import the Oracle WSM Objects

After you generate the import file in Section 7.16.4, "Step 2: Generate the Import File", you can use it to import the Oracle WSM objects to the destination environment.

To import the Oracle WSM objects:

  1. Copy the exported data (created in Section 7.16.5, "Step 3: Export the Oracle WSM Objects") from the source machine to the destination machine.

  2. Start the Oracle WSM Horizontal Migration wizard, as described in Section 7.16.2, "Invoking the Oracle WSM Horizontal Migration Wizard".

  3. Choose Import objects and click Next.

    You are prompted to specify the location of the import file and the location where you want to import the objects.

  4. Click Browse, navigate to the location of the import file (created in Section 7.16.4, "Step 2: Generate the Import File"), and click OK.

  5. Click Browse, navigate to the location where you copied the exported data (in Step 1), and click OK.

  6. Click Finish.

    The Oracle WSM objects are imported and a message displays in the wizard to indicate where data has been imported and where to access the log files.

  7. Click Close to close the wizard.

7.16.7 Step 5: Copy Custom Step JAR Files to Destination Machine (Optional)

If you are migrating custom steps, copy the relevant JAR files into the ccore.ear and gateway.ear files under the ORACLE_HOME\owsm\ears\ directory on the destination machine.

To copy the source JAR files to the destination machine:

  1. On the destination machine (e.g., a Managed Server), extract the ccore.war file from the ccore.ear file.

  2. Add the source JAR files to web-inf\lib directory of the ccore.war file.

  3. Add the modified ccore.war file back inside the ccore.ear file.

  4. Repeats steps 1–3 for the gateway.ear file.

  5. Restart the destination Managed Server for the changes to take effect.

7.17 SAML Signature Verification Also Removes Security Token Reference That Refers to the SAML Assertion From the WS-Security Header

Previously, SAML signature verification could fail because the verification would remove the SAML assertion while leaving the security token reference in the message's WS-Security header. A code fix was implemented so that during SAML verification, SAML always removes the security token references of type SAMLAssertionKeyIdentifier, even if the message does not have any signatures.

7.18 Documentation Errata: Missing Step In "Configuring an Oracle J2SE Web Service Client Agent" Procedure

The procedure entitled "Configuring the Client Agent with the Oracle J2SE Web Service Client" in Chapter 6, "Installing Oracle WSM Agents" of the Oracle Web Services Manager Deployment Guide is missing the following final step:

7.19 Workaround For Using Groups

Since group is not supported in Oracle Web Services (10.1.3.5), you can use the following workaround.

If your schema contains the following group stanzas:

<xs:complexType name="Scope">
  <xs:sequence>
    <xs:group ref="ScopeAttributes"/>
    <xs:element ref="ScopeInformation" minOccurs="0" maxOccurs="unbounded"/>
  </xs:sequence>
</xs:complexType>
<xs:group name="ScopeAttributes">
  <xs:sequence>
    <xs:element name="Type" type="xs:string"/>
    <xs:element name="InstanceIdentifier" type="xs:string"/>
    <xs:element name="Identifier" type="xs:string" minOccurs="0"/>
  </xs:sequence>
</xs:group>

Then change your schema to match the following:

<xs:complexType name="Scope">
  <xs:sequence>
    <xs:element name="ScopeAttributes"/>
  </xs:sequence>
</xs:complexType>
<xs:complexType name="ScopeAttributes">
  <xs:sequence>
    <xs:element name="Type" type="xs:string"/>
    <xs:element name="InstanceIdentifier" type="xs:string"/>
    <xs:element name="Identifier" type="xs:string" minOccurs="0"/>
  </xs:sequence>
</xs:complexType>

7.20 30-Character Service Name Limitation In Web Services Database

The Oracle Web Services database supports a maximum of thirty characters for service names. Therefore, when Oracle Web Services imports a service from UDDI, it truncates the service name to thirty characters.

7.21 Supported wsmadmin Utility Commands on WebLogic Server

The Oracle Web Services command-line tool supports the following wsmadmin commands for deploying the CCORE, GATEWAY, POLICYMANAGER, COREMAN applications on WebLogic Server, as well as supporting the following WebLogic Server administrative commands.

7.22 The Configuration Wizard Must Be Used to Deploy Some Applications on WebLogic Server

The deployment of CCORE, COREMAN, GATEWAY, and POLICYMANAGER applications on WebLogic Server SOA platforms must performed using the Configuration Wizard or the Domain Template Builder tools. The wsmadmin utility should not be used to deploy these applications on WebLogic Server SOA platforms.

7.23 Creating and Saving a New Test For Future Use

The following steps describe how to create a new test and save it for future use.

  1. From the Saved Tests page, click Create New Test to open the Test Page.

  2. Specify the WSDL URL and click Submit Query.

  3. On the ensuing page, specify the parameters and click Save to save the new test.

7.24 Applications Deployed Using the WebLogic Server Administration Console May Throw an "Service Unavailable" Error

On occasion, applications started from the WebLogic Server Administration Console may throw an Error 503--Service Unavailable error. If this should occur, the applications should be restarted from the Administration Console to make them available again.

7.25 Duplicity of Service Name In Ping Scheduler Now Shows an Error Message

Previously, when a user attempted to add a duplicate service to the Ping Scheduler, it would throw an exception with a stacktrace, and would also enter error messages with a stacktrace in the log file. A code fix was implemented so that the Ping Scheduler displays a "duplicate service" error, but no stack trace is logged.

7.26 Ping Scheduler Now Alerts for Negative Delay Value

Previously, users were not alerted if they entered a negative delay value in the Ping Scheduler for a registered service. A code fix was implemented so that the following message is displayed if a negative value is entered in the Change Delay to field:

Delay value should be a positive integer from 0 to 9223372036854775807

7.27 utl_dbws Does Not Support WS-Security

A PL/SQL user can invoke Web services using the PL/SQL package SYS.UTL_DBWS. However, WS-Security security is not supported for Web services where UTL_DBWS is being used.

7.28 Removal of Extra ^M Characters from Installation Properties Files

The following installation properties files may contain extra carriage return (^M) characters:

As a workaround, you can use the dos2unix utility from a command-prompt to remove the extra ^M characters, as follows:

dos2unix <MyFile>

The dos2unix utility converts the file to UNIX format, removing any extra ^M characters, and overwrites the file to itself. Generally, the dos2unix executable is located in either the /usr/bin or /usr/local/bin directory.

7.29 After Installation Run wsmadmin Script to Update Schema

After installing Oracle Web Services Manager on Linux or Microsoft Windows, you must run the wsmadmin script in order to update the Oracle Web Services Manager schema, as follows:

Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Feedback page
Contact Us