BPEL instance recreation for corelation set.

Hi,
In our project we have deployed two composites in the first one we have used a fileadapter,mediator,webservice the flow is like from Fileadapter-->mediator-->webservice(1^st^ Composite) .
In the second composite bpel interface is web service and wrting to an outbound location using a file adapter. The flow is like webservice-->BPEL-->Fileadapter(2^nd^ Composite).
To achieve message aggregation,In the BPEL we have used co-relation set on ID.When we put file in inbound location having same unique ID it will be processed within the same BPEL instance and files having different ID will have different bpel instance.
So it's working as expected after deployment only once.The message are aggregated.But when we are putting some new files in the inbound location having same ID(i:e new instance to be created)there is no files are aggregated at outbound location.In console we can see the flow from fileadapter-mediator-webservice invocation but it's invoking the bpel component..
I am using BPEL instance corelation set to aggregate multiple message segment from same caller for 5 mins.It works fine no issues.
For the same corelation ser if I repeat the same requests after 10 mins it won't instantiate BPEL also does not give any error .
To make it work we have to redeploy the 2^nd^ composite everytime.
So can anybody please help us out on this how to resolve this issue.
Thanks In Advance!:)

Hi,
try the BPEL forum
BPEL
Frank

Similar Messages

BPEL instance recreation for used correlation set.

Hi,
In our project we have deployed two composites in the first one we have used a fileadapter,mediator,webservice the flow is like from Fileadapter-->mediator-->webservice(1^st^ Composite) .
In the second composite bpel interface is web service and wrting to an outbound location using a file adapter. The flow is like webservice-->BPEL-->Fileadapter(2^nd^ Composite).
To achieve message aggregation,In the BPEL we have used co-relation set on ID.When we put file in inbound location having same unique ID it will be processed within the same BPEL instance and files having different ID will have different bpel instance.
So it's working as expected after deployment only once.The message are aggregated.But when we are putting some new files in the inbound location having same ID(i:e new instance to be created)there is no files are aggregated at outbound location.In console we can see the flow from fileadapter-mediator-webservice invocation but it's invoking the bpel component..
I am using BPEL instance corelation set to aggregate multiple message segment from same caller for 5 mins.It works fine no issues.
For the same corelation ser if I repeat the same requests after 10 mins it won't instantiate BPEL also does not give any error .
To make it work we have to redeploy the 2^nd^ composite everytime.
So can anybody please help us out on this how to resolve this issue.
Thanks In Advance!:)

Hi,
Even I am getting the same exception. Even tough my Process doesn't contain any conflicting Receive there is a pick activity that receives the Incoming call with two different messages. And logically it should not generate a conflicting receive.
Did anyone get the root cause of this problem. If someone can update this . It will be really helpful. I am trying to create the PL for the particular branch instead of the global PL as suggested in one of he blogs. I will also update if i get any new clues.
Thanks in advance.
Yogesh

BPEL instance number in the XSL

How can I reference the current BPEL instance number in an XSL?
I figure it would handy to have the unique BPEL instance number for trouble shooting if there is a problem with the interface.

hi
I am facing problems using getInstanceID inside XSLT
the expression not only returns null, but also produces problem in transforming remaining nodes.
I need to use this inside XSL map since i have multiple inputs ( using for-each in transform) and for each of these, i need instance id to be assigned
Is there any way?

Python script to automate the manual recovery of BPEL instances in SOA 11g

I have a requirement for automating the manual recovery of BPEL instances pending for recovery at a particular time. It will be called inside a cron job.
Any help will be much appreciated.
Thanks in advance,
Ravi Prakash

Hi,
When I try to recover the instance that is waiting for manual recovery, I didn't see anything happening.
Also the the fault policy is active and working fine during the retry intervals. That means If I disable one of the webservices and enable them during the retry it is success after some failure retries.
Any ides why the recovery not working in SOA 10.1.3.3
--Khaleel

Sequential Instantiation of BPEL instances for a BPEL process

