Thursday 20 November 2014

Oracle Launches SOA Governance 11g or 12c installation : Enterprise Repository, Service Registry, SOA management with EM and Web Services Manager

Oracle SOA Governance 11g
Oracle has released Oracle SOA Governance 11g(component of Fusion Middleware)  which consists of following sub components
  • Oracle Enterprise Repository (single source of truth for SOA assets)
  • Oracle Service Registry (UDDI v3 compliant registry)
  • Oracle Enterprise Manager Pack Plus for SOA (pack to monitor runtime services)
  • Oracle Web Services Manager (tool to secure web services)
For press release about SOA Governance 11g click here
  • Two major components released as part of SOA Governance 11g are Oracle Service Registry 11g and Oracle Enterprise Repository 11g
  • Oracle SOA Governance 11g supports Oracle Applications including Oracle E-Business Suite and Siebel along with Oracle Application Integration Architecture (AIA).
  • Oracle Service Registry 11g software can be downloaded from here (Need Oracle/3rd Party Database)
  • Oracle Enterprise Repository 11g can be downloaded from here  (Need Oracle/3rd Party Database and Oracle/3rd Party Application Server)
  • For documentation on Oracle Service Registry 11g and Oracle Enterprise Repository 11g click here and go to end of page at OER Guides
  
Related/References 
http://www.oracle.com/us/corporate/press/057498
http://www.oracle.com/us/products/middleware/soa/governance/overview/index.html

Installation of Soa governance 12:-

http://docs.oracle.com/middleware/1213/oer/install-oer/install_gui.htm#OERIG378
http://docs.oracle.com/middleware/1213/oer/concepts-oer/intro.htm#OERQS376

Deploying Application on SOA/BPM domain : exception.71056.name: Access to internal workflow context is denied :

I discussed about SOA suite 11gR1 installation here, in this post I am going to cover issue I encountered while deploying application on SOA 11.1.1.6 Server .
Error while deploying application on SOA Server
______
Deploying on partition “default” of “/Farm_soa_domain/soa_domain/soa_server1″ …
Deploying on “/Farm_soa_domain/soa_domain/soa_server1″ failed!
There was an error deploying the composite on soa_server1: Deployment Failed: Error occurred during deployment of component: ManualAuthProcess to service engine: implementation.bpmn for composite: serv-manual-auth: BPM-71056
Exception
exception.71056.type: error
exception.71056.severity: 2
exception.71056.name: Access to internal workflow context is denied.
exception.71056.description: Requested access to internal workflow context is not allowed according to security policy.
exception.71056.fix: Contact Oracle support if exception can not be fixed
: Exception
exception.71056.type: error
exception.71056.severity: 2
exception.71056.name: Access to internal workflow context is denied.
exception.71056.description: Requested access to internal workflow context is not allowed according to security policy.
exception.71056.fix: Contact Oracle support if exception can not be fixed
_______
If you get above error then check following things in this order
1. Check BPM is enabled in Domain 
To check BPM is enabled in domain look for entry like below in $DOMAIN_HOME/bin/setDomainEnv.sh
EXTRA_JAVA_PROPERTIES=”${EXTRA_JAVA_PROPERTIES} -Dbpm.enabled=true”
If this entry is missing then extend the domain to include Oracle BPM Suite template as shown below and re-start domain



