ORACLE -B2B

B2B or business to business is a gateway which allows the secure exhange of document between enterprises.

Oracle B2B comes along with SOA Suite 11g.So there is no separate install for B2B in 11g.

Once your managed SErver is started you can check in the command console that B2B component is also started.Moreover in the deployments you can check the staus of B2B if it is ok or not.



So it shows its health is ok and is active so now you can just open the b2b console in a separte window by typing following url

http://localhost:8001/b2b

here 8001 is the port number for your managed server as b2b comes up with SOA server component.

so once you will start you will get a console like this




so i will just guide you through the look and feel of 11g b2b.

To create a new document in b2b go to document tab and click on plus button.

YOu will get different type of document definition like rosettanet,hl7,edi_x12 and along with that you have your custom document definition type.

For two enterprises to communicate with each other there are some pre requisite like they should follow a common document,common protocol should have some unique identifier to recognize who is the other enterprise (we call the other enterprise as trading partner).They need to have one common aggreement.So thats basically is the work of b2b that it provides a secure gateway for two enterprises to excahnge document.

oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer

After installing SOA Suite 11g when for the first time you will try to deploy a simple process you may get following error

[03:21:40 PM] Problem in sending HTTP request to the server. Check standard
HTTP response code for 502
[03:21:40 PM] Error deploying archive sca_Project1_rev1.0.jar to soa_server1
[localhost:8001]
[03:21:40 PM] HTTP error code returned [502]
[03:21:40 PM] No error message is returned from the server.
[03:21:40 PM] #### Deployment incomplete. ####
[03:21:40 PM] Error deploying archive
file:/C:/JDeveloper/mywork/Application1/Project1/deploy/sca_Project1_rev1.0.ja
r
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)


YOu can get rid of this issue by doing the following changes.

1>Go to weblogic console

Server->click on managed Server

and select configuration->General tab

There in listen address provide the listen address to the host name and restart the server.

2>Go to jdeveloper 11g and disable the proxy settings there.

Go to tools->Preferences->Web Browser and proxy and disable the use proxy http server

Exit and start the jdeveloper once again.

11g-creating jms resource

In weblogic console

expand Services click on Messaging and click JMS Modules over there.




Click on SOAJMS Module and you will get a screen like this



Click on new and choose queue.

Then say next



provide a name and a jms name to the queue



Select subdedployment as soasubdeployment and select SOAJMS Server



and say Finish

and you will get the queue created in the list of summary of resources




now we will create the connection factory for the queue

Create new on the Summary of resources and select connection factory



provide the name and the jndi name for the connection factory




Say next and finish.




You will find both the queue and the connection factory now in the Summary of resources tab.

Now we will create the connection pool

The connection pool is configured in the JMSAdapter application and it use some Deployment Plan.we will create a directory for the same because by default it deploys to the same directory with the same name.

So i have created a new directory structure

D:\oracle\Middleware\Oracle_SOA1\soa\jmsplan

Now go to weblogic console click on deployment and choose JMSAdapter



Now go to Configuration tab->outbound connection pools




Now select new and Select the factory oracle.tip.adapter.jms.IJmsConnectionFactory



Say next and provide the jndi name



Say Finish

Now provide the directory name we have created earlier and name the plan as plan.xml



Say ok and check the folder if it is correct where the plan is deployed.




Now check the Configuration tab
Expand the factory: oracle.tip.adapter.jms.IJmsConnectionFactory
Click on eis/jms/Queue1



Provide the connection factory location and say save

jms/ConnectionFactory1



No again go back to deployment check JMSAdapter and click on update




Check whether the deployment path plan is correct or not and say finish and you are done with jms conncetion.



All the other adapters are configured in a similar way.SO one can take help from either db adapter configuration or jms adapter configuration and configure for other adapters also.If face any difficulty post me.

11g-Creating connection pool/data source

Go to weblogic console

navigate to services->jdbc->data sources



go to data source and click on new

Once you will click on new you will get a new window like this




Provide the name of the data source and a jndi name.

Let all the other configuration be unchanged.



Say next and you will get the following page




Provide the details for the database you are trying to connect.



Test the configuration



Say next and target to SOA_SErver and say finish




Now you can get the newly created dataosurce in the list






We have completed how to create a data source however we still need to create connection pool and data sources to connect to the data base.So we will create a connection pool.

go to console and click on deployment



then all the deployments will appear up in the right screen.click on db adapter



Click the Configuration tab, and then click on the Outbound Connection Pools tab



Cilck on new

In the next page select javax.resource.cci.ConnectionFactory and say next



Provide some jndi name for the connection and say finish




The deployment plan will be saved in the location by default or you can provide your own directory structure and save the file.Say ok




Verify the deployment plan



Now go to configuration tab and select the connection pool you have created



Now provide the data source name in the xa data source.Press enter key to save the value and verify if it is saved.Using mouse to save it will not save the data so use enter key.



Save the changes and Go to the Deployments page to Update the DbAdapter. Click
Deployments and select the db adapter and say update



Let the default option be there to redeploy the application.Verify the deployment plan and say finish.



Now go back to connection pool verify the configuration again and check if you have all the entries data sources correctly mentioned there.NOw you have configured a connection pool and data source which can be used to connect to database.We will see some example later.

Create a connection from jdeveloper to the application server-11g

Select small window in the panel and Click on new






following screen will come up



SAy ok and provide the connection name



Provide authentication details and check the port and domain is mentioned correctly



Say next and test the connection



Say next and you are done with the connection.

Now create your own process and deploy.

Start Admin Server and Managed SErver for 11g

go to middlewarehome/user_projects/domains/(your domain)

and check if you have startWeblogic.cmd there

execute this command.



once it shows running status in the command console

open in browser the following link

http://localhost:7001
provide the user and password and check in the server tab in weblogic console.



As can be seen there are two managed server bam server and soa server.

We will be first working with soa server and later we will check BAM so we will start the soa server.

so once again we will go the same location

Middleware home/user_projects/domains/(your domain)/bin folder

Just find if you have startManagedWebLogic.cmd command there.

So execute this command like

startManagedWebLogic.cmd ManagerServerName

In my case it is soa_server1

so i will post following command

startManagedWebLogic.cmd soa_server1




It will ask for the credentials provide the credentials



Now wait till it started showing running status in the command console.

Once started running just refresh the weblogic console page and check the server tab

It will show the managed server as started.




Also check the em console

http://localhost:7001/em



so now every thing is set up properly and running.

You can cross verify if everything is fine or not by checking the deployment tab

if everything is up and running

Now we will try to learn how 11g works.