Hi,
We are using Oracle SOA 10.1.3.4 & AIA2.5. We have a situation where the instances of a particular bpel process have to be executed in sequence. Also, the new instance should NOT be instantiated unless the previous instance is completed.
For example.. Lets say a SyncBPELReqABCS is invoking SyncBPELProvABCS via ESB. SyncBPELReqABCS is looping and spawning multiple instances of SyncBPELProvABCS in a certain sequential order in Asynchronous Fire-and-Forget model. Lets say bpel-instance#1, bpel-instance#2 and bpel-instance#3 are instances of SyncBPELProvABCS process. Even though SyncBPELReqABCS invokes (spawns) SyncBPELProvABCS in a fire and forget model, the bpel-instance#2 should not begin unless bpel-instance#1 is completed and bpel-instance#3 shuld not begin unless bpel-instance#2 is completed. This is because there is a dependancy between instacnes of SyncBPELProvABCS process.
Can this be achieved in Oracle SOA?? Can we restrict the instacnes of SyncBPELProvABCS to be created in this manner?
This is similar to "incompatability" of concurrent programs in ORACLE EBusiness Suite where one concurrent program waits till another concurrent program completes.
Please let me know if I am not clear. Appreciate an immediate help!
Thanks,

Hello,
Now that I look back at this tread, I can see that the questions I was asking and those of the original poster were somewhat different.
But they both fall under the heading of "Sequential Instantiation of BPEL instances for a BPEL process", and so I thought I would post some findings we've come across regarding that topic here.
There were a couple steps that helped us achieve the behavior we were looking for, and the were...
1) Change the BPEL oneWayDeliveryPolicy from "async.persist" to "sync"
This can be done in a couple locations. The first is within the EM application that comes bundled with SOA 11g, and the place to go is:EM > [farm name] > SOA > soa-infra (right click) > SOA Administration > BPEL Properties > More BPEL Configuration Properties > OneWayDeliveryPolicyOnce that value has been changed to "sync" (without the quotes), you'll need to stop and start the managed servers that run your SOA instance(s).
As you might expect, making a change at the "server level" like this impacts the default behavior of all composites deployed within your SOA instance. The second place to make this change - within the deployment descriptors for your BPEL process - impacts only the BPEL process that is being modified. To make the change at this level, you would edit your project's composite.xml file and, for each BPEL component, specify: <component name="BPELProcess1" version="2.0">
 <implementation.bpel src="BPELProcess1.bpel"/>
 <property name="bpel.config.oneWayDeliveryPolicy">sync</property>
 <property name="bpel.config.transaction">required</property>
</component>What does this change do? Well, I don't claim to have a complete understanding, but in theory it prevents a thread handoff from taking place between the service that is initiates your BPEL process (like a receive) and the actual BPEL engine thread that processes the request.
In our case, where calls between (and within) composites were all of the synchronous "fire and forget" variety, this change also caused the entire processing of a message (across three different composites) to happen in a single thread (each message handoff was one-way, and with the oneWayDeliveryPolicy set to "sync", each was handled in a synchronous manner).
This also seemed to have the effect of serializing our message processing. For example, in a test case where a BPEL process reads from a JMS queue and 250 messages are enqueued, with the oneWayDeliveryPolicy set to "async.persist", I'd typically go in to EM and, on each refresh, find 5-8 instances of the composite that processes those messages to be in a "Running" state. Once the change to "sync" was made, I'd only see at most only 2 (where one had actually already finished; the audit system just hadn't yet caught up to that fact yet).
This also means that, with a "sync" delivery policy, messages (at least in our environment) are processed more slowly, but that was ok with us as we were more concerned with the behavior than the speed.
For details on this and other BPEL deployment descriptor properties, see:
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10224/bp_app_deploydesc.htm
Also, it's important to note that making the above change will alter the boundaries of your transactions as well as how faults are propagated. For more details, see:
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10224/soa_transactions.htm
2) Front BPEL process with a Mediator object and enable message resequencing
While we're using the above change as a standard practice in our environment, this second change has only been nominally tested - but it could be of interest and so I'll mention it here.
Once you've updated your composite to include a mediator object in front of your BPEL process (if there isn't one there already), edit the .mplan for your mediator and change the "Resequence Level" from the default value of "operations" to "component". Then change the "Resequence Mode" from "off" to "FIFO" and specify an X-Path expression by which the mediator will be able to group your messages. This will help ensure that the messages are being processed in the order you expect.
More information about resequencing within the mediator component can be found:
http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10224/med_resequencer.htm
Hopefully the above information is useful - if not for the original poster, then for someone who comes along later with similar questions.
- Nathan

Indexing for BPEL instances in 11g

Can any one give some suggestion on how to do indexing for bpel instances in 11g.
I am trying like below
oracle.xml.parser.v2.XMLElement studentRollNo= (oracle.xml.parser.v2.XMLElement)getVariableData("inputVariable", "payload", "/ns1:StudentList/ns1:Student/ns1:StudentRollNo");
setIndex(3, studentRollNo.getFirstChild().getNodeValue());
But i am unable to get index search for student roll no except instance id.
Edited by: 957463 on Sep 6, 2012 9:02 AM

