Thursday Feb 20, 2014

Top 10 solution documents for OWSM and OAG/OEG

The following are the top 10 documents that are linked to SRs as solutions, for  Oracle Web Services Manager (OWSM) and Oracle API Gateway (OAG/OEG ) , during the last quarter.

1481062.1 Enterprise Manager Cannot Invoke WS Policy Manager When Managed Servers SSL Port Is Enabled  According to the documentation
http://docs.oracle.com/cd/E23943_01/web.1111/b32511/diagnosing.htm#BABHEHHI.
which mentioned that by default the OWSM auto look up feature tries to connect over SSL.
1548712.1 The issue is caused by the absence of a prerequisite patch.
1586714.1 OAG 11.1.2.1 EM Grid Control Plug-in Not Collecting Data When Using Https  
This is a limitation of the plugin, which is to be addressed in a future release.  Enhancement 1675548 has been filed, but to this point, no indication has been given as to what version will include this functionality.
1540873.1 Poor Performance When Using OWSM Without Message Encryption The message body is parsed first by OWSM; and then later again by the Web Services stack; both are parsing each individual element in the message body.
1569900.1 Misconfigured Policy Accessor URL in config/fmwconfig/policy-accessor-config.xml or Any Inconsistent SSL configuration in the Weblogic Domain can break OWSM.
1574074.1 Security Violation: User: 'OracleSystemUser' has insufficient permission to access EJB wsm-pmserver-wls.jar  The message "'OracleSystemUser' has insufficient permission to access wsm-pmserver-wls.jar" can have the following root causes:  The OracleSystemUser does not exist in the environment, or does not have correct group membership, The role used by OWSM for policy access was changed, and that change was not carried out correctly,  A domain wide administration port was configured, and the OracleSystemUser does not have admin rights for that
1587522.1 Error Message "Attempted to remove a WLSExeucutionContext from the current WorkContextMap" When Using OWSM   The problem shows up when a new context is created during the execution of a Web Service request.
1535635.1 This document is intended to provide just a sample on how to make a setup and implementing a BPEL Compisite to call a web service in a different domain.
942623.1
1572265.1 Error Appears In Gateway Log Caused From Tcp Probes The messages are caused by TCP probes. These TCP probes can come from a hardware load balancer. The TCP probes can also come from software TCP probes.

About


This is the official blog of the Java Development Proactive Services Team. Here we will provide information on our activities, publications, product related information and more. We look forward to your feedback to improve what we do!

Search

Archives
« February 2014 »
SunMonTueWedThuFriSat
      
1
2
3
5
6
7
8
9
11
12
13
14
15
16
17
18
19
21
22
23
24
25
26
27
28
 
       
Today