oraclesoa.blogspot.com
Oracle SOA Suite: April 2009
http://oraclesoa.blogspot.com/2009_04_01_archive.html
Sunday, April 12, 2009. How-To Reload Fault Policy in 10.1.3.4. In 101.3.4 you can reload the fault polcies that are changed and does not need a system restart simply access the following JSP page and all the fualt-policies are reloaded. Http:/ YourHost : YourPort /BPELConsole/ YourDomainName /doReloadFaultPolicy.jsp. Posted by Kalyan Bitra. Subscribe to: Posts (Atom). View my complete profile. How-To Reload Fault Policy in 10.1.3.4. Play and sharpen your brains! Play this free game now!
oraclebpelindepth.blogspot.com
Oracle BPEL In Depth: October 2008
http://oraclebpelindepth.blogspot.com/2008_10_01_archive.html
Oracle BPEL In Depth. Thursday, October 30, 2008. Default Retired BPEL process. How did I find this? I was testing the rollback of BPEL. Processes. That is when I found this behaviour. What was the setup? There were 2 versions of a BPEL. Say version 1.0 and version 1.1. Version 1.1 was deployed. Version 1.0 was retired. What I wanted to do? Now I wanted to rollback to version 1.0. So I retired version 1.1. Set version 1.0 as default. All this was done using the Java API. If you ask me why java API. Well ...
oraclebpelindepth.blogspot.com
Oracle BPEL In Depth: August 2008
http://oraclebpelindepth.blogspot.com/2008_08_01_archive.html
Oracle BPEL In Depth. Friday, August 22, 2008. Correspond manual recovery back to the BPEL process. Looks complex, but is it? Manual recovery of BPEL process does not look like a trivial job at all. And the BPEL Console for manual recovery does do seem to reveal a lot of information as to which process corresponds to which instance of BPEL process in the first glance. Why do instances end up in manual recovery? Well this is to do with how BPEL engine handles in coming messages. Recover only those message...
another-soa-blog.blogspot.com
fred's integration blog: June 2009
http://another-soa-blog.blogspot.com/2009_06_01_archive.html
Matter faced during integration project. Tuesday, June 23, 2009. Error while processing xpath expression * * the reason is FOTY0001: type error. Funny issue last time, might be useful to share it. Worked with JDev on a BPEL process and opened a transform activity. Then before it loads the "Source Part" and the "Target Part", I clicked on the "ok" button to move out of there. But JDev saved the transform activity with empty "Source Part" and "Target Part". The complete error message was:. Web-app xmlns="h...
another-soa-blog.blogspot.com
fred's integration blog: Using AD authentication with OC4J within Oracle Enterprise Manager
http://another-soa-blog.blogspot.com/2011/02/using-ad-authentication-with-oc4j.html
Matter faced during integration project. Thursday, February 17, 2011. Using AD authentication with OC4J within Oracle Enterprise Manager. Here are the steps to authenticate a WAR application using AD. 1 Setup your file WEB-INF/web.xml in your web application with settings similar to above:. 2 As I set the group name in web.xml to be the one on the Active Directory, I don't need to edit/add the file META-INF/orion-application.xml. In case you need, you do it with settings similar to above:. Geneva, Switze...
another-soa-blog.blogspot.com
fred's integration blog: Using OWSM and BPEL PM behind a proxy
http://another-soa-blog.blogspot.com/2009/11/using-owsm-and-bpel-pm-behind-proxy.html
Matter faced during integration project. Wednesday, November 25, 2009. Using OWSM and BPEL PM behind a proxy. We use OWSM and BPEL PM to consumme services outside our network. Nothing to fancy so far, we had to modify the JVM settings and add the following parameter:. DhttpproxyHost = proxy server. DhttpproxyPort = listen port. DhttpnonproxyHost = *localhost *domain.com. In our case this was:. DhttpproxyHost = www-proxy.outsourcing.com. DhttpnonproxyHost = *outsourcing.com. Dhttps.proxyPort = 80. Geneva,...
another-soa-blog.blogspot.com
fred's integration blog: July 2009
http://another-soa-blog.blogspot.com/2009_07_01_archive.html
Matter faced during integration project. Tuesday, July 7, 2009. Web Services standard security implementation overview. Web Services standard security implementation overview. Before Web Services can be used, security issues need to be addressed and security requirements such as authentication, access control, non-repudiation, data integrity, and privacy must be tackled by the underlying security technology. Authentication: ensure the business partner is who he pretends to be. If providing the logged in ...
another-soa-blog.blogspot.com
fred's integration blog: BPEL and Oracle Siebel CRM On Demand
http://another-soa-blog.blogspot.com/2010/02/oracle-siebel-on-demand-session-and.html
Matter faced during integration project. Tuesday, February 16, 2010. BPEL and Oracle Siebel CRM On Demand. When integrating OCOD (aka Oracle Siebel CRM On Demand) using BPEL and Java application,. 1 keeping credentials session open with Oracle CRM On Demand because OCOD accept only 10 concurrent session it is faster to re-use existing session. 2 OCOD refuse 2 request to be made without 50ms between each requests. 3 session need to be reset if OCOD server restart. The code for this proxy is located here:.
another-soa-blog.blogspot.com
fred's integration blog: November 2009
http://another-soa-blog.blogspot.com/2009_11_01_archive.html
Matter faced during integration project. Wednesday, November 25, 2009. Using OWSM and BPEL PM behind a proxy. We use OWSM and BPEL PM to consumme services outside our network. Nothing to fancy so far, we had to modify the JVM settings and add the following parameter:. DhttpproxyHost = proxy server. DhttpproxyPort = listen port. DhttpnonproxyHost = *localhost *domain.com. In our case this was:. DhttpproxyHost = www-proxy.outsourcing.com. DhttpnonproxyHost = *outsourcing.com. Dhttps.proxyPort = 80.
another-soa-blog.blogspot.com
fred's integration blog: enable LDAP over SSL (LDAPS) in OC4J
http://another-soa-blog.blogspot.com/2011/03/enable-ldap-over-ssl-ldaps-in-oc4j.html
Matter faced during integration project. Wednesday, March 30, 2011. Enable LDAP over SSL (LDAPS) in OC4J. To enable LDAP over SSL in OC4J, the certificate use by the LDAP server must be imported in the LDAP client. More specificaly it will be imported into the default keystore used for the JVM. The steps to do that are:. Upload the certificate (mycert.cer) to your server. Connect to your server and go to directory:. PATH TO ORACLE INSTALL/ias/product/asmt 10131/jdk/jre/lib/security.