yes, on em console there is no option to search based on index value. We can only search composite instance.
check if this helps you: http://soasphere.blogspot.in/2011/04/how-to-serch-composites-for-index.html

Java.lang.OutOfMemoryError -- Is there a way to limit BPEL instances number

Hi All,
My BPEL process is using JMS adapter to read the JMS queue. Whenever a new message arrives, a new BPEL instance is created. However, when the message gets bigger and multiple messages arrive at queue at the same time, the OC4J gets java OutOfMemory (heap space) error and was forced shutdown. I'm wondering if there's any way to limit the BPEL instance created, say, only one at a time, and the messages would be processed in sequence. Would this be a good way to not use so much heap at one time? Is there a way to limit the BPEL instance created?
Thanks for your help!
Michelle

Take a look at how to configure Jms polling interval (talks about a property that you can set to introduce a delay in between dequeues). That might be of some help to start with.
It is supposed to work exactly the way you want it i.e the activation agent does a dequeue and hand off to bpel engine (which creates an instance and uses the same thread to run as much of that instance as possible i.e till the first dehydration point). So, if your process has a dehydration point right at the beginning (which could be due to invocation of another async process, or wait or ...), you could very well see this thread go right back and process the next available message.
I believe this is a generic problem that is not necessarily jms adapter specific. One way would be to split up your process into three processes:
1. "Kickoff" process which contains just a "receive" associated with the activation agent followed by an invocation of a "Controller" process
2. "Controller" process which checks for the provided input as to which process it needs to invoke, and then goes on to check how many instances of that process are currently running; if this number is below a certain threshold, kick off the main process providing it the necessary payload gotten from the "KickOff" process
3. "Main" process which is same as your current process except that it is a typical async process without the adapter "receive" partner link
So, the idea being that for any process where you want to introduce a control-flow mechanism, you would split it into #1 and #3 above. Have one generic Controller process, which caters to all of the processes.
Would be interested in learning if others have solved this in a generic way.

BPEL PM looking for correlation id

Hi.
I have BPEL process with 2 receive activities and correlation set. In first initialize I set correlation id.
For example: process is Ordering and correlaion id is Order number. Admin sometimes have to look at instance of order.
Is there posibility in BPEL PM or Console find instance with given correlation id.

Great tip,
more you can read here
http://orasoa.blogspot.com/2007/01/overule-bpel-instance-name.html
http://blogs.oracle.com/rammenon/2007/05/22#a11
but coleague swear that there is some possibility to see correlation id in BPEL console
May be ESB console trackable values can be used this way but I don't know how.

No BPEL instances viewable after upgrading to 10.1.3.4

I upgraded my local copy of the SOA suite to patch 10.1.3.4 and since I have done so, I have come across a number of problems.
When I have run through a BPEL instance it does not appear in the instances tab of the bpel console.
I also cannot see bpel process fom Jdev that are deployed in my local soa suite. When I create a partner link and navigate to the BPEL_Services and drill down I expect to see the deployed processes but I get an error saying Exception: No services found!.
Any ideas anyone.

Hi,
I installed Oracle SOA 10.1.3.1.0 and Oracle 10g Express Edition Database.
I am trying to upgrade Oracle SOA 10.1.3.1.0 to Oracle SOA 10.1.3.4.0
In upgrade Preinstallation Requirements, Oracle is asking to run following sql scripts.
4.2.1 Run Upgrade Scripts on Oracle Application Server 10g Release 3 (10.1.3.1.0)
Before applying 10g Release 3 (10.1.3) Patch Set 4 (10.1.3.4.0) to a Oracle Application Server 10g Release 3 (10.1.3.1.0) instance, do the following procedure:
Connect to the Oracle database as the orabpel user.
Run the following script based on your database and operating system for your BPEL environment:
For Linux x86: upgrade_10131_10134_oracle.sql
The preceding script is located in the SHIPHOME/Disk1/install/soa_schema_upgrade/bpel/scripts directory.
For Microsoft Windows (32-Bit) with Oracle Database: upgrade_10131_10134_oracle.sql
The preceding script is located in the preceding script is located in the SHIPHOME\Disk1\install\soa_schema_upgrade\bpel\scripts directory.
For Microsoft Windows (32-Bit) with Oracle Database Lite: upgrade_10131_10134_olite.sql
The preceding script is located in the preceding script is located in the SHIPHOME\Disk1\install\soa_schema_upgrade\bpel\scripts directory.
Connect to the Oracle database as the oraesb user.
Run the following script based on your database and operating system for your ESB environment.
For Linux x86: upgrade_10133_10134_oracle.sql
The preceding script is located in the SHIPHOME/Disk1/install/soa_schema_upgrade/esb/sql/oracle directory.
For Microsoft Windows (32-Bit) with Oracle Database: upgrade_10133_10134_oracle.sql
The preceding script is located in the SHIPHOME\Disk1\install\soa_schema_upgrade\esb\sql\oracle directory.
For Microsoft Windows (32-Bit) with Oracle Database Lite: upgrade_10133_10134_olite.sql
The preceding script is located in the SHIPHOME\Disk1\install\soa_schema_upgrade\esb\sql\other directory.
MY QUESTIONS IS I didn't create users orabpel and oraesb in database.
IF ORACLE DATABASE HAS ALREADY HAS ORABPEL AND ORAESB USERS, I don't know password.
If you know passwords, will you please inform me.
May I know how you handled above sql while applying patch.
Regards,
Shanti Nagulapalli.

