Create your first SOA Composite - Hello World ! Process

 Start JDeveloper.  Left click Applications node in the Applications Navigator and select New Application, as shown

Create an Application named Training.

Give “Training” in Application name

Select a suitable location and select SOA Application in the Application Template

The wizard now prompts you to create a project.  Later, you can add more projects to this application.

Give the project name as HelloWorld

Select Composite template as Composite with BPEL Process.  This is a convenient shortcut to tell that the composite we want to create would contain one BPEL process.  As an alternative, we can choose Empty Composite here,  add add a BPEL

 component later.

Click on Finish

A new dialog opens up.  This is to configure the BPEL component that we are adding to our composite.

Give name as HelloWorld_BPEL

Select Template as Synchronous BPEL Template and click ok.

 Templates are pre-defined structures provided by Oracle.  Essentially, by using a template, a few activities shall come by default, so that you are saved of the mundane steps of adding those activities.  It’s even possible to create your own custom templates.  As of now, we select the predefined template for a synchronous process.  A synchronous process is one which is expected to be comparatively short-lived (few seconds to minutes) and hence can be expected to return a response quite quickly.  So, the client invoking a synchronous process can afford to wait (and block) for the response to come back.

The following structure comes up.

This is the picture of the composite (more technically, it’s the design time view of composite.xml).  As you can see, it contains a servicecomponent called HelloWorld_BPEL and a binding component called helloworld_bpel_client.

Service components are the building blocks that you use to construct a SOA composite application. Examples - BPEL, Human Task, Business Rules, Mediators, Spring.

Bindingcomponentestablish a connection between a SOA composite and the external world.  They are categorized as Service binding component and Reference binding components.  Service binding components provide the entry point to the composite Reference binding components provides access to the external service in the outside

world.  Examples include JCA Adapters (FTP adapter, DB adapter, Apps adapter etc), HTTP Binding, Direct binding etc.

Double click on this component to open it up.

As you can see, there is an input coming from the helloworld_bpel_client service binding  (which represents any client that is invoking our BPEL process).  

Drag an Assign activity from the component palette on the right.

In this assign activity, we can add any number of “Copy rules”.  Copy rules allow us to copy values from a source variable to a target variable, or to assign result of an expression (say a concatenate operation or a square root operation) to a target variable.

We want to create an expression similar to

“Hello” + Input = Output.   

This we shall create using the following steps:

Expand output variable so that you can see client:result.  This is the string field to which we want to assign some value.

From the icons on top right corner, drag an expression  onto client:result.

A dialog called Expression Builder opens up.  Expression builder is a nifty tool to quickly create expressions.  It shows categories of operations.  You choose a category and it shows you the expressions within that category.   For example

Here we choose “concat” function from the String Functions category

Click on Insert into expression.  This puts the concat() into the Expression box above.  (When you get experienced, you can simply write functions directly here.).  Place the mouse cursor between “(“ and “)” of the concat function

Next we expand the input and select the client:input field.  This is the field that has got the value that was sent by the user.  We want to append hello to this and assign that to the output variable.  So choose this

Press Insert into expression

Type ‘Hello’ followed by a comma.    Note that in BPEL, (or more precisely xpath) we use single quotes for strings

Now press OK.  Control returns to Edit Assign dialog.  Now expand the outputVariablein the To section (right section) and select client:result field.  Press OK

This has completed the Assign activity.  For better readability we should always give descriptive names to activities.  

So double click on the text “Assign1” (not the icon) and give name as “Assign_Hello”  

The BPEL process is now complete !

BPEL Persistence properties are used to control, when and how a process need to be dehydrated.

1. inMemoryOptimization

This property indicates to Oracle BPEL Server that this process is a transient process and dehydration of the instance is not required. When set to true, Oracle BPEL Server keeps the instances of this process in memory only during the course of execution. This property can only be set to true for transient processes (process type does not incur any intermediate dehydration points during execution).

• false (default): instances are persisted completely and recorded in the dehydration store database for a synchronous BPEL process.

• true: Oracle BPEL Process Manager keeps instances in memory only.

2. completionPersistPolicy

This property controls if and when to persist instances. If an instance is not saved, it does not appear in Oracle BPEL Console. This property is applicable to transient BPEL processes (process type does not incur any intermediate dehydration points during execution).

