Connect Java PAPI client to 5.7 Studio embedded engine?

I am coding and unit testing some integration of java PAPI client code against a process inALBPM 5.7. But, it is very cumbersome to have to do a fully deploy to a bpm server to do this unit testing.
Is it possible to configure the properties used to create the ProcessService object to connect to the engine that is launched from within the Studio so that I can test locally on my PC? What would the directory.properties have to look like to do so?
Todd

Hi Adam,
Could you please explain more about this?
I want to use PAPI against my local BPM studio. I have the project at "C:\OracleBPMWorkspace\TestProcess". I tried to point the directory to the project, as you suggested. Am i doing it correctly? I get the below exception. Could somebody help me?
Thanks
raj
Configuration:
Properties configuration = new Properties();
configuration.setProperty(ProcessService.DIRECTORY_ID, "Default");
configuration.setProperty(ProcessService.DIRECTORY_PROPERTIES_FILE, "C:\\OracleBPMWorkspace\\TestProcess");
configuration.setProperty(ProcessService.WORKING_FOLDER, "/tmp");
Exception:
java.lang.IllegalStateException: directory configuration runtime fails to initilize with resource: C:\OracleBPMWorkspace\TestProcess
     at fuego.directory.DirectoryConfigurationManager.getDirectoryConfiguration(DirectoryConfigurationManager.java:335)
     at fuego.directory.DirectoryConfigurationManager.getDirectoryConfigType(DirectoryConfigurationManager.java:313)
     at fuego.directory.provider.Factory.getDirectoryFactory(Factory.java:216)
     at fuego.directory.Directory.startAnonymousSession(Directory.java:211)
     at fuego.papi.impl.ProcessServiceFactoryImpl.obtainSchemaId(ProcessServiceFactoryImpl.java:193)
     at fuego.papi.impl.ProcessServiceFactoryImpl.create(ProcessServiceFactoryImpl.java:75)
     at fuego.papi.impl.ProcessServiceFactoryImpl.create(ProcessServiceFactoryImpl.java:63)
     at fuego.papi.ProcessService.create(ProcessService.java:335)
     at com.thomson.tssq.j2012.bpms.PAPI_Test.main(PAPI_Test.java:35)

Similar Messages

Java papi client 57 UserTransaction lookup fails

Guys,
I am trying to write PAPI client which is to run from Tomcat and connecting to ALBPM 5.7 Enterprise which is on Weblogic 92.
I am able to do all operations how ever do see exceptions when PAPI tries to connect to News Topic.
Please let me know if some one has seen this problem in ALBPM5.7 and how it was resolved. I think fix may be in directory.properties by adding/removing some properties but dont know what.
Following is the error message
An error occurred when subscribing to the JMS Topic engine. Reason:'While trying to lookup 'java:comp.UserTransaction' didn't find subcontext 'java:comp'. Resolved ''
Caused by: While trying to lookup 'java:comp.UserTransaction' didn't find subcontext 'java:comp'. Resolved ''
When I checked in directory database, I see following XML in FUEGO_CONFIG table
<?xml version="1.0" encoding="UTF-8"?>
<?fuego version="5.7 GA SP3" application="albpmenteprisej2ee"?>
<set>
     <configuration name="myengine_ENGINE_DB_FUEGOLABS_ARG" type="SQL" subtype="ORACLE">
          <property name="jdbc.pool.idle_timeout" value="5"/>
          <property name="oracle.driver_type" value="thin"/>
          <property name="oracle.dateEqualsTimestamp" value="false"/>
          <property name="jdbc.schema" value="myengine"/>
          <property name="jdbc.host" value="localhost"/>
          <property name="user" value="myengine"/>
          <property name="jdbc.port" value="1521"/>
          <property name="jdbc.pool.min" value="0"/>
          <property name="jdbc.pool.maxopencursors" value="50"/>
          <property name="oracle.sid" value="xe"/>
          <property name="password" value="<encrypted>gGocbn15UL8="/>
          <property name="jdbc.xa" value="false"/>
          <property name="jdbc.pool.max" value="10"/>
     </configuration>
     <configuration name="*myengine_J2EE_LOCAL_FUEGOLABS_ARG*" type="*J2EE*" subtype="*LOCAL_J2EE*">
          <property name="*javax.user.UserTransaction*" value="*java:comp/UserTransaction*"/>
     </configuration>
     <configuration name="myengine_J2EE_RUNTIME_FUEGOLABS_ARG" type="SQL" subtype="REMOTE_JDBC">
          <property name="lookupName" value="XAmyengineDS"/>
          <property name="jdbc.remote.type" value="ORACLE"/>
          <property name="j2ee.provider" value="myengine_J2EE_LOCAL_FUEGOLABS_ARG"/>
     </configuration>
     <configuration name="myengine_J2EE_FDI_FUEGOLABS_ARG" type="SQL" subtype="REMOTE_JDBC">
          <property name="lookupName" value="XAFDIDS"/>
          <property name="jdbc.remote.type" value="ORACLE"/>
          <property name="j2ee.provider" value="myengine_J2EE_LOCAL_FUEGOLABS_ARG"/>
     </configuration>
</set>
Following is my directory.properties (I have tweaked a bit to make it work)
# Directory configuration
# The following properties define the configuration for a directory provider.
# Do not modify the prefix of the properties. Always leave "directory.default."
directory.default.url=oracle://localhost:1521/schema=BEA_FDI,sid=XE
#directory.default.provider=oracle
#directory.default.connector-subtype=ORACLE
#directory.default.directory-res-ref-name=myengine_J2EE_FDI_FUEGOLABS_ARG
# preset properties.
directory.default.preset.datawarehouse.participant=administrator
directory.default.preset.engine.participant=administrator
directory.default.preset.portal-anonymous.participant_password=<crypted>UA7jo3Pvnu12sc/NMcxJ3ijnJHzgtte9YqKhr3hkgQJeZK2sN9b9waFaN6N8S/fMtkcMRWpbMrUVCeXN8zvx7OLaGtCTBQ==
directory.default.preset.xobjects.participant=administrator
directory.default.preset.datawarehouse.participant_password=<crypted>UA7jo3Pvnu12sc/NMcxJ3ijnJHzgtte9Yp/TapxzhLBvmq3JAXqZ/pOgfmVZxXpleLmdse9pFPjhFG4SH4/hmKPhJg==
directory.default.preset.xobjects.participant_password=<crypted>UA7jo3Pvnu12sc/NMcxJ3ijnJHzgtte9YrahnQoZYB8e7NkVzsFfeKe9qrv/oXpltEQYTDSxMrUVCeXN8zs=
directory.default.preset.engine.participant_password=<crypted>UA7jo3Pvnu12sc/NMcxJ3ijnJHzgtte9YmixG3O3OYx0FW4CpqZf/pP8fnS8vEpQ6fpD8kG9FNGrZQhP
directory.default.preset.portal-anonymous.participant=administrator
# custom properties.
# fuego properties.
directory.default.jdbc-user=BEA_FDI
directory.default.jdbc-password=password
#directory.default.skip-auth=true
If you see I have commented following properties above which is basically referring to elements in XML which I have pasted above.
#directory.default.provider=oracle
#directory.default.connector-subtype=ORACLE
#directory.default.directory-res-ref-name=myengine_J2EE_FDI_FUEGOLABS_ARG
Similarly there is UserTransaction entry in FUEGO_CONFIG table xml as highlighted in bold.
Is there any fix/tweak in directory.properties which will resolve my problem?
Thanks in advance for helping.
Anil
Edited by: Anil Hemnani on 22-Apr-2010 23:30
Edited by: Anil Hemnani on 22-Apr-2010 23:30
Edited by: Anil Hemnani on 22-Apr-2010 23:31

Dear fellow forum members,
For future reference:
After a very very long time we received advise from SAP to perform actions we already suggested.....
We have ´hacked´ the keydb.xml file. We must say that SAP gave good detailed advise on which entries to change:
1#. Log on to ABAP and check what password was set for user "ADS_AGENT"
2#. Go to:
/tmp/sapinst_instdir/NW04S/LM/AS-JAVA/ADDIN/ADA/CENTRAL/CI/
1. Save a backup of "keydb.xml" first.
2. Find the following lines at the keydb.xml:
This solved the problem for our customer, so this question can be marked as answered by Casper (my colleague). We hope that SAP will launch a patch to solve this problem, as it has cost us a lot of time and we can imagine that other consultants are facing the same issues, as this seems to be a hashing mechanism that does not perform/work correctly.
Best regards,
Jan Laros

