Learn with Pavan

I had an issue in configuring the JDev 11g TP4. Earlier I had JDev 11g TP3 in my database and I wanted to install / configure TP4 in my database. But when I checked the scripts, I had seen that the tables and views and queues are same as TP3. So, I thought of removing TP3. For that I had to drop the adrs_soainfra user in the database (now it is renamed to jdev_soainfra).

When I tried to drop the user, I got an error : The ADRS_SOAINFRA cannot be dropped as there is a dependent queue IP_OUT_queue and it needs to be dropped first.

So, I had dropped it and again tried to drop the user. But again same error with different queue. So, I had created the following script to drop the related queues of this user and then dropped the user as follows:

SQL> set serveroutput off
SQL> set pages 1000
SQL> set head off

SQL> spool dropp.sql

SQL> select 'exec dbms_aqadm.stop_queue( queue_name => ''ADRS_SOAINFRA.'||name||''', wait => FALSE);' from dba_queues where owner='ADRS_SOAINFRA';

SQL> select 'exec dbms_aqadm.drop_queue( queue_name => ''ADRS_SOAINFRA.'||name||''');' from dba_queues where owner='ADRS_SOAINFRA';

SQL> select 'exec dbms_aqadm.drop_queue_table(queue_table => ''ADRS_SOAINFRA.'||queue_table||''',force=>TRUE);' from dba_queues where owner='ADRS_SOAINFRA';

SQL> spool off

Now run the dropp.sql using 'SYS' user.

Then execute the following to create the objects in the database. Please check the usernames carefully before creating the objects:

$ cd $JOH\rcu\integration\soainfra\sql

$ sqlplus sys/ as sysdba
SQL> @createuser_soainfra_oracle_all.sql jdev_soainfra SYSTEM TEMP
SQL> conn jdev_soainfra/
SQL> @createschema_soainfra_oracle_all.sql jdev_soainfra

Then configure JDEV 11g TP4:

1. From Tools > Preferences > Run > Select Integrated Server.

2. Ensure no proxy being set (if your database and jdev are in the same domain, then it is not needed).

3. Again from Tools > Configure SOA > enter the database details and click on Test.

That should work now. Enjoy the new version.

Frequently, when I am logging into ESB Console - http://localhost:7777/esb - I get the following error:

Designtime cache has not been initialized Please look in logs for following signs of failure. Fix them and restart. (a) Database access errors (b) ESB Bootstrap errors (c) OC4J class load errors (d) Product installation errors (e) Export ESB params and verify if host and port parameters are correct. Please contact Oracle Support if unable to fix the issue.

I figured out that this error could be due to multiple reasons. The two most frequent mistakes which I make are:

1. My database / database listener are NOT started and I start the SOA suite, due to which the above error is thrown. For this, just shut down the SOA Suite, start the database, then the database listener and then start the SOA Suite and that should help.

2. Incorrect deployment of the RAR files. I tried to deploy few standalone Resource adapters in the wrong directory and tried to invoke the WSDLs which use the RAR files. Although successfully compiled at design time, but at runtime, after the deploying the ESBs, when my ESB server is starting, this error is thrown.
In such cases, comment the RAR configuration in the oc4j-connectors.xml in the $ORACLE_HOME/j2ee//config directory and then try to restart.

Check the two log files (you can check other log files in the OC4J directory apart from these) to get the information, but these cover most of the error information:

a) $ORACLE_HOME/OracleAS/j2ee/oc4j_soa/log/coreman.log:

Example: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12516, TNS:listener could not find available handler with matching protocol stack
The Connection descriptor used by the client was:
//localhost:1521/XE

b) $ORACLE_HOME/j2ee/oc4j_soa/log/oc4j_soa_default_group_1/oc4j/log.xml:
Example: ESB bootstrap: Unknown error occured in constructor of ESB resource adapter
at oracle.tip.esb.configuration.ServiceBusConstants.getESBHome(Unknown Source)
at oracle.tip.esb.configuration.ServiceBusConstants.loadESBConfigs(Unknown Source)..............

Keep in mind that this error is due to incorrect setup / configuration issue and not an issue with the Product itself.

Recently, I have upgrade my SOA from 10.1.3.3 to 10.1.3.4. Luck enough, I didnt find any issues while upgradation :) , I thought of mentioning the articles, I found to be useful to note for the upgradation. Following are the articles for a quick reference for the upgradation:

727068.1 - Oracle Application Server 10g Release 3 (10.1.3.4) Patch Set Notes Addendum
553420.1 - How to find the latest MLR patch for BPEL/ESB 10.1.3.3
730601.1 - What Documents Follow Up For Bpel 10.1.3.3.1 Installation?
728366.1 - Alert Notice For SOA Customers Planning to Upgrade to 10.1.3.4

And this is one of the Bug which I find useful about the OPMN:

5964097 - OPMN PERFORMS ALWAYS A FORCEFUL SHUTDOWN IN 10.1.3.1

I am planning to write a quick reference section (QR) with all the tips for the programmers / administrators. This will help us to quickly check the list of to-do things. So, this is my first QR.

This is a quick reference to know what client side jar files are needed to be added in the CLASSPATH when we are trying to use JMS (in-memory/file or database) from an application client (java code or any other 3rd party JMS client). Following are the JAR files needed in the classpath:

Client-side JAR Files Required for OEMS JMS In-Memory and File-Based Lookup:

oc4jclient.jar -- $ORACLE_HOME/j2ee/<instance_name>
jta.jar -- $ORACLE_HOME/j2ee/<instance_name>/lib
jms.jar -- $ORACLE_HOME/j2ee/<instance_name>/lib
jndi.jar -- $ORACLE_HOME/j2ee/<instance_name>/lib
javax77.jar -- $ORACLE_HOME/j2ee/<instance_name>/lib
optic.jar -- $ORACLE_HOME/opmn/lib

(Required only if the opmn:ormi prefix is used in Oracle Application Server environment.)

Client-side JAR Files Required for OEMS JMS Database Lookup:

oc4jclient.jar -- $ORACLE_HOME/j2ee/<instance_name>
ejb.jar -- $ORACLE_HOME/j2ee/<instance_name>/lib
jta.jar -- $ORACLE_HOME/j2ee/<instance_name>/lib
jms.jar -- $ORACLE_HOME/j2ee/<instance_name>/lib
jndi.jar -- $ORACLE_HOME/j2ee/<instance_name>/lib
javax77.jar -- $ORACLE_HOME/j2ee/<instance_name>/lib
adminclient.jar -- $ORACLE_HOME/j2ee/<instance_name>/lib
ojdbc14dms.jar -- $ORACLE_HOME/j2ee/<instance_name>/../../oracle/jdbc/lib
dms.jar -- $ORACLE_HOME/j2ee/<instance_name>/../../oracle/lib
bcel.jar -- $ORACLE_HOME/j2ee/<instance_name>/lib
optic.jar -- $ORACLE_HOME/opmn/lib

(Required only if the opmn:ormi prefix is used in Oracle Application Server environment.)

Note: If you cant find jndi.jar in the above specified location, then it should be there available in $ORACLE_HOME/datadirect/sun/lib directory.

This quick reference should be helpful when programming with OC4J JMS.

I am so excited to see new JDeveloper 11g production release to the public. It has got tons of new features to play with. One interesting thing is that JDeveloper 11g now has a Installer :) which came as a surprise to me. Until now, we just unzip the package, but now, we have a cool installer, ofcourse as every oracle application install, this one too is a easy ride.

One major change that we have in this version is that the OC4J container is removed and BEA Weblogic container is used in place of OC4J. I was hurt by this because I like OC4J more than BEA. BEA app container is also a cool product and has a stronger foundation than OC4J. Still need to explore more on this area.

These are the quick installer steps for installing newwwwww JDeveloper 11g Production release:

We can see that this installation is similar to BEA Weblogic installation. Oracle has just managed to combine both the installers (Weblogic and JDeveloper).

And NOW for the JDeveloper 11g Interface

There are tons of new features in this release and can they can be checked here.

The quick tutorials can be found here.

One sad thing I felt is SOA part is removed from this release. From FAQs, I found that it will be released when SOA Suite 11g is released.

Sooo, until then enjoy the new JDeveloper 11g for developing ADF, Fusion and J2EE apps :)