Problems in Dialog instance installation for ECC6.0(ABAP+JAVA)

Does anyone can help me what should be a procedure of installing Dialog instance for ECC 6.0 with both ABAP + Java Stacks.
When installing app server do we also choose ABAP and Java or just ABAP. Installation manual does not cover this and when we run the sapinst we have following problem:
The following are the activities that I have done as pre-reqs on the standby on the server that is to host dialog instance
I have mounted the following file systems on ddrsap02. Created the local filesystem /usr/sap/DSP/D00 and NFS mounted the others
/dev/appsaph 5505024 5503856 1% 5 1% /usr/sap/DSP/D00 (is this required or SAPINST should create it itself)
ddrsap00:/stage 419430400 149761708 65% 90835 1% /stage
dprsap01:/sapmnt/DSP 4718592 2888416 39% 12790 2% /sapmnt/DSP
ddrsap12:/usr/sap/trans 2752512 1084932 61% 5107 3% /usr/sap/trans
Then when I run the sapinst from ddrsap02 to install the DI I get the following error
ddrsap02[/tmp/sapinst_instdir/ERP/SYSTEM/ORA/HA/ABAPJAVA/DI]#vi sapinst_dev.log
"sapinst_dev.log" 20516 lines, 641048 characters
TRACE
Running with toplevel file /tmp/sapinst_instdir/ERP/SYSTEM/ORA/HA/ABAPJAVA/DI/toplevel.xml
Running with dialog file /tmp/sapinst_instdir/ERP/SYSTEM/ORA/HA/ABAPJAVA/DI/dialog.xml
Running with keydb file /tmp/sapinst_instdir/ERP/SYSTEM/ORA/HA/ABAPJAVA/DI/keydb.xml
INFO 2007-01-31 09:38:52
Working directory changed to /tmp/sapinst_exe.397528.1170221882.
Opened iaejs701.o
INFO 2007-01-31 09:38:52
Working directory changed to /tmp/sapinst_instdir/ERP/SYSTEM/ORA/HA/ABAPJAVA/DI.
INFO 2007-01-31 09:38:52
Working directory changed to /tmp/sapinst_exe.397528.1170221882.
Opened iacdlib701.o
INFO 2007-01-31 09:38:52
Working directory changed to /tmp/sapinst_instdir/ERP/SYSTEM/ORA/HA/ABAPJAVA/DI.
INFO 2007-01-31 09:38:52
Working directory changed to /tmp/sapinst_exe.397528.1170221882.
Opened iaccdlib.o
INFO 2007-01-31 09:38:52
Working directory changed to /tmp/sapinst_instdir/ERP/SYSTEM/ORA/HA/ABAPJAVA/DI.
INFO 2007-01-31 09:38:52
Working directory changed to /tmp/sapinst_exe.397528.1170221882.
Opened iapasswdman701.o
INFO 2007-01-31 09:38:52
Working directory changed to /tmp/sapinst_instdir/ERP/SYSTEM/ORA/HA/ABAPJAVA/DI.
This is SAPinst, version 701, make variant 700_REL, build 817256
compiled on Mar 14 2006, 23:39:26
TRACE [syxxsyshlp.cpp:175]
 syslib::logSystemState()
Process environment
===================
Environment Variables
=====================
_ = /tmp/sapinst_exe.397528.1170221882/sapinstexe
SAPINST_EXE_DIR = /tmp/sapinst_exe.397528.1170221882
LANG = en_US
LOGIN = root
PATH = /usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/java14_64/jre/bin:/usr/java14_64/bin
SAPINST_EXEDIR_CD = /stage/51031797/IM_AIX_PPC64/.
LC__FASTMSG = true
WINDOWID = 8388621
"sapinst_dev.log" 20516 lines, 641048 characters
 EJS_Installer::writeTraceToLogBook()