2. Check permission in $DOMAIN_HOME/config/fmwconfig/system-jazn.xmlfor  bpm-services.jar
Check that permission for bpm-services.jar contains minimum with entry like below (Add any missing permission) and restart SOA domain
_____
<grant>               <grantee>
                   <codesource>

                       <url>file:${soa.oracle.home}/soa/modules/oracle.soa.workflow_11.1.1/bpm-services.jar</url>
                   </codesource>
               </grantee>
               <permissions>
                   <permission>

                       <class>oracle.security.jps.JpsPermission</class>
                       <name>VerificationService.createInternalWorkflowContext</name>
                   </permission>
                   <permission>

                       <class>oracle.security.jps.service.policystore.PolicyStoreAccessPermission</class>
                       <name>context=APPLICATION, name=*</name>
                       <actions>getApplicationPolicy</actions>
                   </permission>
                   <permission>

                       <class>oracle.security.jps.service.policystore.PolicyStoreAccessPermission</class>
                       <name>context=SYSTEM, name=*</name>
                       <actions>getConfiguredApplications</actions>
                   </permission>
                   <permission>

                       <class>oracle.security.jps.service.policystore.PolicyStoreAccessPermission</class>
                       <name>context=SYSTEM, name=*</name>
                       <actions>getSystemPolicy</actions>
                   </permission>
                   <permission>

      <class>oracle.security.jps.service.credstore.CredentialAccessPermission</class>
                       <name>context=SYSTEM, mapName=BPM-SERVICES, keyName=BPM-SERVICES</name>
                       <actions>read</actions>
                   </permission>
                   <permission>

                       <class>oracle.security.jps.service.credstore.CredentialAccessPermission</class>
                       <name>context=SYSTEM, mapName=WF-ADMIN-USER, keyName=WF-ADMIN-CREDENTIAL</name>
                       <actions>read,write</actions>
                   </permission>
                   <permission>

                       <class>oracle.security.jps.service.credstore.CredentialAccessPermission</class>
                       <name>context=SYSTEM, mapName=BPM-CRYPTO, keyName=BPM-CRYPTO</name>
                       <actions>read,write</actions>
                   </permission>
                   <permission>

                       <class>oracle.security.jps.JpsPermission</class>
                       <name>IdentityAssertion</name>
                       <actions>*</actions>
                   </permission>
               </permissions>
           </grant>
_____

https://forums.oracle.com/message/10094583

Error while starting OAM WebLogic Servers “Policy store update operations are not allowed, system is write protected”

I’ve come across an issue in OAM 11g R2 PS2 environment. Multi Data Center is also being setup with one DC as Master and other DC as Clone. After configuring the Clone DC using T2P commands and running few WLST commands to accomplish MDC setup, the below errors were seen while starting the OAM WebLogic Admin/Managed Servers.
<Apr 8, 2014 4:28:05 PM PDT> <Warning> <oracle.oam.engine.policy> <OAMSSA-06342> <Bootstrap failed for handler oracle.security.am.common.policy.tools.upgrade.r2ps2.bootstrap.RMR2PS2BootstrapHandler!>
<Apr 8, 2014 4:28:05 PM PDT> <Error> <oracle.oam.engine.policy> <BEA-000000> <Policy store update operations are not allowed, system is write protected.
Analysis:
The OAM 11g documentation states “Clone Data Centers can be write protected so no updates can be made to the system or policy configurations”. So I had set WriteEnabledFlag flag in oam-config.xml to false. Therefore any updates to Clone DC for policy or system changes will fail.
You can verify this flag in oam-config.xml and it would look like:
<Setting Name=”WriteEnabledFlag” Type=”xsd:boolean”>true</Setting>
However the weblogic servers would start up fine.
Solution:
Even Clone DC should be Write Enabled.
Connect to weblogic admin server through wlst.sh and run commands as shown below:
wls:/oam_domain/serverConfig> domainRuntime()
Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help(domainRuntime)
wls:/oam_domain/domainRuntime> setMultiDataCenterWrite(WriteEnabledFlag=”true”)
Data center write enable flag set successfully
wls:/oam_domain/domainRuntime>

Oracle Upgrade – from R12.2.3 to R12.2.4

 I performed ERP Upgrade from 12.2.3 to 12.2.4. I would like to share the document, which contains the steps performed, according to environment. This is just to give an idea, user must review the following documents and take environment specific action:
  • Oracle E-Business Suite Release 12.2.4 Readme (Doc ID 1617458.1)
  • Applyng the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)
  • DataInstall and HRGLOBAL Application: 12.2 Specifics (Doc ID 1469456.1)
  • Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc ID 1594274.1)
You may download the file using the URL:R12.2.3 Upgrade to R12.2.4