Tagged ORACLE BPM

Oracle BPM 12.2.1 | BPM with DBadapter | Error deploying archive sca_XXXX.jar to partition “yyyyy” on server ZZZZZZ [http://server:port] HTTP error code returned [500]


Hi,

When deploying BPM artifact that utilizes DBAdapter created with Database Adapter Creator Wizard, take care about the JNDI name that the “Browse JNDI tree” magnifying glass tool retrieves, because the name must match case sensitive the name configured in the Deployments>DBAdapter>Configuration>Outgoing Connections Pool>”Connection Name”:

dbadapter

Otherwise you’ll get a deployment error:

[11:09:32 PM] ----  Deployment started.  ----
[11:09:32 PM] Target platform is  (Weblogic 12.x).
[11:09:32 PM] Running dependency analysis...
[11:09:32 PM] Building...
[11:09:42 PM] Deploying profile...
[11:09:42 PM] Wrote Archive Module to C:\WORK\jdeveloper\mywork\OrangeSamples\
DBadapter\deploy\sca_DBadapter.jar
[11:09:42 PM] Deploying sca_DBadapter.jar to partition "default" on server 
DefaultServer [http://JMUGUETA-ES.es.oracle.com:7101]
[11:09:42 PM] Processing sar=/C:/WORK/jdeveloper/mywork/OrangeSamples/DBadapter
/deploy/sca_DBadapter.jar
[11:09:42 PM] Adding sar file - C:\WORK\jdeveloper\mywork\OrangeSamples\DBadapter\
deploy\sca_DBadapter.jar
[11:09:42 PM] Preparing to send HTTP request for deployment
[11:09:42 PM] Creating HTTP connection to host:JMUGUETA-ES.es.oracle.com, port:7101
[11:09:42 PM] Sending internal deployment descriptor
[11:09:42 PM] Sending archive - sca_DBadapter.jar
[11:09:45 PM] Received HTTP response from the server, response code=500
[11:09:45 PM] JCA Deployment Validation failed for Adapters/dbReference_db.jca:
[11:09:45 PM] Problem 1: [ <connection-factory> <xml-fragment UIConnectionName=
"local" location="eis/db/TEST"/>]:
[11:09:45 PM] The JCA Binding Component is unable to locate the Resource Adapter 
specified in the <connection-factory/> element:  location='eis/db/TEST'
[11:09:45 PM] The reason for this is most likely that either
[11:09:45 PM] 1) the Resource Adapters RAR file has not been deployed successfully 
to the WebLogic J2EE Application server or
[11:09:45 PM] 2) the JNDI <jndi-name> setting in the WebLogic JCA deployment 
descriptor has not been set to eis/db/TEST. In the last case you might have to add 
a new 'connector-factory' entry (connection) to the deployment descriptor.
[11:09:45 PM] Please correct this and then restart the WebLogic Application Server
[11:09:45 PM] Error deploying archive sca_DBadapter.jar to partition "default" on 
server DefaultServer [http://JMUGUETA-ES.es.oracle.com:7101] 
[11:09:45 PM] HTTP error code returned [500]
[11:09:45 PM] Error message from server:
There was an error deploying the composite on DefaultServer: Update Failed: Error 
while validating JCA Reference Binding meta data during composite deployment. : 
JCA deployment validation errors for 'Adapters/dbReference_db.jca'
.
 
[11:09:45 PM] Check server log for more details.
[11:09:45 PM] Error deploying archive sca_DBadapter.jar to partition "default" on 
server DefaultServer [http://JMUGUETA-ES.es.oracle.com:7101] 
[11:09:45 PM] Deployment cancelled.
[11:09:45 PM] ----  Deployment incomplete  ----.
[11:09:45 PM] Error deploying archive file:/C:/WORK/jdeveloper/mywork/OrangeSamples
/DBadapter/deploy/sca_DBadapter.jar 
 (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)

Enjoy 😉

BPM12c WorkSpace: FlexyFields for Custom Views


With Fexy Fileds you can configure custom views (filtering tasks list shown with flexy fields values criteria) as well as show business data related with human tasks.

STEPS

Create HumanTask Data variables:

flexyfields-0

Assign process data to HumanTask variables:

flexyfields--1

Deploy and create instances.

Configure BPM WorkSpace FleyFields:

This slideshow requires JavaScript.

Configure WorkSpace Views:

This slideshow requires JavaScript.

Administrator can create custom views for others:

flexyfields-20flexyfields-21

😉

BPM User Tasks Assigned to Groups Doesn’t Appear in my CustomWorkListApp


Should you have adquired tasks in your BPM instances that the user didn’t released beacuse abrupt window closing or software implementaion issues/faillures maybe you are querying the BPM engine only for tasks asigned to the group or yourself (me and my group).

BPM has a default configuration of 3 days for task AutoRelease that you can change (see official documentation or https://blogs.oracle.com/soacommunity/entry/how_to_configure_oracle_soa

Anyway, a good idea is making “world class” software by giving end user as much information as possible in order to help resolve issues in a more intuitive way. In this particular case you could query the BPM engine not only for assigned tasks but others such as adquired by others, failled, etc. Is the way the standard worklist app does.

😉