2007-01-31 09:42:48.898 NWDB.getDBHost() done: undefined
ERROR 2007-01-31 09:42:48 [iaxxinscbk.cpp:271]
 abortInstallation
CJS-00030 Assertion failed: in getSidFromProfiles: Variable dbHost should be defined
TRACE [iaxxejsbas.hpp:388]
 handleException<ESAPinstException>()
Converting exception into JS Exception Exception.
ERROR 2007-01-31 09:42:48
 CJSlibModule::writeError_impl()
MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
TRACE [iaxxejsbas.hpp:460]
 EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.
ERROR 2007-01-31 09:42:48
FCO-00011 The step assertDBInfo with step key |NW_DI|ind|ind|ind|ind|0|0|NW_GetSidFromProfiles|ind|ind|ind|ind|1|0|assertDBInfo was executed with status ERROR .
<html><head></head><body>An error occurred while processing service SAP ERP 2005 Support Release 1 > SAP Systems > Oracle > High-Availability System > Base
d on AS ABAP and AS Java > Dialog Instance. You may now<ul> <li>press Retry to repeat the current step.</li> <li>press the View Log button
to get more information about the error.</li> <li>stop the task and continue with it later.</li></ul>Log files are written to /tmp/sapinst_instdir/ERP/SYST
EM/ORA/HA/ABAPJAVA/DI.</body></html>
TRACE [iaxxgenimp.cpp:1093]
 showDialog()
waiting for an answer from gui
Am I missing some pre-reqs or variable definitions?
I was going through the documentation and it says that /sapmnt/DSP/exe should be a local filesystem for a DI on a separate server. Will this create a problem ?
Also they talk about starting sapinst with the variable SAPINST_USE_HOSTNAME set to ddrsap02. I have tried this also
We are also not 100% sure about the settings for parameters:
rdisp/mssserv
rdisp/mssserv_internal
Accorss Devault Instance and Services Instance profile.
When we define it as per installation GUIDE (Abap+Java page 64) we get the popup message in SAPINST:
<html>Profile parameter rdisp/msserv_internal is not set for instance DVEBMGS01/DSP on host dprsap01.You have to set the parameter in the default profile and restart the instance.For further information refer to SAP Note 821875.</html>
Other errors follow shortly.
Any help would be appreciated

Hi ,
are you able to resolve this error :Profile parameter rdisp/msserv_internal is not set for instance DVEBMGS01/DSP on host dprsap01.
You have to set the parameter in the default profile and restart the instance.
For further information refer to SAP Note 821875.</html>
? if yes , pls let me know , I am stuck with same issue while installing dialog instance .
Thanks
Hamendra

How to install Oracle BPEL Process Manager for OracleAS Middle Tier

hi,
i need to install BPEL process manager, so i download the following file from otn
1.soa_windows_x86_101310_disk1
2.soa_windows_x86_bpel_101310
here i read the document named b28980.pdf from bpel\doc\pc.1012 to install BPEL PM
so i start to complete the pre-installation task
1.installed Oracle database 10g
2.Run the Integration Repository Creation Assistant on the Database
3.Install Oracle Application Server 10g Release3 (10.1.3.1.0) and select either the J2EE Server installation type or the J2EE and Web Server installation type. selected J2EE and Web Server installation type
and installed according to the Oracle application server installation guide.
installed OracleAS in the path : D:\product\10.1.3.1\OracleAS_1
4.Install the current release of Oracle BPEL Process Manager for OracleAS Middle Tier
here they mention to select the J2EE and Web Server installation type because that type is selected in Oracle AS installed in Oracle Application Server
so i start to install the BPEL PM by selecting the setup.exe-->and shows the location source and destination
default destination is : D:\product\10.1.3.1\OraBPEL_1 selected next on the screen
the next screen is select installation type here there are two types named
1.BPEL process Manager for Developer (371MB)
2.BPEL process manager for Oracle AS Middle tier (107MB)
i selected 2.BPEL process manager for Oracle AS Middle tier (107MB) and click next
pop up window opens with title dependencies
error:
BPEL Process manager for oracle AS Middle tier will run on top of a supported Oracle Application Server 10.1.3.1.0 J2EE server and Web Server Or J2EE server instance. this location does not contain this instance. Please select new Oracle home that contains a supported instance.
so i changed the destination path to : D:\product\10.1.3.1\OracleAS_1\BIN then also i got the same error.
please any one mention the path for J2EE and Web Server instance for installing the BPEL PM for Oracle AS Middle Tier.
Thanks in Advance
Aswath Thaniga

