Steps to apply the patch in weblogic server

Steps to apply the patch in webLogic Server

1)    Copy the patch file local to your system.

2)    Extract the contents from the zip file. We will have a jar file and patch-catalog_xxx.xml.
Copy the files (AYBZ.jar and patch-catalog_22669.xml) to the appropriate cache_dir directory for the target system i.e, $MIDDLEWARE_HOME/utils/bsu/cache_dir.
Ex: /opt/fmw11g/utils/bsu/cache_dir

Note: The directory MW_HOME\utils\bsu\cache_diris created as the default patch download directory when you install Smart Update 3.3.0.

3)    Log in to the putty using target system credentials and run the below command to navigate to bsu folder.
cd /opt/fmw11g/utils/bsu

4)    Command to view the downloaded patches as below:[optional]
./bsu.sh -prod_dir=/opt/fmw11g/wlserver_10.3 -patch_download_dir=/opt/fmw11g/utils/bsu/cache_dir -status=downloaded -view -verbose
5)    Below is the command to install a patch
./bsu.sh -prod_dir=/opt/fmw11g/wlserver_10.3 -patchlist=AYBZ -verbose –install
6)    Command to check if the patch is installed:
./bsu.sh -prod_dir=/opt/fmw11g/wlserver_10.3 -status=applied -verbose –view

NOTE: We need to apply the Patches for WLS installation and not per domain. If we have a managed server in another machine in a domain (that is, set up with its own WLS installation), we need to install this patch on that other machine as well.
References:
1.    Patch Download Location: https://support.oracle.com/epmos/faces/ui/patch/PatchDetail.jspx?parent=DOCUMENT&sourceId=1903457.1&patchId=20523619

2.    Reference doc to apply the patch:
https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&sourceId=1903457.1&id=876004.1

Event Driven Network(EDN) In SOA 11g

Today we are going to discuss how to use EDN in SOA11g,

Events are used to handle the business operations i.e.to transfer the data. Events contains the data in form of XML. In SOA, Events are handled by using either Bpel or Mediator. A process which generates the event is called Event Publisher. A process which consumes the event is called Event Subscriber.

Events are completely follows Fire and Forget mechanism means, Event Publisher don’t wait for the response from Event Subscriber. Even Event Publisher don’t know any information about Event Subscriber and vice versa. Events may contains one publisher with multiple subscribers i.e. one to one as well as one to many.

Let consider an example which demonstrates the EDN. We are going to design two SOA composites i.e. Event Publisher Process, Event Subscriber Process.

Note : We can design both publisher and subscriber in a single composite as well as in two different composites.

Design Event Publisher Process :

• Create Bpel process as shown below

• Design the Xsd file as shown below

• Drag drop the invoke activity from component pallet and follow the below screen shots.

• Drag drop one assign activity and map the data from input variable to invoke input variable.

• Finally deploy the composite.

     

Design Event Subscriber Process :

•   Create Bpel process as shown below

• Click on add symbol as shown in the above screen shot and choose the required Event which we have created in Event publisher process

•  Localize the .edl and .xsd files to your current composite.

• Drag and drop the assign activity and perform the addition operation for calculating the Total marks.

•  The bpel process will look  like as follows.

Testing

• Request to the EDN publisher process 

• Check the instance dashboard in EM for subscriber process.

• Audit Trail of subscriber process.