PAPI client calls - stuck threads with albpm57 engine

PAPI client running on weblogic portal 10.3, connecting to ALBPM 5.7 engine (on weblogic 8.1 cluster).
threads get stuck in WLP servers (where PAPI client runs), and the call is for getActiveInstances from default view. We have around 15000 active instances, and the papi cache size is configured for 25000.
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=17 idx=0x7c tid=6615 prio=1 alive, in native, waiting, daemon
-- Waiting for notification on: fuego/papi/impl/lock/SimpleLock@0x1f443568[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)[optimized]
at java/lang/Object.wait(Object.java:485)
at fuego/papi/impl/lock/SimpleLock.readLock(SimpleLock.java:50)
^-- Lock released while waiting: fuego/papi/impl/lock/SimpleLock@0x1f443568[fat lock]
at fuego/papi/impl/InstanceCache$Entry.readLock(InstanceCache.java:708)
at fuego/papi/impl/InstanceCache.getInstancesByFilter(InstanceCache.java:505)
at fuego/papi/impl/InstanceCache.getInstancesByFilter(InstanceCache.java:231)
at fuego/papi/impl/ProcessServiceImpl.getInstancesByFilter(ProcessServiceImpl.java:1084)
at fuego/papi/impl/ProcessServiceNESessionImpl.getInstancesByFilter(ProcessServiceNESessionImpl.java:754)
Please help how to resolve this.
thanks in advance.
Edited by: 811778 on May 17, 2013 5:05 PM

support team suggested to use,
-Dfuego.papi.lockManagerClass=fuego.papi.impl.lock.ParanoidLockManager for each java process, acting as PAPI client. This class available in fuegopapi-client.jar
additional comments from support team,
Implementing this property does not generate side-effects. This property detects and kills/recovers deadlocks in the PAPI instance cache

Connecting Java client to SSL server with existing certificates