If you choose the developer version you will be fine.
If you have installed J2EE and Web Server installation into D:\product\10.1.3.1\OracleAS_1 then this is the location you install your BPEL PM into, not D:\product\10.1.3.1\OraBPEL_1 or D:\product\10.1.3.1\OracleAS_1\BIN.
D:\product\10.1.3.1\OracleAS_1 is what we call the ORACLE_HOME, generally we create a new home for each install, but in this case there is a dependency on 10.1.3.1 OC4J container. So it needs to be installed into 10.1.3.1 oracle home.
The bin directory is just the executables for that home, its not the actual. home.
cheers
James

No CENTRAL nor DIALOG instance known for system SID

Hi,
We are in the process of setting up our Solution Manager 7.1. Currently we are in the step 'Managed System Configuration'.
We are stuck on the step 7 - "Create Users". There are 4 users to be created which are already there in the systems(Created Manually).
The users are
SAPSUPPORT and SMDAGENT_XXX for ABAP and Java both.
In the ABAP view it gives the error as "No CENTRAL nor DIALOG instance known for system SID".
In the Java view it gives the error as "User Status Cannot be checked".
We are on the below Support Pack status:
SAP_ABA 702 0008 SAPKA70208
SAP_BASIS 702 0008 SAPKB70208
PI_BASIS 702 0008 SAPK-70208INPIBASIS
ST-PI 2008_1_700 0004 SAPKITLRD4
SAP_BS_FND 702 0006 SAPK-70206INSAPBSFND
SAP_BW 702 0008 SAPKW70208
SAP_AP 700 0024 SAPKNA7024
WEBCUIF 701 0005 SAPK-70105INWEBCUIF
BBPCRM 701 0005 SAPKU70105
BI_CONT 706 0003 SAPK-70603INBICONT
CPRXRPM 500_702 0006 SAPK-50006INCPRXRPM
ST 710 0003 SAPKITL703
ST-BCO 710 0001 SAPK-71001INSTBCO
SOCO 101 0000 -
ST-A/PI 01N_700SOL 0000 -
ST-ICO 150_700 0030 SAPK-1507UINSTPL
ST-SER 701_2010_1 0008 SAPKITLOS8
Please suggest a solution to this.
Thanks & Regards,
Ajitabh

Hello Ajitabh,
I'm sure that you will see this error if you expand the error entry:
SPML service failed to process searchRequest
1. If you followed the advices from note 1616058, disabling SPML:
When the SPML is desactivated, the status of users can't be checked.
We are working to provide a note to solve this issue. Note number is 1647267, it is not release yet, but the solution is:
"Enable to flag the user creation to 'manually performed' in solman_setup".
2. If you didn't disable SPML:
Please refer to the steps in this SAP Note : 1647157 which will help you address the issue.
Please let us know the outcome, thanks.
Best regards,
Guilherme

Looking to use BPEL Instance and counter inside of a transformation

I'm trying to find a way to include the BPEL instance and a counter within a BPEL transformation to create a unique key.
Example, picking up files with multiple lines and no unique keys, each file is processed as a unique BPEL instance (key 1), and would like to use the row number (of the file, but not specified in the file) as the second key.
My process takes a file from a file adapter and loads it into a database adapter if that helps.
Any ideas would be appreciated.

We ended up finding a Node-set Function -> Position to return the position inside of the dataset.

Bpel deployment fails for all processes that have revision other than 1.0.

Using: Release *10.1.3.3.1*
Hello All,
Bpel deployment fails for all processes that have revision other than *1.0*.
We have been attempting to deploy several BPEL projects via ANT script to a target environment and are encountering failures to deploy for every project which isn’t a (revision 1.0). We are getting the following error whenever we try to deploy a process with a revision other than 1.0:
D:\TJ_AutoDeploy\BPEL_AutoDeploy_BETA\build.xml:65: BPEL archive doesnt exist in directory "{0}"
 at com.collaxa.cube.ant.taskdefs.DeployRemote.getJarFile(DeployRemote.java:254)
 at com.collaxa.cube.ant.taskdefs.DeployRemote.deployProcess(DeployRemote.java:409)
 at com.collaxa.cube.ant.taskdefs.DeployRemote.execute(DeployRemote.java:211)
 at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
 at org.apache.tools.ant.Task.perform(Task.java:364)
 at org.apache.tools.ant.Target.execute(Target.java:341)
 at org.apache.tools.ant.Target.performTasks(Target.java:369)
 at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
 at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
 at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
 at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
 at org.apache.tools.ant.Main.runBuild(Main.java:668)
 at org.apache.tools.ant.Main.startAnt(Main.java:187)
 at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
 at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