This property is only used when inMemoryOptimization is set to true.

This parameter strongly impacts the amount of data stored in the database (in particular, the cube_instance, cube_scope, and work_item tables). It can also impact throughput.

• on (default): The completed instance is saved normally.

• deferred: The completed instance is saved, but with a different thread and in another transaction, If a server fails, some instances may not be saved.

• faulted: Only the faulted instances are saved.

• off: No instances of this process are saved.

<component name="mySampleBPELComponent">
...
<property name="bpel.config.completionPersistPolicy">faulted</property>
<property name="bpel.config.inMemoryOptimization">true</property>
...
</component>

3. oneWayDeliveryPolicy

The oneWayDeliveryPolicy is from the Oracle 10g configuration property deliveryPersistencePolicy.The new configuration property name is bpel.config.oneWayDeliveryPolicy.

This property controls database persistence of messages entering Oracle BPEL Server. Its used when we need to have a sync-type call based on a one way operation. This is mainly used when we need to make an adapter synchronous to the BPEL Process.

By default, incoming requests are saved in the following delivery service database tables: dlv_message

• async.persist: Messages are persisted in the database.

• sync.cache: Messages are stored in memory.

• sync: Direct invocation occurs on the same thread.

--------------------------------------------------------------------------------------------------------------

#291 BPEL configuration properties

Rule of thumb for BPEL is - keep those processes short and sweet.
Transient, synchronous is the way to go, if possible.

ORCL docs provide for very good reading in this area - I recommend the FMW Developer Guide for SOA Suite, the FMW SOA Suite Administrators Guide as well as the FMW Performance Guide. The info below, has to a great extent, been taken from there. I also recommend AnTony Reynolds and Matt Wright's - Oracle SOA Suite 11g Developers Guide - available here

Tuning BPEL Engine Threads -

These are the guys who do the actual work -

The dspInvokeThreads property specifies the total number of threads allocated to process invocation dispatcher messages. Invocation dispatcher messages are generated for each payload received and are meant to instantiate a new instance. If the majority of requests processed by the engine are instance invocations (as opposed to instance callbacks), greater performance may be achieved by increasing the number of invocation threads. Higher thread counts may cause greater CPU utilization due to higher context switching costs.


The dspEngineThreads property specifies the total number of threads allocated to process engine dispatcher messages. Engine dispatcher messages are generated whenever an activity must be processed asynchronously. If the majority of processes deployed are durable with a large number of dehydration points (mid-process receive, onMessage, onAlarm, and wait activities), greater performance may be achieved by increasing the number of engine threads. Note that higher thread counts can cause greater CPU utilization due to higher context switching costs.

The dspSystemThreads property specifies the total number of threads allocated to process system dispatcher messages. System dispatcher messages are general clean-up tasks that are typically processed quickly by the server (for example, releasing stateful message beans back to the pool). Typically, only a small number of threads are required to handle the number of system dispatch messages generated during run time.

Start off with the defaults, and tune - if necessary - paying attention to the heuristics above.

These properties can be set in EM. 

As you can see, the Audit Level is set to Inherit as default. Please see my My Post on Logging for more info.

Here is the doc -

For production systems - use Production or Error - depending on your logging requirements.

Audit Detail threshold - under the threshold? - details store in the audit_trail table.
over the threshold? then audit info will be written to the audit_details table.

Large Doc Threshold - same concept -

This is the maximum size (in kilobytes) of a BPEL variable before it is stored in a separate location from the rest of the instance scope data.

Payload Validation - validates incoming and outgoing XML documents 
Incurs a performance hit.

Other Configuration properties

Now let's look at the rest -

As you can see, the descriptions shown in EM are useful and succinct.
You will not change most of these, however - some are worth investigating -


For one way invokes with possible callbacks -

Per default requests to execute a BPEL process are written to the soa_infra.dlv_message table - this causes a message to be generated that is then picked up by a worker thread which then starts executing the process.

Big benefit - Reliability no requests get lost - however we do have an extra DB write.

If set to async.cache then the request is cached in-memory - better Performance

If set to sync -> queuing is bypassed, and the BPEL process is invoked synchronously.
Client has full control of what happens.