I am currently trying to connect my Java client to an existing server application
written in C++. I have been provided the needed certificates (root.pem, server.pem,
and client.pem). My code simply creates a SSLSocket and then attempts to read
from it. Something goes wrong during the handshake process and I get a SSLHandshakeException. The certificates have been added to the keystore
I am using, and I do not know any other action to take.
Here is the debug output:
setting up default SSLSocketFactory
use default SunJSSE impl class: com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl
class com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl is loaded
keyStore is :
keyStore type is : jks
keyStore provider is :
init keystore
init keymanager of type SunX509
trustStore is: keystore.jks
trustStore type is : jks
trustStore provider is :
init truststore
adding as trusted cert:
Subject: [email protected], CN=Employee, OU=test, O=company-USA, L=City, ST=AL, C=US
Issuer: [email protected], CN=company Employee, OU=test, O="company, Inc.", L=City, ST=AL, C=US
Algorithm: RSA; Serial number: 0xb40b909f74d167aa
Valid from Tue Sep 12 09:42:01 CDT 2006 until Thu Oct 12 09:42:01 CDT 2006
adding as trusted cert:
Subject: [email protected], CN=Employee, OU=test, O="company, Inc.", L=City, ST=AL, C=US
Issuer: [email protected], CN=ISAC Employee, OU=test, O="company, Inc.", L=City, ST=AL, C=US
Algorithm: RSA; Serial number: 0xb40b909f74d167ab
Valid from Tue Sep 12 09:49:12 CDT 2006 until Thu Oct 12 09:49:12 CDT 2006
adding as trusted cert:
Subject: [email protected], CN=company Employee, OU=test, O="company, Inc.", L=City, ST=AL, C=US
Issuer: [email protected], CN=company, OU=test, O="company, Inc.", L=City, ST=AL, C=US
Algorithm: RSA; Serial number: 0xf6e3ada87dc4004f
Valid from Tue Sep 12 09:40:32 CDT 2006 until Thu Oct 12 09:40:32 CDT 2006
init context
trigger seeding of SecureRandom
done seeding SecureRandom
instantiated an instance of class com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl
SSL socket created
%% No cached client session
*** ClientHello, TLSv1
RandomCookie: GMT: 1158089181 bytes = { 138, 112, 170, 91, 246, 86, 216, 146, 160, 188, 243, 154, 238, 132, 33, 219, 251, 3, 93, 25, 191, 247, 41, 14, 99, 135, 130, 23 }
Session ID: {}
Cipher Suites: [SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA]
Compression Methods: { 0 }
[write] MD5 and SHA1 hashes: len = 79
0000: 01 00 00 4B 03 01 45 07 0A DD 8A 70 AA 5B F6 56 ...K..E....p.[.V
0010: D8 92 A0 BC F3 9A EE 84 21 DB FB 03 5D 19 BF F7 ........!...]...
0020: 29 0E 63 87 82 17 00 00 24 00 04 00 05 00 2F 00 ).c.....$...../.
0030: 35 00 33 00 39 00 32 00 38 00 0A 00 16 00 13 00 5.3.9.2.8.......
0040: 09 00 15 00 12 00 03 00 08 00 14 00 11 01 00 ...............
Client Thread, WRITE: TLSv1 Handshake, length = 79
[write] MD5 and SHA1 hashes: len = 107
0000: 01 03 01 00 42 00 00 00 20 00 00 04 01 00 80 00 ....B... .......
0010: 00 05 00 00 2F 00 00 35 00 00 33 00 00 39 00 00 ..../..5..3..9..
0020: 32 00 00 38 00 00 0A 07 00 C0 00 00 16 00 00 13 2..8............
0030: 00 00 09 06 00 40 00 00 15 00 00 12 00 00 03 02 .....@..........
0040: 00 80 00 00 08 00 00 14 00 00 11 45 07 0A DD 8A ...........E....
0050: 70 AA 5B F6 56 D8 92 A0 BC F3 9A EE 84 21 DB FB p.[.V........!..
0060: 03 5D 19 BF F7 29 0E 63 87 82 17 .]...).c...
Client Thread, WRITE: SSLv2 client hello message, length = 107
[Raw write]: length = 109
0000: 80 6B 01 03 01 00 42 00 00 00 20 00 00 04 01 00 .k....B... .....
0010: 80 00 00 05 00 00 2F 00 00 35 00 00 33 00 00 39 ....../..5..3..9
0020: 00 00 32 00 00 38 00 00 0A 07 00 C0 00 00 16 00 ..2..8..........
0030: 00 13 00 00 09 06 00 40 00 00 15 00 00 12 00 00 .......@........
0040: 03 02 00 80 00 00 08 00 00 14 00 00 11 45 07 0A .............E..
0050: DD 8A 70 AA 5B F6 56 D8 92 A0 BC F3 9A EE 84 21 ..p.[.V........!
0060: DB FB 03 5D 19 BF F7 29 0E 63 87 82 17 ...]...).c...
Client Thread, received EOFException: error
Client Thread, handling exception: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
Client Thread, SEND TLSv1 ALERT: fatal, description = handshake_failure
Client Thread, WRITE: TLSv1 Alert, length = 2
[Raw write]: length = 7
0000: 15 03 01 00 02 02 28 ......(
Client Thread, called closeSocket()
Error: Remote host closed connection during handshake
Thread-4, handling exception: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake

(I am the original poster of this message, I had to create a new username though).
The original problem had to do with incompatibilities with the protocol and/or cipher suites
used. Now, the client and server perform most of the handshake process, but something
goes wrong as the server requests the client certificate. In other words, the server requires
mutual authentication, but for some reason it seems like my JSSE client won't send over
it's client certificate. I don't get any type of bad certificate exceptions, so I'm not sure
where the source of the error lies.
Updated output:
setting up default SSLSocketFactory
use default SunJSSE impl class: com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl
class com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl is loaded
keyStore is : keystore
keyStore type is : jks
keyStore provider is :
init keystore
init keymanager of type SunX509
trustStore is: truststore
trustStore type is : jks
trustStore provider is :
init truststore
adding as trusted cert:
Subject: [email protected], CN=Employee, OU=default, O="default Inc.", L=default, ST=AL, C=US
Issuer: [email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US
Algorithm: RSA; Serial number: 0xb40b909f74d167ab
Valid from Tue Sep 12 09:49:12 CDT 2006 until Thu Oct 12 09:49:12 CDT 2006
adding as trusted cert:
Subject: [email protected], CN=default-Server, OU=HawkEye, O=default, L=default, ST=AL, C=US
Issuer: [email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US
Algorithm: RSA; Serial number: 0xb40b909f74d167ac
Valid from Tue Sep 12 14:42:28 CDT 2006 until Thu Oct 12 14:42:28 CDT 2006
adding as trusted cert:
Subject: [email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US
Issuer: [email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US
Algorithm: RSA; Serial number: 0xf6e3ada87dc4004f
Valid from Tue Sep 12 09:40:32 CDT 2006 until Thu Oct 12 09:40:32 CDT 2006
init context
trigger seeding of SecureRandom
done seeding SecureRandom
instantiated an instance of class com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl
%% No cached client session
*** ClientHello, TLSv1
RandomCookie: GMT: 1158242806 bytes = { 71, 195, 185, 44, 86, 96, 14, 11, 171, 76, 105, 135, 136, 114, 53, 54, 137, 75, 202, 254, 112, 208, 240, 91, 199, 246, 175, 207 }
Session ID: {}
Cipher Suites: [SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA]
Compression Methods: { 0 }
Client Thread, WRITE: TLSv1 Handshake, length = 79
Client Thread, READ: TLSv1 Handshake, length = 74
*** ServerHello, TLSv1
RandomCookie: GMT: 1158242807 bytes = { 63, 93, 48, 73, 98, 251, 160, 215, 61, 110, 246, 12, 5, 209, 95, 194, 152, 193, 0, 181, 135, 26, 150, 174, 52, 92, 56, 250 }
Session ID: {83, 31, 134, 30, 76, 200, 183, 120, 7, 94, 26, 65, 186, 91, 197, 25, 10, 193, 94, 220, 198, 250, 162, 153, 6, 89, 12, 250, 66, 105, 249, 211}
Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Compression Method: 0
%% Created: [Session-1, TLS_RSA_WITH_AES_128_CBC_SHA]
** TLS_RSA_WITH_AES_128_CBC_SHA
Client Thread, READ: TLSv1 Handshake, length = 1903
*** Certificate chain
chain [0] = [
Version: V3
Subject: [email protected], CN=Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US
Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
Key: Sun RSA public key, 1024 bits
modulus: 164546130673614659100546464587508805401937082626997447139358150641653094778762702643605529386963945060462618417820295217144739538713137107756847225226998964727905246706969036839701385553183842454061172884072035749790213037240682893878786969498404371282074360019097248835858617183835587887295684928062301303789
public exponent: 65537
Validity: [From: Tue Sep 12 09:49:12 CDT 2006,
               To: Thu Oct 12 09:49:12 CDT 2006]
Issuer: [email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US
SerialNumber: [    b40b909f 74d167ab]
Certificate Extensions: 4
[1]: ObjectId: 2.16.840.1.113730.1.13 Criticality=false
Extension unknown: DER encoded OCTET string =
0000: 04 1F 16 1D 4F 70 65 6E 53 53 4C 20 47 65 6E 65 ....OpenSSL Gene
0010: 72 61 74 65 64 20 43 65 72 74 69 66 69 63 61 74 rated Certificat
0020: 65 e
[2]: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
0000: C8 EA 02 93 42 9E 44 D1 55 7D 2D 32 4B 9B 1C 6D ....B.D.U.-2K..m
0010: 63 6B 73 82 cks.
[3]: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
0000: 2C BC 66 DC 06 BA 62 79 3B 1A 20 92 E0 81 71 A0 ,.f...by;. ...q.
0010: 0D 05 3C 95 ..<.
[[email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US]
SerialNumber: [    f6e3ada8 7dc4004f]
[4]: ObjectId: 2.5.29.19 Criticality=false
BasicConstraints:[
CA:false
PathLen: undefined
Algorithm: [SHA1withRSA]
Signature:
0000: BF 60 5A 67 3E E6 F0 92 4F E4 81 6D 71 0A 2E E8 .`Zg>...O..mq...
0010: F3 59 A1 87 7B D1 3A 7A CB FF D6 39 63 79 B6 82 .Y....:z...9cy..
0020: 2A 22 D0 46 51 30 6B 2A 61 6B A0 4C F0 3B CE 5B *".FQ0k*ak.L.;.[
0030: 9C 1D 46 CB D7 C2 B2 23 E2 A5 06 CD 12 F8 A9 CB ..F....#........
0040: B5 A2 43 B1 06 4C 42 B5 67 F2 DF 50 6B BC 8A 5E ..C..LB.g..Pk..^
0050: 95 0D F3 2A 73 A8 5A C8 55 77 D7 36 74 16 9E 05 ...*s.Z.Uw.6t...
0060: 85 C6 DC 3C 44 D3 06 5E 47 0C 1F 80 40 30 C7 D8 ...<D..^G...@0..
0070: 8C 27 FF B9 0C 71 EB D4 31 5C 1F 15 A1 23 6F A2 .'...q..1\...#o.
chain [1] = [
Version: V3
Subject: [email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US
Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
Key: Sun RSA public key, 1024 bits
modulus: 140862286957037297158683104484469503810921697537964422595574798580128510755934413463045842414762254029728885690233847950678735782281077619629628663140568366247472189890316085560712610474766899389736269383565795688749374256479726939861138704211990111677657317335172626254520371267441364353295155431963634875809
public exponent: 65537
Validity: [From: Tue Sep 12 09:40:32 CDT 2006,
               To: Thu Oct 12 09:40:32 CDT 2006]
Issuer: [email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US
SerialNumber: [    f6e3ada8 7dc4004f]
Certificate Extensions: 3
[1]: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
0000: 2C BC 66 DC 06 BA 62 79 3B 1A 20 92 E0 81 71 A0 ,.f...by;. ...q.
0010: 0D 05 3C 95 ..<.
[2]: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
0000: 2C BC 66 DC 06 BA 62 79 3B 1A 20 92 E0 81 71 A0 ,.f...by;. ...q.
0010: 0D 05 3C 95 ..<.
[[email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US]
SerialNumber: [    f6e3ada8 7dc4004f]
[3]: ObjectId: 2.5.29.19 Criticality=false
BasicConstraints:[
CA:true
PathLen:2147483647
Algorithm: [SHA1withRSA]
Signature:
0000: AB 84 38 1F 7B 71 D8 87 FF 24 DB C2 7E DC D0 0B ..8..q...$......
0010: 60 60 14 A8 F8 D5 46 AD 6B FC 33 90 6F 43 08 17 ``....F.k.3.oC..
0020: AE 2B EE 6C 2B 29 85 E2 A6 67 EE 5D A4 61 F3 9E .+.l+)...g.].a..
0030: E7 CA B1 27 F9 11 36 ED 93 05 7B E1 20 90 57 B5 ...'..6..... .W.
0040: C6 F9 8A 9D 50 CD B3 4A 54 DC 1B 52 EC EA 7A 0B ....P..JT..R..z.
0050: B6 E6 95 FD DD 80 BE 66 F0 77 F4 E7 9A 8A A3 EF .......f.w......
0060: 9B 68 57 0C 9C 4B 4C C0 24 C5 34 16 D3 8E 45 27 .hW..KL.$.4...E'
0070: CA 23 F1 E0 C5 5E FB FB AA 1C 21 6E CB 5B 57 D9 .#...^....!n.[W.
Found trusted certificate:
Version: V3
Subject: [email protected], CN=Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US
Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
Key: Sun RSA public key, 1024 bits
modulus: 164546130673614659100546464587508805401937082626997447139358150641653094778762702643605529386963945060462618417820295217144739538713137107756847225226998964727905246706969036839701385553183842454061172884072035749790213037240682893878786969498404371282074360019097248835858617183835587887295684928062301303789
public exponent: 65537
Validity: [From: Tue Sep 12 09:49:12 CDT 2006,
               To: Thu Oct 12 09:49:12 CDT 2006]
Issuer: [email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US
SerialNumber: [    b40b909f 74d167ab]
Certificate Extensions: 4
[1]: ObjectId: 2.16.840.1.113730.1.13 Criticality=false
Extension unknown: DER encoded OCTET string =
0000: 04 1F 16 1D 4F 70 65 6E 53 53 4C 20 47 65 6E 65 ....OpenSSL Gene
0010: 72 61 74 65 64 20 43 65 72 74 69 66 69 63 61 74 rated Certificat
0020: 65 e
[2]: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
0000: C8 EA 02 93 42 9E 44 D1 55 7D 2D 32 4B 9B 1C 6D ....B.D.U.-2K..m
0010: 63 6B 73 82 cks.
[3]: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
0000: 2C BC 66 DC 06 BA 62 79 3B 1A 20 92 E0 81 71 A0 ,.f...by;. ...q.
0010: 0D 05 3C 95 ..<.
[[email protected], CN=default Employee, OU=default, O="default, Inc.", L=default, ST=AL, C=US]
SerialNumber: [    f6e3ada8 7dc4004f]
[4]: ObjectId: 2.5.29.19 Criticality=false
BasicConstraints:[
CA:false
PathLen: undefined
Algorithm: [SHA1withRSA]
Signature:
0000: BF 60 5A 67 3E E6 F0 92 4F E4 81 6D 71 0A 2E E8 .`Zg>...O..mq...
0010: F3 59 A1 87 7B D1 3A 7A CB FF D6 39 63 79 B6 82 .Y....:z...9cy..
0020: 2A 22 D0 46 51 30 6B 2A 61 6B A0 4C F0 3B CE 5B *".FQ0k*ak.L.;.[
0030: 9C 1D 46 CB D7 C2 B2 23 E2 A5 06 CD 12 F8 A9 CB ..F....#........
0040: B5 A2 43 B1 06 4C 42 B5 67 F2 DF 50 6B BC 8A 5E ..C..LB.g..Pk..^
0050: 95 0D F3 2A 73 A8 5A C8 55 77 D7 36 74 16 9E 05 ...*s.Z.Uw.6t...
0060: 85 C6 DC 3C 44 D3 06 5E 47 0C 1F 80 40 30 C7 D8 ...<D..^G...@0..
0070: 8C 27 FF B9 0C 71 EB D4 31 5C 1F 15 A1 23 6F A2 .'...q..1\...#o.
Client Thread, READ: TLSv1 Handshake, length = 13
*** CertificateRequest
Cert Types: RSA, DSS,
Cert Authorities:
*** ServerHelloDone
*** Certificate chain
*** ClientKeyExchange, RSA PreMasterSecret, TLSv1
Random Secret: { 3, 1, 27, 159, 38, 131, 132, 24, 47, 148, 161, 90, 7, 39, 189, 28, 178, 156, 20, 151, 220, 192, 239, 182, 115, 234, 99, 225, 68, 250, 199, 173, 96, 181, 78, 180, 238, 37, 243, 72, 19, 91, 249, 11, 49, 83, 1, 150 }
Client Thread, WRITE: TLSv1 Handshake, length = 141
SESSION KEYGEN:
PreMaster Secret:
0000: 03 01 1B 9F 26 83 84 18 2F 94 A1 5A 07 27 BD 1C ....&.../..Z.'..
0010: B2 9C 14 97 DC C0 EF B6 73 EA 63 E1 44 FA C7 AD ........s.c.D...
0020: 60 B5 4E B4 EE 25 F3 48 13 5B F9 0B 31 53 01 96 `.N..%.H.[..1S..
CONNECTION KEYGEN:
Client Nonce:
0000: 45 09 62 F6 47 C3 B9 2C 56 60 0E 0B AB 4C 69 87 E.b.G..,V`...Li.
0010: 88 72 35 36 89 4B CA FE 70 D0 F0 5B C7 F6 AF CF .r56.K..p..[....
Server Nonce:
0000: 45 09 62 F7 3F 5D 30 49 62 FB A0 D7 3D 6E F6 0C E.b.?]0Ib...=n..
0010: 05 D1 5F C2 98 C1 00 B5 87 1A 96 AE 34 5C 38 FA .._.........4\8.
Master Secret:
0000: 0E 63 38 16 86 A1 84 72 33 2C D7 07 D7 C3 AC E0 .c8....r3,......
0010: AD 5B CD 3B 2E 2A 02 91 1E FE 17 97 4E 3B 56 C3 .[.;.*......N;V.
0020: 5D 0F 7A 99 90 0D 3D 4E 5F 39 C5 EB 6E AD DA 71 ].z...=N_9..n..q
Client MAC write Secret:
0000: 99 32 FA 60 0B 88 36 CD 88 02 D5 4A CA D2 A6 49 .2.`..6....J...I
0010: 69 60 42 B6 i`B.
Server MAC write Secret:
0000: 43 3F 85 72 FB 6D 28 1C BA 1E 8A 26 56 DE 18 FB C?.r.m(....&V...
0010: 01 83 20 7F .. .
Client write key:
0000: 6F 58 29 AB B3 8C F5 75 3C 70 04 DF 9D 01 43 F5 oX)....u<p....C.
Server write key:
0000: 4A D7 E9 63 53 32 78 DF E0 99 89 60 A4 1A 3C E7 J..cS2x....`..<.
Client write IV:
0000: 24 FB 0E 12 AB D2 70 6D 80 B1 B2 BC 78 1A 55 88 $.....pm....x.U.
Server write IV:
0000: E4 75 62 25 46 95 0F 7A 44 16 E2 39 38 AD 29 CD .ub%F..zD..98.).
HawkEye Client Thread, WRITE: TLSv1 Change Cipher Spec, length = 1
*** Finished
verify_data: { 98, 254, 245, 75, 252, 23, 91, 164, 67, 197, 69, 44 }
Client Thread, WRITE: TLSv1 Handshake, length = 48
Client Thread, READ: TLSv1 Alert, length = 2
Client Thread, RECV TLSv1 ALERT: fatal, handshake_failure
Client Thread, called closeSocket()
Client Thread, handling exception: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
Error: Received fatal alert: handshake_failure
Thread-4, handling exception: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

Cannot connect a Java GUI client to an EJB

I am having problems trying to make a Java GUI client connect to an EJB. I am using JRun4.
At first, I tried making the Java GUI client a part of the enterprise application that I am building (of which the EJB is a part of). I included the client as a Java module in the application.xml of the enterprise application.
However, when I try to start the server, containing this application, I get an error saying:
Application authentication required. Incorrect method call.
Now when I try to execute the application from the console, it works fine except when it comes to the part when it has to connect to the EJB. At this point I get an java.lang.reflect.UndeclaredThrowableException. Here's the stack trace:
java.lang.reflect.UndeclaredThrowableException
at $Proxy1.create(Unknown Source)
at mds.Caller.actionPerformed(Caller.java:135)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: jrun.ejb.invocation.ContainerNotFoundException: The EJB container for boss-ejb#Boss could not be found.
at jrun.ejb.invocation.AbstractInvocationProxy.findContainer(AbstractInvocationProxy.java:58)
at jrun.ejb.invocation.LocalInvocationProxyImpl.invoke(LocalInvocationProxyImpl.java:53)
at jrun.ejb.invocation.ClientInvocationHandlerImpl.invoke(ClientInvocationHandlerImpl.java:198)
... 25 more
Since the bean is local, I am using a local reference to the bean in the lookup in the code of the client:
Object o = context.lookup("local/BeanTest")
I tried to use:
Object o = context.lookup("java:comp/env/ejb/BeanTest")
and added an ejb-local-ref in the application-client.xml file of the client. But when I try executing the client in this case, I get an error saying:
No such binding: ejb
I wish someone can help me out with this. My main aim is to get the app client talk to the EJB. Thanks a lot in advance.
Soham

I am not sure of a tool to view the JNDI tree. I have one in Weblogic console. But you can check the JNDI names with a small sample code.
import java.util.*;
import javax.naming.*;
import javax.rmi.PortableRemoteObject;
public class TestEnvironment {
    public static void main(String[] args) {
        Context context   = null;
        Object object     = null;
        // Hashtable for environment properties.
        Hashtable env = new Hashtable();
        env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
        env.put(Context.PROVIDER_URL, "t3://localhost:7001");
        try {
            context   = new InitialContext(env);
            NamingEnumeration enum = context.listBindings("");
            while (enum.hasMore()) {
                Binding binding = (Binding) enum.next();
                System.out.println("Name: " + binding.getName());
                System.out.println("Type: " + binding.getClassName());
                System.out.println("Value: " + binding.getObject());
        } catch (Exception exception) {
            exception.printStackTrace();
}Hope this helps.

Java EJB client "Can't connect to ORB" errors...

I'm writing an application that is a Java EJB client application (no web
stuff at all). Needless to say there are no examples of such an app in
the samples dir, they are all web-based.
My problem is that when I try to run my application (client calls a
stateless session bean on the server and gets a "hello world" string
back) I get a "Could not create the TestService bean:
javax.naming.CommunicationException: Cannot connect to ORB [Root
exception is org.omg.CORBA.COMM_FAILURE: minor code: 1 completed:
Maybe]" error.
This is a very simple test, and I'm getting quite frustrated in trying
to figure out what's actually wrong.
Here's the client code (the bean on the server has been deployed into a
module called achptestEjb, the bean name is TestService)
TestService service = null;
TestServiceHome home=null;
String host = "localhost";
String port = "12345";
try {
Properties env = new Properties();
Context context=null;
String jndiName="ejb/achptestEjb/TestService";
System.out.println("JNDI name is "+jndiName);
env.put
("java.naming.factory.initial","com.sun.jndi.cosnaming.CNCtxFactory");
env.put("java.naming.provider.url", "iiop://"+host+":"+port);
context = new InitialContext(env);
The error comes when the new InitialContext is set with the properties
in the env object.
Any ideas what I'm doing wrong?
It would be a BIG help if iPlanet included one simple pure EJB client
example. There are some of us out here who feel HTML is too limiting
for complicated applications.
Douglas Bullard

I finally found the answer to my problem.... in the Ant script I had
copied from another example, the "-iiop" was lacking in the ejbc
arguments - almost all of the examples assume you'll be calling EJBs
from within the container, instead of a stand-alone client, so they
don't use that flag.
Putting that "-iiop" flag into the ejbc arguments fixed everything.
Thanks, Shivani, for pointing out what is now obvious but was
mysterious.
Douglas Bullard
In article <[email protected]>,
[email protected] says...
I'm writing an application that is a Java EJB client application (no web
stuff at all). Needless to say there are no examples of such an app in
the samples dir, they are all web-based.
My problem is that when I try to run my application (client calls a
stateless session bean on the server and gets a "hello world" string
back) I get a "Could not create the TestService bean:
javax.naming.CommunicationException: Cannot connect to ORB [Root
exception is org.omg.CORBA.COMM_FAILURE: minor code: 1 completed:
Maybe]" error.
This is a very simple test, and I'm getting quite frustrated in trying
to figure out what's actually wrong.
Here's the client code (the bean on the server has been deployed into a
module called achptestEjb, the bean name is TestService)
TestService service = null;
TestServiceHome home=null;
String host = "localhost";
String port = "12345";
try {
Properties env = new Properties();
Context context=null;
String jndiName="ejb/achptestEjb/TestService";
System.out.println("JNDI name is "+jndiName);
env.put
("java.naming.factory.initial","com.sun.jndi.cosnaming.CNCtxFactory");
env.put("java.naming.provider.url", "iiop://"+host+":"+port);
context = new InitialContext(env);
The error comes when the new InitialContext is set with the properties
in the env object.
Any ideas what I'm doing wrong?
It would be a BIG help if iPlanet included one simple pure EJB client
example. There are some of us out here who feel HTML is too limiting
for complicated applications.
Douglas Bullard

Re: Cannot connect Java client to T3S

Timothy Lee wrote:
This should be in one of the FAQs for WLS7. I think this is the message you
get when you do not have a valid certificate, or you forgot to disable cert
validity/hostname checking via
-Dweblogic.security.SSL.IgnoreHostnameVerification=true
The WLS 6.1sp2 message might have been something like:
Failed to connect to t3s://localhost:7002 due to: [t3s://localhost:7002:
Destination unreachable; nested exception is:
java.io.IOException: Server Certificate SubjectDN CommonName
received does not match Server hostname; No available router to destination]
However, I've verified that the -D option (above) fails in 7.0, and using
the console to disable hostname verification also fails in 6.1sp2. This is
exactly what fails for me:
java -cp ~/weblogic6/wlserver6.1/lib/weblogic.jar weblogic.Admin -url
t3s://localhost:7002 PING
(with the error above).
I get the original poster's error (below) with 7.0 even if I disable
hostname verification. In 7.0, SSL isn't enabled by default and you have to
generate your own certs with utils.CertGen password...
I notice that the release notes for 6.1sp3 contain several t3s fixes.
Perhaps it is fixed there. I'm still waiting to be "approved" for the silly
new system bea has in place so I can download patches to test sp3.
(as a software developer, I want to download and test the software I am
thinking of purchasing and running in production. If I can not do that then
the system is broken.)
Hi
The same command works with Weblogic 6.0. Is it a bug of Weblogic
7.0?
Or it is a configuration issue (I use default value for everything for a
newly created domain).
Tim
Timothy Lee wrote:
Hi
I am trying to connect a Java JMS client to Weblogic 7.0 over SSL.
However, I am not able to connect any Java client using t3s (e.g. java
weblogic.Admin PING). The SSLClient from the example works fine in both
Weblogic and JSSE. Is anyone have idea what is wrong with my Weblogic
setting or anything? Here is the error message:
Failed to connect to t3s://localhost:7002 due to: [t3s://localhost:7002:
Destination unreachable; nested exception is:
java.io.IOException: Write Channel Closed, possible SSL handshaking or
trust failure; No available router to destination]
Regards,
Tim

"Kiran" <[email protected]> wrote in message
news:3fafdf60$[email protected]..
I am also getting the same problem. Is there any solution for this?What is the exact error message that you are getting?

PAPI Client program is not working

Hi,
i'm running a sample bpm project in albpm studio 5.7
and tried to get the instance details thru PAPI client, but im getting following exception.
pls help me.
Code:*
package papi.example;
import java.io.Serializable;
import java.util.Properties;
import fuego.papi.CommunicationException;
import fuego.papi.InstanceInfo;
import fuego.papi.OperationException;
import fuego.papi.ProcessService;
import fuego.papi.ProcessServiceSession;
public class PapiExample implements Serializable {
     private static final long serialVersionUID = 6828488904644822028L;
     public static void main(String[] args) throws Exception {
          Properties configuration = new Properties();
          configuration.setProperty(ProcessService.DIRECTORY_ID, "default");
          configuration
                    .setProperty(ProcessService.PROJECT_PATH,
                              "C:/Documents and Settings/458232/bpmProjects/ExpenseManagement.fpr");
          configuration
                    .setProperty(ProcessService.WORKING_FOLDER,
                              "/tmp");
          try {
               ProcessService processService = ProcessService
                         .create(configuration);
               ProcessServiceSession session = processService.createSession(
                         "Peter Jones", "", "localhost");
               for (String processId : session.processesGetIds()) {
                    System.out.println("\n Process: " + processId);
                    for (InstanceInfo instance : session
                              .processGetInstances(processId)) {
                         System.out.println(" -> " + instance.getId());
               session.close();
               processService.close();
          } catch (CommunicationException e) {
               System.out.println("Could not connect to Directory Service");
               e.printStackTrace();
          } catch (OperationException e) {
               System.out.println("Could not perform the requested operation");
               e.printStackTrace();
Exception*:
Local folder /tmp\system\Schema3387192-1626570987\catalogs found.
Loading catalogs from local folder: /tmp\system\Schema3387192-1626570987\catalogs
0 jars found locally.
[CatalogMgrCache] =======================
Registering CatalogMgr [ExpenseManagement.fpr] ...CatalogManagerCache 25934938:
Managers:
Counters:
[CatalogMgrCache] =======================
CatalogMgr [ExpenseManagement.fpr] REGISTERED!CatalogManagerCache 25934938:
Managers:
{ExpenseManagement.fpr=fuego.util.LocalCatalogManager@facf0b}
Counters:
Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
Process: /ExpenseReport#Default-1.0
Unreachable Engine Tolerance (seconds):
by default: 0
to be used: 0
This papi client will not cache exceptions which imply that an engine could not be reached.
The connection to 'tcp://01HW316455:8586' was refused. Details:
tcp://01HW316455:8586. Details: java.io.EOFException)
Caused by: An exception occurred while attempting to connect to: tcp://01HW316455:8586
Caused by: java.io.EOFException
fuego.papi.impl.rmi.EngineLocationStatus$EngineCrashedException: tcp://01HW316455:8586. Details: java.io.EOFException)
     at fuego.papi.impl.rmi.EngineLocationStatus.get(EngineLocationStatus.java:92)
     at fuego.papi.impl.rmi.RMIUtils.connectToLocation(RMIUtils.java:136)
     at fuego.papi.impl.rmi.RMIUtils.connectToEngine(RMIUtils.java:111)
     at fuego.papi.impl.rmi.RMIEngineAccessImpl.createSecureEngineProxy(RMIEngineAccessImpl.java:153)
     at fuego.papi.impl.rmi.RMIEngineAccessImpl.createSecureEngine(RMIEngineAccessImpl.java:105)
     at fuego.papi.impl.ProcessServiceImpl.createSecureEngine(ProcessServiceImpl.java:1222)
     at fuego.papi.impl.ProcessServiceSessionImpl$2.run(ProcessServiceSessionImpl.java:3641)
     at fuego.papi.impl.ProcessServiceImpl.executeEngineOp(ProcessServiceImpl.java:1858)
     at fuego.papi.impl.ProcessServiceSessionImpl.getSecureEngine(ProcessServiceSessionImpl.java:3649)
     at fuego.papi.impl.ProcessServiceImpl.createProcessControl(ProcessServiceImpl.java:1208)
     at fuego.papi.impl.ProcessServiceSessionImpl$1.run(ProcessServiceSessionImpl.java:2481)
     at fuego.papi.impl.ProcessServiceImpl.executeEngineOp(ProcessServiceImpl.java:1858)
     at fuego.papi.impl.ProcessServiceSessionImpl.getProcessControl(ProcessServiceSessionImpl.java:2486)
     at fuego.papi.impl.ProcessServiceSessionImpl.processGetInstances(ProcessServiceSessionImpl.java:2155)
     at papi.example.PapiExample.main(PapiExample.java:41)
Caused by: fuego.rmi.spi.ConnectException: An exception occurred while attempting to connect to: tcp://01HW316455:8586
     at fuego.rmi.ClientCluster.initialize(ClientCluster.java:486)
     at fuego.rmi.ClientCluster.<init>(ClientCluster.java:107)
     at fuego.rmi.ClientCluster.find(ClientCluster.java:228)
     at fuego.rmi.RemoteProxy.<init>(RemoteProxy.java:73)
     at fuego.papi.impl.rmi.PublicEngineProxy.<init>(PublicEngineProxy.java:33)
     at fuego.papi.impl.rmi.EngineLocationStatus.createPublicEngine(EngineLocationStatus.java:109)
     at fuego.papi.impl.rmi.EngineLocationStatus.get(EngineLocationStatus.java:44)
     ... 14 more
Caused by: java.io.EOFException
     at java.io.DataInputStream.readShort(Unknown Source)
     at fuego.rmi.Packet.read(Packet.java:129)
     at fuego.rmi.spi.BaseConnection$Receiver.run(BaseConnection.java:190)
fuego.papi.ProcessNotAvailableException: Process '/ExpenseReport#Default-1.0' not available.
     at fuego.papi.impl.ProcessServiceImpl.createProcessControl(ProcessServiceImpl.java:1215)
     at fuego.papi.impl.ProcessServiceSessionImpl$1.run(ProcessServiceSessionImpl.java:2481)
     at fuego.papi.impl.ProcessServiceImpl.executeEngineOp(ProcessServiceImpl.java:1858)
     at fuego.papi.impl.ProcessServiceSessionImpl.getProcessControl(ProcessServiceSessionImpl.java:2486)
     at fuego.papi.impl.ProcessServiceSessionImpl.processGetInstances(ProcessServiceSessionImpl.java:2155)
     at papi.example.PapiExample.main(PapiExample.java:41)
Caused by: fuego.papi.impl.EngineNotAvailableException: Engine 'ExpenseManagement.fpr' cannot process requests.
     at fuego.papi.impl.rmi.RMIUtils.connectToEngine(RMIUtils.java:119)
     at fuego.papi.impl.rmi.RMIEngineAccessImpl.createSecureEngineProxy(RMIEngineAccessImpl.java:153)
     at fuego.papi.impl.rmi.RMIEngineAccessImpl.createSecureEngine(RMIEngineAccessImpl.java:105)
     at fuego.papi.impl.ProcessServiceImpl.createSecureEngine(ProcessServiceImpl.java:1222)
     at fuego.papi.impl.ProcessServiceSessionImpl$2.run(ProcessServiceSessionImpl.java:3641)
     at fuego.papi.impl.ProcessServiceImpl.executeEngineOp(ProcessServiceImpl.java:1858)
     at fuego.papi.impl.ProcessServiceSessionImpl.getSecureEngine(ProcessServiceSessionImpl.java:3649)
     at fuego.papi.impl.ProcessServiceImpl.createProcessControl(ProcessServiceImpl.java:1208)
     ... 5 more
Could not perform the requested operation

I think problem is with your working folder.
configuration.setProperty(ProcessService.WORKING_FOLDER,"/tmp");
set it to where exactly your application folder path.

PAPI client is running outside a j2ee container

Hi,
I install BPM J2EE 10.3.1 for linux and weblogic 10.3 for linux on Red Hat Linux Enterprise 5. The database' version is 10.2.0.1 for windows and the database is install in window server 2003 sp1 on another machine.
I search this forum and copy and change the code. But I still get error "PAPI client is running outside a j2ee container"
The java code runs in the 3rd machine.
-------------------------java code-------------------------------------------------
Properties configuration = new Properties();
configuration.setProperty(ProcessService.DIRECTORY_ID, "Default");
configuration.setProperty(ProcessService.DIRECTORY_PROPERTIES_FILE, "F:\\share\\192.168.1.103\\directory.xml");
Properties systemProperties = System.getProperties();
systemProperties.setProperty("java.naming.factory.initial", "weblogic.jndi.WLInitialContextFactory");
systemProperties.setProperty("java.naming.provider.url", "t3://192.168.1.103:7001");
ProcessService processService = ProcessService.create(configuration);
ConnectionPassport Conpassport = processService.createPassportWithPreset("container-auth");
Conpassport.setParticipant("jcooper");
Conpassport.setPassword("welcome1");
System.out.println("34");
Conpassport.fillPassport();
System.out.println("36");
ProcessServiceSession session = processService.createSession(Conpassport, null);
System.out.println("38");
String processName = "/processA";
Arguments arguments = Arguments.create();
System.out.println("41");
session.processCreateInstance(processName, "BeginIn", arguments);//
System.out.println("43");
-----------------------error message----------------------------------------------------
D:\JDeveloper11g_20090318\jdk160_05\bin\javaw.exe -client -classpath E:\Jdeveloper10131_20090318\jdev\mywork\GDHZDJDCIntegrationTest\HZGTprocess\classes;D:\BPM_HOME_standalone\client\papi\lib\b1oracle.jar;D:\BPM_HOME_standalone\client\papi\lib\b1util.jar;D:\BPM_HOME_standalone\client\papi\lib\b1base.jar;D:\BPM_HOME_standalone\client\papi\lib\fuegopapi-client.jar hzgtprocess.VM_192_168_1_103_linux
Creating connector [fuego:SQL]
Creating ProcessService with id 'oracle/2009-09-14 13:23:12+08:00'.
********* PAPI (Version 10.3.1.0.0 Mantainance Pack 1 Build # 98982 ) is starting *********
Local folder /tmp\system\Schema3387192-437105321\catalogs found.
Loading catalogs from local folder: /tmp\system\Schema3387192-437105321\catalogs
0 jars found locally.
[CatalogMgrCache] =======================
Registering CatalogMgr [oracle/2009-09-14 13:23:12+08:00] ...CatalogManagerCache 20195943:
Managers:
Counters:
[CatalogMgrCache] =======================
CatalogMgr [oracle/2009-09-14 13:23:12+08:00] REGISTERED!CatalogManagerCache 20195943:
Managers:
{oracle/2009-09-14 13:23:12+08:00=fuego.util.LocalCatalogManager@1cbda0a}
Counters:
ProcessService 'oracle/2009-09-14 13:23:12+08:00' created successfully.
34
36
38
41
Unreachable Engine Tolerance (seconds):
by default: 0
to be used: 0
This papi client will not cache exceptions which imply that an engine could not be reached.
A user transaction provider is not available for reading Papi News received through the JMS Topic (probable reason: PAPI client is running outside a j2ee container). Papi News will be processed anyway. Details: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
The connection to the JMS Topic engine was completed successfully.
Exception in thread "main" fuego.papi.ProcessNotAvailableException: Process '/processA#Default-1.0' not available.
     at fuego.papi.impl.AbstractProcessLoader.createProcess(AbstractProcessLoader.java:96)
     at fuego.papi.impl.AbstractProcessLoader.createProcess(AbstractProcessLoader.java:36)
     at fuego.papi.impl.SessionProcessLoader.load(SessionProcessLoader.java:254)
     at fuego.papi.impl.ProcessManager.get(ProcessManager.java:894)
     at fuego.papi.impl.ProcessServiceImpl.getProcess(ProcessServiceImpl.java:1380)
     at fuego.papi.impl.SessionProcessManager.getProcess(SessionProcessManager.java:143)
     at fuego.papi.impl.ProcessServiceSessionImpl.processGet(ProcessServiceSessionImpl.java:2665)
     at fuego.papi.impl.ProcessServiceSessionImpl.checkBeginPermissions(ProcessServiceSessionImpl.java:4286)
     at fuego.papi.impl.ProcessServiceSessionImpl.processCreateInstance(ProcessServiceSessionImpl.java:3177)
     at hzgtprocess.VM_192_168_1_103_linux.main(VM_192_168_1_103_linux.java:42)
Caused by: fuego.papi.impl.EngineNotAvailableException: Cannot reach engine 'bpmengine' at URL: ''.
     at fuego.papi.impl.EngineNotAvailableException.wrapConnectionException(EngineNotAvailableException.java:80)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.createSecureEngine(J2EEEngineAccessImpl.java:181)
     at fuego.papi.impl.ProcessServiceImpl.createSecureEngine(ProcessServiceImpl.java:1111)
     at fuego.papi.impl.ProcessServiceSessionImpl$2.run(ProcessServiceSessionImpl.java:3987)
     at fuego.papi.impl.ProcessServiceImpl.executeEngineOp(ProcessServiceImpl.java:1693)
     at fuego.papi.impl.ProcessServiceSessionImpl.getSecureEngine(ProcessServiceSessionImpl.java:3995)
     at fuego.papi.impl.AbstractProcessLoader.createProcess(AbstractProcessLoader.java:48)
     ... 9 more
Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
     at javax.naming.InitialContext.init(InitialContext.java:223)
     at javax.naming.InitialContext.<init>(InitialContext.java:197)
     at fuego.util.InitialContextProvider.create(InitialContextProvider.java:44)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.createInitialContext(J2EEEngineAccessImpl.java:492)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.getInitialContext(J2EEEngineAccessImpl.java:293)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.getEngineHome(J2EEEngineAccessImpl.java:277)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.getSecureEngineInterface(J2EEEngineAccessImpl.java:333)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.createSecureEngine(J2EEEngineAccessImpl.java:178)
     ... 14 more
Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
     at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:247)
     at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:46)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:654)
     ... 23 more
The connectivity to the JMS Topic for the server synchronization information has been temporarily interrupted.
Details:
The connectivity to the JMS Topic has been broken due to a JNDI Context initialization problem.
Details:
javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
Caused by: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory
Caused by: weblogic.jndi.WLInitialContextFactory
fuego.papi.impl.j2ee.JMSTopicLookUpException: The connectivity to the JMS Topic has been broken due to a JNDI Context initialization problem.
Details:
javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.lookupTopic(J2EEEngineAccessImpl.java:665)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.run(J2EEEngineAccessImpl.java:574)
Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
     at javax.naming.InitialContext.init(InitialContext.java:223)
     at javax.naming.InitialContext.<init>(InitialContext.java:197)
     at fuego.util.InitialContextProvider.create(InitialContextProvider.java:44)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.createInitialContext(J2EEEngineAccessImpl.java:492)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.access$1000(J2EEEngineAccessImpl.java:68)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.lookupTopic(J2EEEngineAccessImpl.java:660)
     ... 1 more
Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
     at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:247)
     at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:46)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:654)
     ... 8 more
Process exited.

Could this be a CLASSPATH issue?
Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)

Long time to start Java Web Client (Analyzer 6.2.1)??

Does anyone know why Analyzer(6.2.1) takes a long time to start Java Web Client. Sometime it's even take more than 5 minutes. I think it is the Java Plug-in starting on the client computer. Any solution?

The key to Analyzer 6.2.1 running correctly is the version of Sun Java Plugin. The ideal version (most optimal) is 1.3.0_02.Secondary to this if Analyzer performs OK once you are logged in then it could be down to the speed of your connection. The applet compiles at runtime (unlike Analyzer 5 which was a one time download). The delay in getting to the login screen could be this download.Hope this helps.Paul ArmitageAnalitica Ltd.www.analitica.co.uk

NullPointerException at com.sun.jndi.ldap.Connection.run(Connection.java:52

We are using the Sun jndi 1.2.1 files from a Java client to
access the IBM SecureWay Directory 3.2 server. Our test case is
retrieving entries using the ctx.getAttributes (String, String[])
method. Occasionally we are receiving the following error.
java.lang.NullPointerException
at com.sun.jndi.ldap.Connection.run(Connection.java:525)
at java.lang.Thread.run(Thread.java:481)
The java.lang.NullPointerException is coming from the Sun JNDI file.
Our program is not catching this exception.
Has anyone seen this problem before and have any ideas on how this can be resolved?

Download and use LDAP 1.2.3 or JDK 1.3.1.
The problem should go away.

Java Server/Client Applicaton - problem with sending data back

Hello!
I'm trying to write a small server/client chat application in Java. It's server with availability to accept connections from many clients and it's app just for fun... However, I've come up against a huge problem: everything what clients send, arrives to server (I'm sure about that because it is displayed on the Server Application screen) and then server should send it back to all clients but it doesn't work. I have no faintest idea what causes this problem. Maybe you can help me?
Here is my server app code:
import java.net.*;
import java.util.*;
import java.io.*;
* @author Robin
public class Server {
    ServerSocket serw = null;
    Socket socket = null;
    String line = null;
    Vector<ClientThread> Watki = new Vector();
    ClientThread watek = null;
    public Server(int port) {
        try {
            serw = new ServerSocket(port);
            line = "";
            while(true) {
                System.out.println("Running. Waiting for client to connect...");
                socket = serw.accept();
                System.out.println("Connected with:\n" + socket.getInetAddress() + "\n");
                watek = new ClientThread(socket);
                Watki.addElement(watek);
                Watki.firstElement().Send("doszlo?");
        }catch (IOException e) {
            System.out.println("BLAD: " + e);
    public void sendToAll(String s) {
        for(int i = 0; i < Watki.size(); i++) {
            Watki.elementAt(i).Send(s);
    public class ClientThread extends Thread {
        Socket socket;
        DataInputStream in = null;
        DataOutputStream out = null;
        String line = null;
        public ClientThread(Socket s) {
            try {
                this.socket = s;
                in = new DataInputStream(s.getInputStream());
                out = new DataOutputStream(s.getOutputStream());
                start();
            }catch (IOException e) {
                System.out.println("BLAD: " + e);
        public void Send(String s) {
            try {
                out.writeUTF(s);
            }catch (IOException e) {
                System.out.println("BLAD: " + e);
        public void run() {
            try {
                line = "";
                while (true) {
                    line = in.readUTF();
                    System.out.println(line);
                    sendToAll(line);
            }catch (IOException e) {
                System.out.println("BLAD: " + e);
    public static void main(String[] args) {
        Server serwer = new Server(5000);
}And here is client app code:
import java.net.*;
import java.util.*;
import java.io.*;
* @author Robin
public class Client implements Runnable {
    Socket socket = null;
    BufferedReader keyIn = new BufferedReader(new InputStreamReader(System.in));
    DataInputStream in = null;
    DataOutputStream out = null;
    String line = null;
    public Client(String host, int port) {
        try {
            System.out.println("Connecting to " + host + ":" + port);
            socket = new Socket(host, port);
            System.out.println("Connected\nTALK:");
            out = new DataOutputStream(socket.getOutputStream());
            in = new DataInputStream(socket.getInputStream());
            line = "";
            while(!line.toLowerCase().equals(".bye")) {
                line = keyIn.readLine();
                Send(line);
        }catch (UnknownHostException e) {
            System.out.println("BLAD: " + e);
        }catch (IOException e) {
            System.out.println("BLAD: " + e);
    public void Send(String s) {
        try {
            out.writeUTF(s);
        }catch (IOException e) {
            System.out.println("BLAD: " + e);
    public void run() {
        String loaded = "";
        try {
            while(true) {
                loaded = in.readUTF();
                System.out.println(loaded);
        }catch (IOException e) {
            System.out.println("BLAD: " + e);
    public static void main(String[] args) {
        Client client = new Client("localhost", 5000);
}By the way, this app is mainly written in English language (text that appears on the screen) however in functions I used Polish language (for example: BLAD - it means ERROR in English). Sorry for that :)

Yeap, I will change those exceptions later, thanks for advice.
You asked what's going on with it: both applications start with no errors, but when I write something in client side it should be sent to the server and then forwarded to all connected clients but it stops somewhere. However, I added a one line to the server code
line = in.readUTF();
System.out.println(line);
sendToAll(line); and after it reads message from client (no matter which one) it shows that message on the server side screen, then it should send this message to all clients but it doesn't work in this moment. What's confusing: no errors occurs, so it's rather a mistake in my code, but where?
Edited by: Robin3D on Sep 30, 2009 9:07 AM

Exception in Java WebService Client

Hi,
I am using RAD7.0 with WAS6.1, I have generated client from wsdl, I am trying to invoke one of the operation in webservice. I am getting the following error.
The same code is working in local environment, but its getting failed delivary environment.
Error:
2009-05-19 10:25:30,ERROR,com.hbos.dimsarchival.dimsclient.ArchivalBatchJob,WebSphere_EJB_Timer_Service_WorkManager.Alarm Pool : 0 Error while ArchivingDocument
WebServicesFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultString: WSWS3713E: Connection to the remote host 10.164.1.19 failed.Received the following error: Async IO operation failed, reason: RC: 32 There is no process to read data written to a pipe.
faultActor: null
faultDetail:
WSWS3713E: Connection to the remote host 10.164.1.19 failed.Received the following error: Async IO operation failed, reason: RC: 32 There is no process to read data written to a pipe.
     at com.ibm.ws.webservices.engine.transport.http.HttpOutboundChannelConnection.connect(HttpOutboundChannelConnection.java:820)
     at com.ibm.ws.webservices.engine.transport.http.HttpsOutboundChannelConnection.connect(HttpsOutboundChannelConnection.java:210)
     at com.ibm.ws.webservices.engine.transport.http.HTTPSender.invoke(HTTPSender.java:530)
     at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:228)
     at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:228)
     at com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServicesEngine.java:336)
     at com.ibm.ws.webservices.engine.client.Connection.invokeEngine(Connection.java:929)
     at com.ibm.ws.webservices.engine.client.Connection.invoke(Connection.java:722)
     at com.ibm.ws.webservices.engine.client.Connection.invoke(Connection.java:673)
     at com.ibm.ws.webservices.engine.client.Connection.invoke(Connection.java:495)
     at com.ibm.ws.webservices.engine.client.Stub$Invoke.invoke(Stub.java:948)
     at com.hb.dimsarchival.dimsentities.DIMSServiceEndpointBindingStub.archiveDocuments(DIMSServiceEndpointBindingStub.java:1136)
     at com.hb.dimsarchival.dimsclient.ArchivalBatchJob.archiveDocuments(ArchivalBatchJob.java:106)
     at com.hb.dimsarchival.archivescript.ArchiveSchedulerBean.ejbTimeout(ArchiveSchedulerBean.java:130)
     at com.ibm.ejs.container.TimedObjectWrapper.ejbTimeout(TimedObjectWrapper.java:90)
     at com.ibm.ejs.container.TimerTaskHandler.doWork(TimerTaskHandler.java:265)
     at com.ibm.ws.scheduler.AlarmListener.executeTaskWithNotification(AlarmListener.java:795)
Service is available, and its running successfully. I have checked the endpoint url.
Can any one help me on this topic.
Edited by: javausers07 on May 20, 2009 7:45 AM

Hi, I Found the solution.
Its mistake in SSLConfiguration. End point url is given in IP but in SSL configuration we have give workstation name.
So instead of getting SSLConfiguration issue we got this issue.
Thanks alot.

Creating instances in Java Papi

Hi all,
Actually,I am a newbie to aqualogic bpm.I have written a papi code in java to get process instances directly from studio workspace.Now, I want to crate process instances in java papi code itself and then getting those instances.I don't know how to do that.Can anybody help please?

Hi Dan,
That's pretty good but it is exposing all methods and that's a WSDL file.. Here is some PAPI-WS code that somebody on some other thread put up.. But it does not work properly.. Do you know what files to import to the JAVA project to make it to work?
import java.net.MalformedURLException;
import java.rmi.RemoteException;
import javax.xml.rpc.ServiceException;
import com.bea.albpm.PapiWebService.OperationException;
public class CreateInstances {
public static void main(String[] args) throws MalformedURLException, ServiceException, OperationException, RemoteException {
java.net.URL url = null;
org.apache.axis.EngineConfiguration config = null;
com.bea.albpm.PapiWebService.PapiWebServicePortBindingStub binding = null;
com.bea.albpm.PapiWebService.InstanceInfoBean value = null;
//String processId = "/Proceso1";
//String processId = "/ActividadesExternas";
String processId = "/PAPIWS";
String argumentsSetName = "BeginIn";
//Binding
//url = new java.net.URL("http", "localhost", 8686, "/papiws/PapiWebServiceEndpoint");
url = new java.net.URL("http", "localhost", 8585, "/papiws/PapiWebServiceEndpoint");
config = new org.apache.axis.configuration.FileProvider("client_deploy.wsdd");
binding = (com.bea.albpm.PapiWebService.PapiWebServicePortBindingStub) new com.bea.albpm.PapiWebService.PapiWebService_ServiceLocator(config).getPapiWebServicePort(url);
binding.setTimeout(60000);
//Arguments
com.bea.albpm.PapiWebService.ArgumentsBeanArgumentsEntry argumentsBeanArgumentsEntry[] = new com.bea.albpm.PapiWebService.ArgumentsBeanArgumentsEntry[1];
argumentsBeanArgumentsEntry[0] = new com.bea.albpm.PapiWebService.ArgumentsBeanArgumentsEntry();
argumentsBeanArgumentsEntry[0].setKey("entradaArg");
argumentsBeanArgumentsEntry[0].setValue("Instancia creada de forma externa mediante PAPI-WS 2.0");
com.bea.albpm.PapiWebService.ArgumentsBean argumentsBean = new com.bea.albpm.PapiWebService.ArgumentsBean(argumentsBeanArgumentsEntry);
com.bea.albpm.PapiWebService.holders.ArgumentsBeanHolder argumentsBeanHolder = new com.bea.albpm.PapiWebService.holders.ArgumentsBeanHolder(argumentsBean);
//Create instance
value = binding.processCreateInstance(processId, argumentsSetName, argumentsBeanHolder);
System.out.println("Created instance -> InstanceInfo.id = " + value.getId());
Edited by: user8752903 on Oct 28, 2009 8:49 AM

WS-PAPI client communication (SOAP)

I'm writing a web service (it's Global Activity) in ALBPM and I have a little question about SOAP encapsulation. When other app calls my web service, I do something inside my web service, and the result of web service is some xml created by me, for simplicity assume it looks like this:
<output>
<arg1>aaa</arg1>
<arg2>bbb</arg2>
</output>
But what should I do, when I have to use SOAP? Should I manually add soap envelope&body parts and everything needed to my output xml? Or my output xml will be automatically wrapped to SOAP message by WS-PAPI before sending to client, and I don't have to care about SOAP? Because I read in documentation of WS-PAPI:
The client application connected to PAPI Web Service, uses SOAP (Simple Object Access
Protocol) over HTTP to invoke any of the functions listed in the WSDL. PAPI Web Service relies on
PAPI to obtain the information the client requests. Then it translates this information into
XML and uses SOAP to send it back to the client.
PAPI Web Service implementation is based on the following:
+ JAX-WS 2.0 web service+
+ WS-I 1.1 compliant+
+ Document/literal wrapped style WSDL SOAP binding+
Anybody with concrete experiences? Thanx for answering

I have exactly the same problem.
how you solved this issue?

Connect Java PAPI client to 5.7 Studio embedded engine?

Similar Messages

Maybe you are looking for