The structure of our automated deployment script is as follows:
First, a batch script calls (Jdeveloper_BPEL_Prompt.bat) in order to set all necessary environment variables i.e. ORACLE_HOME, BPEL_HOME, ANT_HOME, etc for ant.
Next, the script lists every .jar file within the directory to an .ini file called BPEL_List.ini. Furthermore, BPEL_DIR, ADMIN_USER and ADMIN_PSWD variables are set and initialized respectively to:
- “.” – point to directory where script is running from because all the BPEL processes are located here
- “oc4jadmin”
- “*********” (whatever the password for out environment is)
We’ve developed a method to have the script prompt the user to select the target environment to deploy to. Once the user selects the appropriate environment, the script goes through the BPEL_List.ini files and a loop tells it that for every BPEL process listed:
DO ant
-Dprocess.name=%%b
-Drev= !Rev!
-Dpath=%BPEL_DIR%
-Ddomain=default
-Dadmin.user=%ADMIN_USER%
-Dadmin.password=%ADMIN_PWD%
-Dhttp.hostname=%HOST%
-Dhttp.port=%PORT%
-Dverbose=true
(What’s happening is that the variables in the batch file are being passed on to the ANT script where *%%b* is the process name, !rev! is revision #, and so on…)
The loop goes through each line in the BPEL_List.ini and tokenizes the BPEL process into 3 parts *(%%a, %%b, and %%c)* but we only extract 2 parts: *%%b* (process name) and *%%c* which becomes !Rev! (revision number).
Example:
Sample BPEL process:
bpel_ThisIsProcess1_1.0.jar
bpel_ThisIsProcess2_SOAv2.19.0.001B.jar
After tokenizing:
%%a %%b %%c
bpel ThisIsProcess1 1.0.jar
bpel ThisIsProcess2 SOAv2.19.0.001B.jar
*!Rev!* and not *%%c* because *%%c* will return whatever the revision number is + the “.jar” file extension as illustrated above. So to circumvent this, we parse *%%c* so that the last 4 characters are stripped. Such is done like this:
set RevN=%%c
set RevN=!RevN:~0,-4!
Hence, the usage of !Rev!.
Below is a screenshot post of the ANT build.xml that goes with our script:


<project name="bpel.deploy" default="deployProcess" basedir=".">
 
 <property name="process.dir" value="${basedir}" />
 
 
 <property environment="env"/>
 
 <condition property="bpel.home" value="${env.BPEL_HOME}">
 <available file="${env.BPEL_HOME}/utilities/ant-orabpel.xml" />
 </condition>
 
 
 
 
 <property name="oracle.home" value="${env.ORACLE_HOME}" />
 <property name="bpel.home" value="${oracle.home}/bpel" />
 
 <property file="${process.dir}/build.properties"/>
 
 <import file="${bpel.home}/utilities/ant-orabpel.xml" />
 
 <property file="${bpel.home}/utilities/ant-orabpel.properties" />
 
 <target name="deployProcess">
 <tstamp>
 <format property="timestamp" pattern="MM-dd-yyyy HH:mm:ss" />
 </tstamp>
 
 <record name="build_verbose.log" loglevel="verbose" append="true" />
 <record name="build_debug.log" loglevel="debug" append="true" />
 <echo></echo>
 <echo>####################################################################</echo>
 <echo>BPEL_AutoDeploy initiated @ ${timestamp}</echo>
 <echo>--------------------------------------------------------------------</echo>
 <echo>Deploying ${process.name} on ${http.hostname} port ${http.port} </echo>
 <echo>--------------------------------------------------------------------</echo>
 <deployProcess
 user="${admin.user}"
 password="${admin.password}"
 domain="${domain}"
 process="${process.name}"
 rev="${rev}"
 dir="${process.dir}/${path}"
 hostname="${http.hostname}"
 httpport="${http.port}"
 verbose="${verbose}" />
 <sleep seconds="30" />
 
 </target>
 
</project>
SUMMARY OF ISSUE AT HAND:
~ Every bpel process w/ 1.0 revision deploys with no problems
~ At first I would get an invalid character error most likely due to the “!” preceding “Rev”, but then I decided to set rev=”false” in the build.xml file. That didn’t work quite well. In another attempt, I decided to leave the –Drev= attribute within the batch script blank. That still led to 1.0s going through. My next thought was deploying something other than a 1.0, such as 1.2 or 2.0 and that’s when I realized that if it wasn’t a 1.0, it refused to go through.
QUESTIONS:
1. IS THERE A WAY TO HAVE ANT LOOK INTO THE BPEL PROCESS AND PULL THE REVISION ID?
2. WHAT ARE WE DOING WRONG? ARE WE MISSING ANYTHING?
3. DID WE GO TOO FAR? MEANING, IS THERE A MUCH EASIER WAY WE OVERLOOKED/FORGOT/OR DON’T KNOW ABOUT THAT EXISTS?
Edited by: 793292 on Jul 28, 2011 12:38 PM

Only thing i can think of is instead of using a MAC ACL , u cud jus use the default class
Policy Map Test
class class-default
police 56000 8000 exceed-action drop
Class Map match-any class-default (id 0)
Match any
You would be saving a MAC-ACL ;-).