1. bpel.config.oneWayDeliveryPolicy
Default value specified in MBean - accessible from em

async.persist: Messages are persisted in the database hash map.
sync.cache: Messages are stored in memory.
sync: Direct invocation occurs on the same thread.

Can be overwritten in the BPEL process definition in composite.xml -

onewayDeliveryPolicy=sync
and
transaction=required
BPEL process runs in the same thread and the same transaction.

onewayDeliveryPolicy=sync
and
transaction=requiresNew
BPEL process runs in the same thread but within a new transaction.

completionPersistPolicy

Here you need to ask yourself, whether the instance data needs to be persisted, and if so to what extent.
If your BPEL process integrates System A with System B. then the fact that the data has been successfully written to B suffices.

Simple example -

here is my one-way BPEL process that writes its input to a file -

Test - here is the output order.

Here is the em trace -

Now I set the the completePersistPolicy to off in composite.xml -
I also need to set inMemoryOptimization = true

Re-test - my output file has been written.

Check the audit trail in em -

Probably faulted would be the best setting here.

The SyncMaxWaitTime property sets the maximum time the process result receiver
waits for a result before returning. Results from asynchronous BPEL processes are
retrieved synchronously by a receiver that waits for a result from Oracle BPEL Server.
The default value is 45 seconds.

If you have sync BPEL processes and you see the need to up this property, then consider making the processes async.

MaxRecoverAttempt - number of times to attempt recovery of invoke/callback messages.

The recovery behavior for invoke and callback messages is different when
MaxRecoverAttempt is set. For example, assume MaxRecoverAttempt is set to 4.
■ Invoke message recovery is retried 4 (N) times before moving the message to
the exhausted state.
■ Callback message recovery is retried 5 times (N + 1) before moving the
message to the exhausted state.
This is the expected behavior. The first attempt is not counted as a recovery
attempt. The recovery attempts are incremented by the BPEL process service
engine. If MaxRecoverAttempt is set to 1, you see one default resolution process
and then one recovery attempt.

Recovery Configuration

This feature is detailed in the Administrator’s Guide for Oracle SOA Suite and Oracle
Business Process Management Suite


e.g. We are trying to update a DB and it is temporarily unavailable.

This covers -
All activities (for example, wait activities and OnAlarm branches of pick activities)
that have an associated expiration date and are scheduled with the SOA
Infrastructure to be rescheduled
■ All activities that are not complete over a provided threshold time

■ All invoke and callback messages that are unresolved

When should auto-recovery be available?
Check out the RecurringScheduleConfig - set start/stopWindowTime

Check out StartupScheduleConfig -
the default config tells us -

maxMessageRaiseSize The maximum number of messages to submit for each startup
recovery attempt. Use this property to limit the impact of recovery on the server. This value specifies the maximum number of messages to filter from activity, invoke, and callback
queries; that is, 50 messages from each of the activity, invoke, and callback tables.

startupRecoveryDuration -
Specifies the number of seconds that the startup recovery period
lasts. After the server starts, it goes into a startup recovery
period. During this period, pending activities and undelivered
callback and invocation messages are resubmitted for
processing.
The default value is 600 (ten minutes). A negative or zero value
disables startup recovery.

 

Partner Link Properties

The main ones ares -

nonBlockingInvoke=true
PartnerLink Service will executed in a separate transaction.

idempotent=false
Executes on same Thread/transaction

 

Creating a Simple BPEL Process : HelloWorld BPEL

Business Process Execution Language(BPEL) is an execution language for defining business processes. In short, it is the language for orchestrating multiple WebServices based on the business logic.

This post is about creating your first BPEL process using Oracle SOA Suite 11g

This is a simple BPEL process that gives back fullName as response, inputs being firstName & lastName

Defining your first BPEL Process

Create a new Project, name it HelloWorldBPELPrj and select Empty Composite in the next screen'

Define a Schema as follows

In the composite file, drag and drop BPEL Processcomponent from the Component Palette into the Components swimlane of the composite.xml

This will open up a wizard where you need to give the following details

Name : HelloWorldBPEL

Template : Syncrhonous BPEL Process

Select Input and Outputfrom the schema just created

Select the checkbox "Expose as a SOAP WebService" so that it creates a WebService with the same message types in the External References section of the composite.xml, though which external clients talk to this BPEL process

