Introduction:
Oracle JDeveloper 11g showcases new features to provide a full development environment for Java EE 5 – including EJB 3.0 and JSF 1.2 – and rounded out with new features for AJAX developers, including an impressive new ADF Faces rich client set of components as well as Javascript editing and debugging.
JDeveloper 11g marks a significant milestone in the progress of application development.Web services development is greatly improved with updated support for JAX-WS, a complete Web services test framework, and a comprehensive WSDL editor. There are also many developer productivity enhancements to the IDE and Java development features to explore. And, building applications with Oracle ADF has been dramatically improved with the addition of ADF Faces rich client, a new JSF-based ADF controller framework, and countless productivity-boosting enhancements.
JDeveloper now makes use of an installer to prevent errors during installation.
Features of the installer include:
a. Platform-specific(native) installers for Windows & Linux,including a bundled JDK.
b. Generic installer (without a JDK) for all other platforms.
c. Install into a new or existing Middleware home.
d. Perform a complete installation, or install just the components you need.
e. Create shortcuts in the Start menu on Windows.
f. QuickStart page after installation provides easy access to common tasks.
g. Installer supports 3 modes: GUI/graphical, console, and silent.
For more information, you can visit:
http://www.oracle.com/technology/products/jdev/collateral/papers/11/newfeatures/index.html
Technical posts containing information and solutions on Oracle Fusion Middleware 12c/11g/10g, AIA, Oracle BPEL PM, Mediator, OSB, MFT, ESB, OWSM, Business Rules, JDeveloper, Oracle Weblogic, Oracle Application Server etc..etc..
Wednesday, October 15, 2008
BPEL : ORABPEL-11622
Problem:
A "javax.transaction.RollbackException" is thrown when BPEL PM is under heavy load.
Error:
Caused by: ORABPEL-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore. [Caused by: Transaction has been marked for rollback: Timed out]
See root exception for the specific exception. You may need to configure the connection settings in the deployment descriptor
(i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml) and restart the server. Caused by Exception [TOPLINK-23005]
(Oracle TopLink - 10g Release 3 (10.1.3.1.0) (Build 061004)):
oracle.toplink.exceptions.TransactionException
Exception Description: Error binding to externally managed transaction
Internal Exception: javax.transaction.RollbackException: Transaction has been marked for rollback
Solution:
A step by step solution for this error is shown as under:
a. Goto SOA_HOME/bpel/domains//config
b. Open domain.xml and change syncMaxWaitTime to 1800.
(If the existing value is more than this don't make any changes here)
c. Goto SOA_HOME/j2ee/OC4J_SOA/application-deployments/orabpel/ejb_ob_engine
d. Open orion-ejb-jar.xml and change all the transaction-timeout values to 3600. (If the existing value is more than this don't make any changes here).
e. Goto SOA_HOME/j2ee/OC4J_SOA/config
f. Open transaction-manager.xml and change transaction-timeout value to 7200. (This value you could use as high as 60000, if needed).
A "javax.transaction.RollbackException" is thrown when BPEL PM is under heavy load.
Error:
Caused by: ORABPEL-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore. [Caused by: Transaction has been marked for rollback: Timed out]
See root exception for the specific exception. You may need to configure the connection settings in the deployment descriptor
(i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml) and restart the server. Caused by Exception [TOPLINK-23005]
(Oracle TopLink - 10g Release 3 (10.1.3.1.0) (Build 061004)):
oracle.toplink.exceptions.TransactionException
Exception Description: Error binding to externally managed transaction
Internal Exception: javax.transaction.RollbackException: Transaction has been marked for rollback
Solution:
A step by step solution for this error is shown as under:
a. Goto SOA_HOME/bpel/domains/
b. Open domain.xml and change syncMaxWaitTime to 1800.
(If the existing value is more than this don't make any changes here)
c. Goto SOA_HOME/j2ee/OC4J_SOA/application-deployments/orabpel/ejb_ob_engine
d. Open orion-ejb-jar.xml and change all the transaction-timeout values to 3600. (If the existing value is more than this don't make any changes here).
e. Goto SOA_HOME/j2ee/OC4J_SOA/config
f. Open transaction-manager.xml and change transaction-timeout value to 7200. (This value you could use as high as 60000, if needed).
Thursday, October 9, 2008
Setting Log level
Setting Log Level for BPEL
Steps:
1) Log in BPEL Console
2) Click on Manage BPEL Domain
3) Goto auditLevel and set the property to production, then click Apply.
4) Goto Logging, on the same page, and set all loggers to error and click on Apply.
Keep Learning...
Steps:
1) Log in BPEL Console
2) Click on Manage BPEL Domain
3) Goto auditLevel and set the property to production, then click Apply.
4) Goto Logging, on the same page, and set all loggers to error and click on Apply.
Keep Learning...
Tuesday, October 7, 2008
Setting for oc4j-ra.xml
Oracle recommends to modify the container settings in oc4j-ra.xml. By doing so, it increases the performance of the SOA server.
Steps:
1) Goto the location SOA_HOME/j2ee/oc4j_soa/application-deployments/default/DbAdapter
2) Open the file oc4j-ra.xml
Default Value:
<connection-pooling use="none">
</connection-pooling>
New Value:
<connection-pooling use="private">
<property name="waitTimeout" value="300"/>
<property name="scheme" value="fixed_wait"/>
<property name="maxConnections" value="100"/>
<property name="minConnections" value="0"/>
</connection-pooling>
3) Similarly, open the file oc4j-ra.xml present under location:
SOA_HOME/j2ee/oc4j_soa/application-deployments/default/AqAdapter
4) Change the default value to the New value as shown above for DB Adapter.
5) Bounce the SOA Server.
Keep Learning with me...
Steps:
1) Goto the location SOA_HOME/j2ee/oc4j_soa/application-deployments/default/DbAdapter
2) Open the file oc4j-ra.xml
Default Value:
<connection-pooling use="none">
</connection-pooling>
New Value:
<connection-pooling use="private">
<property name="waitTimeout" value="300"/>
<property name="scheme" value="fixed_wait"/>
<property name="maxConnections" value="100"/>
<property name="minConnections" value="0"/>
</connection-pooling>
3) Similarly, open the file oc4j-ra.xml present under location:
SOA_HOME/j2ee/oc4j_soa/application-deployments/default/AqAdapter
4) Change the default value to the New value as shown above for DB Adapter.
5) Bounce the SOA Server.
Keep Learning with me...
Subscribe to:
Posts (Atom)