How to Increase Instance size for ALBPM-Err:'Max instance size exceeded.

HI,
Can anybody in How to increase maximum instance size for
1. ALBPM Studio
2. runtime i.e. process administrator?
Look forward for help.
Cheers
The exception in detail is:
Error while persisting the transaction data: 'Max instance size exceeded.
Current size is 33262, whereas the maximum size is 16384. This occurs with instance 'Process1' at activity 'StartExecution[Process1DownloadMessage]' of process '/Process1Download#Default-1.0''
Details:
Max instance size exceeded.
Current size is 33262, whereas the maximum size is 16384. This occurs with instance 'Process1' at activity 'StartExecution[Process1DownloadMessage]' of process '/Process1Download#Default-1.0'
fuego.server.exception.MaxInstanceSizeRuntimeException: Max instance size exceeded.
Current size is 33262, whereas the maximum size is 16384. This occurs with instance 'Process1' at activity 'StartExecution[Process1DownloadMessage]' of process '/Process1Download#Default-1.0' at fuego.server.ProcInst.getComponentData(ProcInst.java:792) at fuego.server.ProcInst.mustStoreComponent(ProcInst.java:2777) at fuego.server.persistence.jdbc.JdbcProcessInstancePersMgr.executeUpdateInstance(JdbcProcessInstancePersMgr.java:2870) at fuego.server.persistence.jdbc.JdbcProcessInstancePersMgr.updateInstance(JdbcProcessInstancePersMgr.java:2272) at fuego.server.persistence.Persistence.updateProcessInstance(Persistence.java:1008) at fuego.server.execution.EngineExecutionContext.persistInstances(EngineExecutionContext.java:1819) at fuego.server.execution.EngineExecutionContext.persist(EngineExecutionContext.java:1109) at fuego.transaction.TransactionAction.beforeCompletion(TransactionAction.java:132) at fuego.connector.ConnectorTransaction.beforeCompletion(ConnectorTransaction.java:685) at fuego.connector.ConnectorTransaction.commit(ConnectorTransaction.java:368) at fuego.transaction.TransactionAction.commit(TransactionAction.java:302) at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:481) at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551) at fuego.transaction.TransactionAction.start(TransactionAction.java:212) at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123) at fuego.server.execution.DefaultEngineExecution.executeAutomaticWork(DefaultEngineExecution.java:63) at fuego.server.execution.EngineExecution.executeAutomaticWork(EngineExecution.java:42) at fuego.server.execution.ToDoItem.executeAutomaticWork(ToDoItem.java:264) at fuego.server.execution.ToDoItem.run(ToDoItem.java:559) at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:773) at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:753) at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:142) at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:134) at fuego.fengine.ToDoQueueThread$PrincipalWrapper.processBatch(ToDoQueueThread.java:446) at fuego.component.ExecutionThread.work(ExecutionThread.java:837) at fuego.component.ExecutionThread.run(ExecutionThread.java:408)

First take a look at your instance variables in your processes. Determine if some could be changed to be Separated instance variables. Once an instance variable's category changes from "Normal" to "Separated", it is not included in the instance size calculation.
If you cannot mark variables as Separated, then in Studio's "Project Navigator" tab, right mouse click the name of your project -> click "Engine Preferences" -> with the "Engine" selected as the Category, click the "Advanced" tab on the upper right change the "Maximum Instance Size" to 64KB (4x the original 15kb value) and change the "Instances Cache" to 1250 (1/4th the original value).
What version of Enterprise are you on (Standalone or WLS)? There is a similar setting on Enterprise, but it is slightly different between the two types of Enterprise Engines.
Dan

BPEL instance recreation for corelation set.

Similar Messages

Maybe you are looking for