This will create the following in the composite.xml

Now that you've created the skeleton, lets implement the BPEL process.

Either open the .bpel file from the Navigator or double click the BPEL process icon in the coposite.xml - this will take you to the BPEL Component Editor where you'll implement the business logic in the BPEL process

When you look at the empty BPEL process, you'll find an incoming line from the external WS to Receive Activity, and an outgoing line from Reply Activity to the same external WS. These lines represent the flow of message to and from the WS to the BPEL Process

Note : Every operation in a BPEL process is called an Activity

Click on the "X" symbol in the boundary enclosing both the activities. The boundary is called a Scope in BPEL, which is similar to Scope in any programming language

This will open up variables section, where you'll see 2 variables (inputVariable and outputVariable). The inputVariable contains the the value coming into the BPEL process from the external WS.

In this example, inputVariable contains just a simple string, name

We need to concatenate this with 'Hello ' and assign it to the output variable. This can be done using Assign activity

Drag and drop Assign activity in between the two activities, name it AssignOutput

Here, we need to concatenate both the elements from the input and assign it to the output.  

 

For this, click on the Expression icon at the top right as shown

Use the concat() function from the String functions and append Helloto the name from the inputVariable, as shown

This will create a function icon in the middle of the Assing editor, where you need to drag this to assign it to the returnMsg of the outputVariable and click OK

With this, the outputVariable is stuffed which is sent back to the calling WS(indicated the outgoing line)

Thats it, you are done with your first BPEL process

Deploy the project as per this linkand test it in Enterprise Manager

Hope this tutorial gave you a basic understanding on working with a BPEL process.

Thanks for going through my post, feel free to provide a feedback!

※ 참고사이트 : http://middlewareschools.com/bpel-in-helloworld

                      https://chendamok.wordpress.com/2013/10/19/soa-bpel-project-helloworld/ (SOA BPEL Project : HelloWorld)

Transaction timeout can be configured for BPEL in 11g using the below properties.

※ JDeveloper Setting : Windows - Preferences - SOA - C:\Oracle\MiddleWare2\jdeveloper\lib\aia.jar

1. SyncMaxWaitTime

Description : The maximum time a request/response operation will take before ti times out. The default value is 45 seconds.

Maximum time BPEL process wait before returning result to client(or another Sync process)

To set this property

a. Login to EM console

b. Expand SOA and right click on “soa-infra”

c. From context menu, select SOA Administration –> BPEL properties

d. Click on “More BPEL Configuration properties…”

2.Transaction Time-out for BPEL EJB’s

The following EJB’s need to be configured for transaction time outs.

• BPELActivityManagerBean
• BPELDeliveryBean
• BPELDispatcherBean
• BPELEngineBean
• BPELFinderBean
• BPELInstanceManagerBean
• BPELProcessManagerBean
• BPELSensorValuesBean
• BPELServerManagerBean

To change time out for these beans ,

a. Login to Administration Console

b. Click on Deployments

c. Expand soa-infra –> EJB’s

d. Click on EJB for which you want to change the timeout

e. Click on Configuration

f. Change value for field “Transacion Timeout”

g. Click Save.

3. Global Transaction Timeout

This property is timeout in seconds for active transactions. After this time, if the transaction is still “Active”, then it gets rolled back.

To change this value

a. Login to Administration Console

b. Expand “Services” –> Click on “JTA”

c. Click on “JTA” tab if it’s on a different tab

d. Change value for field “Timeout Seconds”

Very Important :

SyncMaxWaitTime < BPEL EJB's transaction timeout < Global Transaction Timeout

Restart Weblogic server .

• MW_HOME/ORACLE_SOA/rda
• MW_HOME/oracle_common/rda

Oracle SOA Suite 11g, Resequence messages in Mediator

“A Resequencer is used to rearrange a stream of related but out-of-sequence messages back into order. It sequences the incoming messages that arrive in a random order and then send them to the target services in an orderly manner. The sequencing is done based on the sequencing strategy selected.”
For the resequencer to work we need to have 2 values in the source payload. The first one is a sequenceID, and the next one is a groupdID. The sequenceID will be used as identifier for the message itself. The groupID will be used to group the messages in which the resequencer will rearrange the messages based on the sequenceID. Different groups will have seperate processing, so they won’t have any influence on each other.
The mediator supplies us 3 types of resequencers :

