How to use the TCP Monitor

Whats the use of TCP Monitor : Think about you have created all the BPEL Processes with hostname as localhost and then you want to deploy from different machine. If you try to make use of jdeveloper
to deploy, jdev will complain that the localhost is not the actual path. In case if you are not having any soa suite in your machine and you dint deploy to your local soa suite.

Inorder to bypass this issue, you can use the TCP Monitor, which will route to the server

Where you can find the TCP Monitor:Its available with the bpel bin folder,
C:\product\10.1.3.1\OracleAS_2\bpel\bin\obtunnel.bat

What need to mention in the TCP Monitor:
You just need to mention the routing hostname, port number.
Then you can deploy to the server with out doing any modification to the code.

Screenshot of TCP Monitor:

How to get the version of Oracle Database

1. Run the command in your sql window.

select * from v$version where banner like 'Oracle%';

2. When you login using SQLPlus, you will get to see the sql version first then the database version that you are logging in.

"weblogic.rjvm.PeerGoneException: ; nested exception is: weblogic.utils.NestedException: java.lang.NoClassDefFoundError: com/bea/xml/XmlException"

I was trying to create a connection with datasource lying in weblogic 9.2 from Oracle Jdeveloper Studio Version 10.1.3.3.

To create a application connection and integration connection with Oracle Jdeveloper we have to copy the "weblogic.jar" file from the "c:\bea\weblogic92\server\lib" folder to
Oracle Jdeveloper "D:\JDevstudio10133\jdk\jre\lib\ext" folder.
This setup will work for creating application connection and integration connection with oracle Jdeveloper. But when i run a java client which calls the datasource it is failing and throwing following error message.


"weblogic.rjvm.PeerGoneException: ; nested exception is:
weblogic.utils.NestedException: java.lang.NoClassDefFoundError: com/bea/xml/XmlException",

I dropped all the below jar files into the "D:\JDevstudio10133\jdk\jre\lib\ext" location and added these jar file into the project libraries.
Then i tried to run the java client and it worked. The java code is pasted below.

ojdbc14.jar
xbean.jar
xmlx.jar
xqrl.jar
wlxbean.jar
weblogic.jar

public class JavaClient {
public JavaClient()
{
}

public void getDataSourceConnection()
{
Context ctx = null;
Connection conn = null;
Statement stmt = null;
ResultSet rs = null;
DataSource ds = null;
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
ht.put(Context.PROVIDER_URL,"t3://hostname:9700");

try
{
ctx = new InitialContext(ht);
ds = (javax.sql.DataSource) ctx.lookup ("jdbc/BPELServerDataSource");
conn = ds.getConnection();

stmt = conn.createStatement();
stmt.execute("select * from domain");
rs = stmt.getResultSet();

while(rs.next())
{
System.out.println("The value of the domain id column is ==>"+rs.getString(1));
}
}
catch (Exception e)
{
System.out.println("Exception is: " + e.getMessage());
e.printStackTrace();
}
finally
{
try
{
ctx.close();
if (rs != null) rs.close();
if (stmt != null) stmt.close();
if (conn != null) conn.close();
} catch (Exception e)
{
System.out.println("Exception ==>"+e);
}
}
}

public static void main(String[] args) {
JavaClient jc = new JavaClient();
jc.getDataSourceConnection();
}
}

Please reply with your comment, if you are facing any issues.

How to create outbound connection pooling using datasource in weblogic server 9.2

Creating outbound connection pooling using the web console is not allowing to create and it defaults to the local instances.
So there is a workaround to do this, You can create the outbound connection pooling by editing the weblogic-ra.xml file.
weblogic-ra.xml file is the one, which holds all the eis connections. By default it has some examples, so we can copy and paste the existing connection information and edit for your use.
You can find the weblogic-ra.xml file under the following path
"C:\bea\user_projects\apps\bpelApps\DbAdapter\META-INF\weblogic-ra.xml"

After modifying the content, you need to restart the server. Stop the oracleBPELServer, Admin Server and nodemanager. Then bring all three up.
Test the outbound connection pooling that we created by navigating to outbound connection pooling page, the path for is as follows.

1. Click on the "Environmen" in the Domain Structure
2. Click on the Servers link.
3. Click on the "OracleBPELServer" link on the summary of server, available on the righside window.
4. Click on the "Deployments" tab.
5. Click on the "DbAdapter" from the list of Applications and Modules Deployed to this Server
6. Click on the "Configuration" tab
7. Click on the "Outbound Connection Pools" sub tab.
8. Expand the "javax.resource.cci.ConnectionFactory" available in the Outbound Connection Pool Configuration Table
9. Click on the "Testing" tab.
10. Check your Outbound Connection Pool and hit the "Test" button. You will get the result in the TestResult column.

If the result is success then the outbound connection is established, if it throws error, you need to go and check the xml tags in weblogic-ra.xml file.