• Standard Resequencer
• FIFO Resequencer
• BestEffort Resequencer

 

 

Let’s test the first one.
For this i created the next composite

In here i just map the input of the process 1on1 to the File adapter, which will store the input of the process on filesystem.
Interface of the composite

01	<?xml version="1.0" encoding="UTF-8"?>

02	<schema attributeFormDefault="unqualified"

03	elementFormDefault="qualified"

04	targetNamespace="http://xmlns.oracle.com/Application1_jws/MyReSequence/ProcessEmployees"

05	xmlns="http://www.w3.org/2001/XMLSchema">

06	<element name="process">

07	<complexType>

08	<sequence>

09	<element name="empID" type="string"/>

10	<element name="empType" type="string"/>

11	<element name="empName" type="string"/>

12	</sequence>

13	</complexType>

14	</element>

15	<element name="processResponse">

16	<complexType>

17	<sequence>

18	<element name="result" type="string"/>

19	</sequence>

20	</complexType>

21	</element>

22

</schema>

 

Configuration of the sequencer

Doubeclick the mediator component in the composite.

For the Resequence Level we can select ‘operations’ or ‘component’.
For Mediator components which only have 1 operation it doesn’t matter which one we select. For a Mediator component which consists of more then 1 operation and selecting the ‘component’ option means resequencing is applied to all operations in it. For this test we selected the ‘component’ option and used the ‘Standard’ mode.
Now we have several options to configurate the resequencer.

• Group – xpath expression to the field in the payload which the resequencer will use to group our incoming messages
• ID – xpath expression to the field which will uniquely identify our message
• Start – Start value of the ID in the incoming message
• Increment – Value which will be used for the increment of the id field in the upcoming messages
• Timeout – Time to wait before a following expected message arrives at the Mediator component

And that’s it what is needed for the configuration of the ‘Standard’ resequencer.

 

Test

To test this scenario i will use the following 3 messages.

1	<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

2	<soap:Body xmlns:ns1="http://xmlns.oracle.com/Application1_jws/MyReSequence/ProcessEmployees">

3	<ns1:process>

4	<ns1:empID>1</ns1:empID>

5	<ns1:empType>IT</ns1:empType>

6	<ns1:empName>Eric</ns1:empName>

7	</ns1:process>

8	</soap:Body>

9	</soap:Envelope>

1	<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

2	<soap:Body xmlns:ns1="http://xmlns.oracle.com/Application1_jws/MyReSequence/ProcessEmployees">

3	<ns1:process>

4	<ns1:empID>2</ns1:empID>

5	<ns1:empType>IT</ns1:empType>

6	<ns1:empName>John</ns1:empName>

7	</ns1:process>

8	</soap:Body>

9	</soap:Envelope>

1	<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

2	<soap:Body xmlns:ns1="http://xmlns.oracle.com/Application1_jws/MyReSequence/ProcessEmployees">

3	<ns1:process>

4	<ns1:empID>3</ns1:empID>

5	<ns1:empType>IT</ns1:empType>

6	<ns1:empName>Theo</ns1:empName>

7	</ns1:process>

8	</soap:Body>

9	</soap:Envelope>

Go to the console > soa_domain > SOA > soa-infra > > and Test it.
If we trigger the process 3 times with the payloads as we describes and in the same sequence, the instances will all complete and write the files to filesystem in the same sequence.

We used the ‘Standard’ mode and selected empID for sequence-value and emptType for group-value, and the sequence should start with 1 and will increment by 1.
Now switch the last 2 messages in the sequence and see what happens. Since we’re trying to process and already processed message again we will get the next errormessage

1	The selected operation execute could not be invoked.

2	An exception occured while invoking the webservice operation. Please see logs for more details.

3

oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: oracle.tip.mediator.infra.exception.MediatorException: ORAMED-03003:[Storing Resequencer Group Failed]Unable to store Resequencer Group." oracle.tip.mediator.common.persistence.MediatorResequencerMessage, mediator InstanceId=E07531315F8511DFBFBF3B164F19FDA3, componentDn=default/MyReSequence!1.0/Mediator1, operation=execute, groupId=IT, sequenceId=1, status=0"Possible Fix:Unable to store Resequencer Group. Check your Database connection or check data

So change all empType to ‘HR’ instead of ‘IT’.
For example

1	<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

2	<soap:Body xmlns:ns1="http://xmlns.oracle.com/Application1_jws/MyReSequence/ProcessEmployees">

3	<ns1:process>

4	<ns1:empID>1</ns1:empID>

5	<ns1:empType>HR</ns1:empType>

6	<ns1:empName>Eric</ns1:empName>

7	</ns1:process>

8	</soap:Body>

9	</soap:Envelope>

The sequence we’re now going to use is empID=1, empID=3, empID=2
After sending the second message (empID=3), you will notice the instance won’t complete. Because the resequencer expects an empID=2. In this case it will wait till this message arrives.

1	<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

2	<soap:Body xmlns:ns1="http://xmlns.oracle.com/Application1_jws/MyReSequence/ProcessEmployees">

3	<ns1:process>

4	<ns1:empID>2</ns1:empID>

5	<ns1:empType>HR</ns1:empType>

6	<ns1:empName>Eric</ns1:empName>

7	</ns1:process>

8	</soap:Body>

9	</soap:Envelope>

Now use the last test message (empID=2) and see what happens.

Instance 30030 changes from Running to Completed. This is because it received the next message in the sequence (empID=2), and after that the instance 30030 (empID=3) could continue.
If we check the files on filesystem we also see (compair the datetime of the files) that the files are stored in the correct sequence.

 

Other Resequencers

Besides the ‘Standard’ resequencer wel also have the ‘FIFO’- and the ‘BestEffort’ resequencer.
See this document to decide what resequencer suits best for your case.

No comments:

Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest

Labels:SOA

Oracle SOA Suite 11g and the new Partitions feature

In the old school Oracle SOA Suite we had the functionality to create different domains in the BPEL Console to group our applications.
This functionality was gone in the 11g SOA Suite, and because it still was a wanted feature, Oracle reintroduced it as feature in the new Oracle SOA 11g Patchset2.
Now it’s called ‘Partitions’.
So let’s see how to manage them.
Go to the Enterprise Manager (http://localhost:7001/em), Farm_ > SOA > soa-infra (soa_server1).
Right mouseclick on soa-infra > Manage Partitions. Create the new partition. (SOA Partition 별, Composite count 알 수 있음)


The new partition should be added to the list (beneath the default partition).
JDeveloper
In JDeveloper we will create a simple SOA Composit application.
Deploy the new application and now in the wizard of the deployment when we select a server it gives us a new selectbox to select the newly created partition. By default it will use the ‘default’ partition.

Deploy the application and let’s go back to the console.
Now we will see the new deployed application in the list of the ‘test_partition’ partition.

 

Using ant

ant-sca-mgmt.xml createPartition – Creates a partition in the SOA Infrastructure.
Location of the file :

1	<ORACL_MIDDLEWARE_HOME>/bin

ant -f ant-sca-mgmt.xml createPartition -Dhost=localhost -Dport=8001 -Duser=weblogic -Dpassword=weblogic -Dpartition=my_ant_partition

01	Buildfile: ant-sca-mgmt.xml

02	[echo] oracle.home = E:\oraclehome\11g\middleware\Oracle_SOA1\bin/..

03

04	createPartition:

05	[input] skipping input as property host has already been set.

06	[input] skipping input as property port has already been set.

07	[input] skipping input as property user has already been set.

08	[secure-input] skipping secure-input as property password has already been set.

09	[input] skipping input as property partition has already been set.

10	[echo] oracle.home = E:\oraclehome\11g\middleware\Oracle_SOA1\bin/..

11

12	folderMgrTask:

13	[java] calling FolderManager.initConnection(), m_host=localhost, m_port=8001, m_user=weblogic

14	[java] Connecting to: service:jmx:t3://localhost:8001/jndi/weblogic.management.mbeanservers.runtime

15	[java] connection initiated

16	[java] folderMBean=oracle.soa.config:name=soa-infra,j2eeType=FolderLifecycleConfig,Application=soa-infra

17	[java] Partition (my_ant_partition) is successfully created.

18

19	BUILD SUCCESSFUL

And the partitions list in the console

No comments:

Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest

Labels:SOA

Weblogic

  1. Managed Servers are on Admin state instead of Running state

During start up managed servers from admin console result in Admin State instead of Running State (see the screenshot below). This issue comes up usually when Weblogic is unable to connect to infrastructure database. Usually this is happening when the infrastructure database's listener is not down after reboot or server configuration change. In Windows make sure oracle services are up and the database EM console is accessible

No comments:

Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest

Labels:Weblogic

※ 참고사이트 : http://anatech-oracle.blogspot.kr/

Oracle SOA 11g - Configure transaction timeout for BPEL.

1. Setting the SyncMaxWaitTime :

2. Setting the global transaction timeout at Weblogic Domain Level:

3. Overriding the transaction timeout setting for BPEL EJB's

   1) Log into Oracle Weblogic Administration Console

   2) Click Deployments

   3) Expand soa-infra -> EJBs

   4) Click on the configuration tab for the timeout setting for each of EJB;s listed below and the change the time out values as required

   5) Click Save

   6) Restart Oracle Weblogic Server

※ 참고사이트 :  http://www.albinsblog.com/2011/11/oracle-soa-11g-configure-transaction_20.html

 1. SOA WSDL Caching

 2. MDS Cache

From a first glimpse myself I have the following impressions:

• The book gives a very good overview of the various topics of Performance Tuning
• A lot of recommendations are very valuable and show that the authors have real project experience
• My feeling is though that it concentrates a little bit too much on the low level infrastructure (like JVM tuning) and its config settings instead of explaining the why and what to tweak. Example: reducing audit level may help – but can also impact monitoring capabilities during production.
• Even though it touches database tuning, the book underestimates the need of database performance monitoring, database tuning, of regular purging and of tuning to prevent data growth. This often is a major area which leads to performance problems if not addressed in an early stage. For example no word about using Secure File LOBs for reducing HW contention in the DB….
• Architectural decisions are not mentioned– like splitting up one SOA domain into multiple ones for various reasons.
• SOA monitoring chapter promotes and focuses Hyperic as a product and misses out Oracle Grid Control and other available solutions.
• Design-level tuning covers only BPEL. Often one key area of performance tuning is to choose the right SOA component for a requirement. For example to use OSB
• A few components are not covered, for example Mediator resequencer, OHS tuning, XREFs and DVMs.

For some recommendations however, you should be careful to follow them without validation. Just one example:

“The adapter.jms.receive.threads, adapter.aq.dequeue.threads, and InboundThreadCount properties set the number of threads available for processing JMS,
AQ, and MQ messages. The default value for these is 5, and performance can be improved by using more threads to dequeue messages from these providers.”

First, the default for “adapter.jms.receive.threads” is 1. Secondly, as an experience from real world complex deployments in large clusters, the right number of consumers should be determined by the expected load and for example the message size (potentially triggering different transaction times). Last but not least, in a cluster, each JMS consumer thread is multiplied by the number of cluster nodes. Therefore you should be very careful to increase JMS Adapter receive threads. I have seen performance tests where we proved that throughput increased dramatically by decreasing the number of JMS receive threads…

As a summary, the book provides some good add on’s to the standard documentation available in the Oracle Fusion Middleware Performance and Tuning Guide.
Get a copy, check them out and tune your SOA 11g environment!

참고사이트 : http://stefankoser.blogspot.kr/2013/09/new-book-about-soa-11g-performance.html

참고사이트 : https://www.packtpub.com/books/content/performance-tuning-%E2%80%93-systems-running-bpel-processes

Part 1 - Principles of Performance Tuning

Part 2 - Diagnosing and tuning performance problems in the java Virtual Machine

Part 3 - Tuning and Scaling WebLogic

Part 4 - Oracle Service Bus Performance

Part 5 - Oracle BPEL Performance Best Practices

Part 6 - Monitoring SOA Suite with Oracle Enterprise Manager

Up to release 11.1.1.5 there have been 4 thread pools in Oracle SOA Suite 11g to control parallelism of execution:

1. Invoke Thread Pool ( for asynchronous invocations)

2. Engine Thread Pool ( for callback execution)

3. System Thread Pool

4. Audit Thread Pool