Jar for weblogic client applications?

I am developing a client applications that accesses some session beans from
WLS 6.1 SP1.
I am currently putting the weblogic.jar file in the classpath in order to
be able to access the WLS JNDI server using T3/T3S.
This weblogic.jar file is very large (about 25MB) and includes many things
I am not using.
Is there a way to make a client applications that accesses EJBs in a
weblogic server without using that large file?
Regards,
Vegeta

Please don't cross post. see my reply in weblogic.developer.interest.ejb.
thanks,
Michael
Vegeta wrote:
I am developing a client applications that accesses some session beans from
WLS 6.1 SP1.
I am currently putting the weblogic.jar file in the classpath in order to
be able to access the WLS JNDI server using T3/T3S.
This weblogic.jar file is very large (about 25MB) and includes many things
I am not using.
Is there a way to make a client applications that accesses EJBs in a
weblogic server without using that large file?
Regards,
Vegeta--
Michael Young
Developer Relations Engineer
BEA Support

Similar Messages

SimpleCallbackHandler no longer in weblogic.jar for WebLogic 10.3g

I was using the weblogic.security.SimpleCallbackHandler in WebLogic 9.2 to authenticate users. I looked at the documentation for 10.3g and it still mentions this class is available, however it is not in the weblogic.jar file nor in the javadocs. Here is the URL where I was looking. http://e-docs.bea.com/wls/docs103/security/thin_client.html#wp1035574.
The only CallbackHandler in the 10.3g release seems to be the weblogic.security.URLCallbackHandler class. I tried replacing the SimpleCallbackHandler with this class. When I put the weblogic.jar in my classpath and build, I get the following error.
class file for weblogic.security.acl.internal.AuthenticatedSubject not found
ServletAuthentication.runAs(mySubject, request);
Indeed, this class is not in the weblogic.jar file. Both SimpleCallbackHandler and AuthenticatedSubject were in the weblogic.jar for WebLogic 9.2
<code>
import javax.security.auth.Subject;
import weblogic.security.SimpleCallbackHandler;
import weblogic.security.services.Authentication;
public ActionForward execute(ActionMapping mapping, ActionForm form, HttpServletRequest request, HttpServletResponse response) throws Exception {
LoginForm loginForm = (LoginForm) form;
Subject subject = Authentication.login(new SimpleCallbackHandler(loginForm.getUsername(), loginForm.getPassword().getBytes()));
weblogic.servlet.security.ServletAuthentication.runAs(subject, request);
<./code>
Why were these removed and not deprecated???

SimpleCallbackHandler does not exist in weblogic.jar. Used the following code to get around this. WebLogic documentation offers this as an alternative to using SimpleCallbackHandler.
Subject subject = Authentication.login(new URLCallbackHandler(uid, pwd));
weblogic.servlet.security.ServletAuthentication.runAs(subject, request);
This code agrees with the snippet provided in WebLogic documentation
Project does not compile with the following error:
Project: C:\apps\11g\PrismMainApp\ViewController\ViewController.jpr
C:\apps\11g\PrismMainApp\ViewController\src\adr\prismmain\view\managed\PrismLogin.java
Error(70,28): cannot access weblogic.security.acl.internal.AuthenticatedSubject

Where to download wlst.jar and python.jar for weblogic 10

where to download wlst.jar and python.jar for weblogic 10 ? I am unable to find the links ..most of the prevoius ones point to dev2dev which are no longer valid

Hi,
I have written the below python script to list the user ,that was created in realms->myrealms->users.
It's not working it.
Kindly help to in this python script.
from weblogic.management.security.authentication import UserReaderMBean
from weblogic.management.security.authentication import GroupReaderMBean
file_loc='MbeanValues.properties'
file=java.io.File(file_loc)
if file.exists():
loadProperties(file_loc)
connect(dwlusr,dwlspwd,dwlsurl)
domain_name = cmo.getName()
print 'UserName='+dwlusr
print 'URL='+dwlsurl
print 'DomainName='+ domain_name
print 'welcome'
print 'Checking if isMember of a group'realm=cmo.getSecurityConfiguration().getDefaultRealm()
atns = realm.getAuthenticationProviders()
for i in atns:
if isinstance(i,UserReaderMBean):
userReader = i cursor = i.listUsers("*",0)
print 'Users in realm '+realm.getName()+' are: '
while userReader.haveCurrent(cursor):
print userReader.getCurrentName(cursor)
userReader.advance(cursor)
userReader.close(cursor)for i in atns:
if isinstance(i,GroupReaderMBean):
groupReader = i
cursor = i.listGroups("*",0)
print 'Groups in realm are: '
while groupReader.haveCurrent(cursor):
print groupReader.getCurrentName(cursor)
groupReader.advance(cursor)
groupReader.close(cursor)
disconnect()

.jar file for wls client application

Is there a .jar file include files when client app needs at runtime

You need weblogic jar file and if its ejb client application you might need client
file that can be produced by ejbc.
S
"Wei Li" <[email protected]> wrote:
>
Is there a .jar file include files when client app needs at runtime

How to use two different ojdbc14.jar for two web application.

Hi,
I have two web application running in same tomcat, I need to use the two different ojdbc14.jar for two application, now both are taking the jars from tomcat common/lib directory, I tried copying the new ojdbc14.jar in web-inf/lib folder of one application, but it is not working.
Could you please let me know whether this will take the jar from tomcat by befault or from web-inf, and a solution how to proceed with this.
Thanks in advance.

Yes, I tried removing the jars from common/lib, but as the connection string is mentioned inside the server.xml it is showing db connection error while trying to connect to the database

Using flex for thik client application

My application is an C++ thik client application. It uses
some king of lib (called zaf) for the UI.
Can Flex be used for handling the UI of desktop application
?

You could use AIR (Adobe Integrated Runtime), in which most
of the app is created in Flex, and some in AIR extensions, but
there would be limitations. You can't execute native applications
from AIR applications, so you can't execute Perl scripts, Java
apps, etc. from your AIR app. You can of course use FDS (Flex Data
Services) to connect to POJO, EJB, JavaBeans, SOAP and other web
services, etc.

Problem in creating a build.xml for weblogic portal application

Team ,
I am facing problem in creating the build.xml using weblogic.BuildXMLGEN tool .
a) Below is the structure of my portal application
SrcCode
--- .metadata (eclipse plugins folder)
--- B2BApp ( Ear Content)
--- b2bPortal ( portal related file(controllers,jsp)
--- b2bsrc (java src)
b) Now I executed below utility to generate the build.xml "
java weblogic.BuildXMLGen -projectName B2BApp -username weblogic -file build.xml -password welcome1 F:\srcCode"
c) Based on the above step , build.xml got generated .
d) when I execute "ant compile" target from the command prompt , I see the below exception
ant compile
Buildfile: build.xml
compile:
+[wlcompile] [JAM] Warning: failed to resolve class AbstractJspBacking+
+[wlcompile] [JAM] Error: unexpected exception thrown:+
+[wlcompile] com.bea.util.jam.internal.javadoc.JavadocParsingException: Parsing failure in F:\b2bNew\b2bPortal\src\portlets\b2b\dmr\Picker\PickerController.java at line 58.+
e) I suspect , the problem is bcoz of classpath issues , as I generated build.xml donot have the references to dependent lib's.As build.xml looks like below :
+<target name="compile" description="Only compiles B2BApp application, no appc">+
+<wlcompile srcdir="${src.dir}" destdir="${dest.dir}">+
++
++
++
+.....+
+....+
Please help me to reslove these issues .
PS: I able to deploy the application using 10.3.2 weblogic workshop ( i.e inbuilt eclipse )

i JaySen ,
thanks for your response. As mentioned we added all the necessary library within the -librarydir but still we see the same error :
+[JAM] Error: unexpected exception thrown:+
com.bea.util.jam.internal.javadoc.JavadocParsingException: Parsing failure in F:\b2bNew\b2bPortal\src\portlets\typeAhead\TypeAheadController.java at line 70. Most likely, an annotation is declared whose type has not been imported.
at com.bea.util.jam.internal.javadoc.JavadocTigerDelegateImpl_150.getAnnotationTypeFor(JavadocTigerDelegateImpl_150.java:410)
at com.bea.util.jam.internal.javadoc.JavadocTigerDelegateImpl_150.extractAnnotations(JavadocTigerDelegateImpl_150.java:176)
at com.bea.util.jam.internal.javadoc.JavadocTigerDelegateImpl_150.extractAnnotations(JavadocTigerDelegateImpl_150.java:152)
at com.bea.util.jam.internal.javadoc.JavadocClassBuilder.addAnnotations(JavadocClassBuilder.java:404)
at com.bea.util.jam.internal.javadoc.JavadocClassBuilder.populate(JavadocClassBuilder.java:359)
===================
a) this is a upgrade project [ upgrading from wlp 8.1.4 to 10.3.2 ]
i.e we are using weblogic portal 10.3.2 version.
b) Searched some sites/forums regarding the above error, and it says something related to "jwsc" ant task [ i.e while compiling a webservice(JWS) ], but we see this error while compiling a normal controller(jpf) class :(
c) we are using "ant compile" target which internally calls wlcompile task , while executing wlcompile this error is thrown .
Help Appreciated
Thx,
Sarat

Weblogic.jar for Weblogic 4.5.1

I'm trying to upgrade the Weblogic JSP Compiler optional Ant task so that it
will
work with newer version of Weblogic JSP Compiler. I got it to work for 6.1,
7.0 and 8.1.
The current released version of Ant supports only Weblogic JSP compiler
version 4.5.1.
I want to ensure backward compatibility with 4.5.1 jsp compiler but I don't
have the older version of Weblogic 4.5.1. I've gone to the Bea support site
and apparently, our company's support contract doesn't allow me to download
older versions of WebLogic.
How do I get my hands on the older version? I don't need the entire
product, I just need the portion that has the Weblogic JSP Compiler
(weblogic.jar)

4.5.1 isn't supported anymore so I wouldn't worry about it.
-- Rob
newsgroups.bea.com wrote:
I'm trying to upgrade the Weblogic JSP Compiler optional Ant task so that it
will
work with newer version of Weblogic JSP Compiler. I got it to work for 6.1,
7.0 and 8.1.
The current released version of Ant supports only Weblogic JSP compiler
version 4.5.1.
I want to ensure backward compatibility with 4.5.1 jsp compiler but I don't
have the older version of Weblogic 4.5.1. I've gone to the Bea support site
and apparently, our company's support contract doesn't allow me to download
older versions of WebLogic.
How do I get my hands on the older version? I don't need the entire
product, I just need the portion that has the Weblogic JSP Compiler
(weblogic.jar)

OWSM: Jar for weblogic.wsee.jws.jaxws.owsm.SecurityPolicyFeature

I am developing a JAX-WS client to access the web service which has OWSM policy "wss_username_token_service_policy" attached to it. Hence i am trying to add the below code:
weblogic.wsee.jws.jaxws.owsm.SecurityPolicyFeature[] securityFeature = new weblogic.wsee.jws.jaxws.owsm.SecurityPolicyFeature[]
new weblogic.wsee.jws.jaxws.owsm.SecurityPolicyFeature( "policy:oracle/wss_username_token_service_policy")
But I am unable to find the class SecurityPolicyFeature class in weblogic.wsee.jws.jaxws.owsm package of weblogic.jar. It only has PolicySubjectBindingFeature class in it. Hence I am unable to proceed. Can you let me know where I can find this class?

You're welcome... If you think the answer is helpful/correct just remember to mark it accordingly... Don't just mark the question as anwered, but mark the answers as well...
https://forums.oracle.com/forums/ann.jspa?annID=893
Cheers,
Vlad

Get URL for J2EE client application

Please forgive me if this question has an obvious answer, but I can't see it.
Once Web Start has downloaded and started my J2EE Swing application client, how can my client get the name of the host (or entire URL) from which the client was downloaded?
I would rather not have to hard code this into my client, so that the WAR file I deploy to the server is platform independent.
bobj5000

Use the JNLP BasicSevice API getCodeBase() to get the URL of the server.
BasicService bs = (BasicService)ServiceManager.lookup("javax.jnlp.BasicService");
URL url = bs.getCodeBase();
Hope this helps
Jeff

Could not find Patch CR112484_81sp1.jar for WEBLOGIC 8.1

Due problem with ACTUATE Server 7 WE have to install this patch but we could not
find it ?
Where is it on WL8.1 reference site ?
Thanks

Hello,
As these patch is not publically avialble through BEA Advisories....so you need to open a support case to get this patch. Or otherwise you can upgrade to WLS 8.1 sp2 ,as this issue is fixed in this service pack.
Regards,
Kuldeep.

JNDI lookup fails for client applications

I am currently porting our j2ee application to weblogic 7.0. The application already
runs successfully on Orion and Jboss. I have got everything working now except
for our client applications, which all fail with a JNDI lookup error. The exception
is:
javax.naming.NameNotFoundException: Unable to resolve 'java:comp.env/ejb/QualiferInstance'
Resolved: '' Unresolved:'java:comp' ; remaining name 'java:comp.env
/ejb/QualifierInstance'
at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutbound
equest.java:109)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemote
ef.java:262)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemote
ef.java:229)
at weblogic.jndi.internal.ServerNamingNode_WLStub.lookup(Unknown Source
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:338)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:333)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at BatchIndexer.main(BatchIndexer.java:89)
I have looked up numerous postings on various mailing lists describing similar
problems, but none of them give an explanation which helps me.
I am convinced that I have the ejb deployment descriptors correct because all
our JSPs, servlets and session beans successfully lookup and use the EJBs.
I am also convinced that I have the correct code for the JNDI lookup in our client
applications, because they work perfectly well on Orion and Jboss and use syntax
which is described as correct in the jsee specification, i.e. "java:comp/env/..."
Here is the descriptor from weblogic-ejb-jar.xml for the EJB mentioned in the
example exception above:
<weblogic-enterprise-bean>
<ejb-name>QualifierInstance</ejb-name>
<jndi-name>comp/env/ejb/QualifierInstance</jndi-name>
</weblogic-enterprise-bean>
And here is the descriptor in the application-client.xml file:
     <ejb-ref>
          <ejb-ref-name>ejb/QualifierInstance</ejb-ref-name>
          <ejb-ref-type>Entity</ejb-ref-type>           <home>com.espritsoutron.xengine.ejb.metamodel.QualifierInstanceHome</home>
          <remote>com.espritsoutron.xengine.ejb.metamodel.QualifierInstance</remote>
          <ejb-link>QualifierInstance</ejb-link>
     </ejb-ref>
And here is the code in the client application that attempts to perform the lookup:
qiHome = (QualifierInstanceHome)PortableRemoteObject.narrow(context.lookup("java:comp/env/ejb/QualifierInstance"),
QualifierInstanceHome.class);
The annoying thing is that I know I can make this work if I change the code to
omit the "java:" prefix, but I don't want to do this because then it would no
longer work on either Orion and Jboss.
P.S. I have also tried changing the jndi-name in the weblogic-ejb-jar descriptor
to "ejb/QualifierInstance" and just "QualifierInstance", but neither of these
make any difference. I even tried chaning it to "java:comp/env/ejb/QualifierInstance"
but that totally breaks the server.
Can anyone can please help with this?

you can find the JNDI name in the JNDI tree from the admin console
right click on your server and choose "view jndi tree".
if you bind your ejb to ejb/QualifierInstance
you look it up with that exact same name ejb/QualifierInstance
Julian Fawcett wrote:
I am currently porting our j2ee application to weblogic 7.0. The application already
runs successfully on Orion and Jboss. I have got everything working now except
for our client applications, which all fail with a JNDI lookup error. The exception
is:
javax.naming.NameNotFoundException: Unable to resolve 'java:comp.env/ejb/QualiferInstance'
Resolved: '' Unresolved:'java:comp' ; remaining name 'java:comp.env
/ejb/QualifierInstance'
at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutbound
equest.java:109)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemote
ef.java:262)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemote
ef.java:229)
at weblogic.jndi.internal.ServerNamingNode_WLStub.lookup(Unknown Source
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:338)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:333)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at BatchIndexer.main(BatchIndexer.java:89)
I have looked up numerous postings on various mailing lists describing similar
problems, but none of them give an explanation which helps me.
I am convinced that I have the ejb deployment descriptors correct because all
our JSPs, servlets and session beans successfully lookup and use the EJBs.
I am also convinced that I have the correct code for the JNDI lookup in our client
applications, because they work perfectly well on Orion and Jboss and use syntax
which is described as correct in the jsee specification, i.e. "java:comp/env/..."
Here is the descriptor from weblogic-ejb-jar.xml for the EJB mentioned in the
example exception above:
<weblogic-enterprise-bean>
<ejb-name>QualifierInstance</ejb-name>
<jndi-name>comp/env/ejb/QualifierInstance</jndi-name>
</weblogic-enterprise-bean>
And here is the descriptor in the application-client.xml file:
     <ejb-ref>
          <ejb-ref-name>ejb/QualifierInstance</ejb-ref-name>
          <ejb-ref-type>Entity</ejb-ref-type>           <home>com.espritsoutron.xengine.ejb.metamodel.QualifierInstanceHome</home>
          <remote>com.espritsoutron.xengine.ejb.metamodel.QualifierInstance</remote>
          <ejb-link>QualifierInstance</ejb-link>
     </ejb-ref>
And here is the code in the client application that attempts to perform the lookup:
qiHome = (QualifierInstanceHome)PortableRemoteObject.narrow(context.lookup("java:comp/env/ejb/QualifierInstance"),
QualifierInstanceHome.class);
The annoying thing is that I know I can make this work if I change the code to
omit the "java:" prefix, but I don't want to do this because then it would no
longer work on either Orion and Jboss.
P.S. I have also tried changing the jndi-name in the weblogic-ejb-jar descriptor
to "ejb/QualifierInstance" and just "QualifierInstance", but neither of these
make any difference. I even tried chaning it to "java:comp/env/ejb/QualifierInstance"
but that totally breaks the server.
Can anyone can please help with this?

Classpath for remote client

Hi,
Is there a minimum package of classes (.jar, .zip) that are required for
remote client application to call EJBs in WL 5.1 container ?
My remote application works fine if I include WL_HOME/classes in its
classpath. The problem is that WL_HOME/classes directory is huge. I am
looking for some lightweight package of classes that would contain only
client side implementation of WL's RMI, JNDI and EJB - just enough to
call EJBs from remote client application.
I couldn't find such .jar in the WL 5.1 installation.
Can anybody help ?
thanks,
Rafal

These is no such jar provided by BEA. You can try to create one using
verbose2zip: http://www.weblogic.com/docs51/techstart/utils.html#verbosetozip
If network speed allows for it, you can network classload from WebLogic :
http://dima.dhs.org/misc/ThinClient.jsp or
http://dima.dhs.org/misc/ThinClient2.jsp
(this will download few hundred k, so it is not acceptable for a client
connected via 28.8 modem).
Rafal Mantiuk <[email protected]> wrote:
Hi,
Is there a minimum package of classes (.jar, .zip) that are required for
remote client application to call EJBs in WL 5.1 container ?
My remote application works fine if I include WL_HOME/classes in its
classpath. The problem is that WL_HOME/classes directory is huge. I am
looking for some lightweight package of classes that would contain only
client side implementation of WL's RMI, JNDI and EJB - just enough to
call EJBs from remote client application.
I couldn't find such .jar in the WL 5.1 installation.
Can anybody help ?
thanks,
Rafal--
Dimitri

Complete message timeout in weblogic client

Hi,
We have a weblogic client application connecting to weblogic server 8.1 SP6. The client is getting the below error while executing a rmi call. I have tried setting the CompleteMessagetimeout in weblogic console as well as the client program (-Dweblogic.CompleteMessageTimeout=480). But still the below exception occurs. Any one can help to identify how to set a higher value for CompleteMessageTimeout in client side ? I noticed a number of threads in the forums, but unable to find a concrete answer.
ERROR stdErr 22/Jan/2010/09:45:28 - Caused by: java.io.IOException: A complete message could not be read on socket: 'weblogic.rjvm.t3.T3JVMConnection@125d61e', in the configured timeout period of '60' secs
ERROR stdErr 22/Jan/2010/09:45:28 -      at weblogic.socket.SocketMuxer$TimeoutTrigger.trigger(SocketMuxer.java:796)
ERROR stdErr 22/Jan/2010/09:45:28 -      at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
ERROR stdErr 22/Jan/2010/09:45:28 -      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
ERROR stdErr 22/Jan/2010/09:45:28 -      at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
ERROR stdErr 22/Jan/2010/09:45:28 -      at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
ERROR stdErr 22/Jan/2010/09:45:28 -      at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
ERROR stdErr 22/Jan/2010/09:45:28 -      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
ERROR stdErr 22/Jan/2010/09:45:28 -      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

Hi,
Please try applying the following two properties in the Service Stub... (This change you need to make on Client Program after getting the "port" reference....rest of the code will be same)
((Stub)port)._setProperty("weblogic.wsee.transport.read.timeout ","480");
((Stub)port)._setProperty("weblogic.wsee.transport.connection.timeout ","480");
Actually 60-Seconds is the Default " T3 Connection Timeout " period which u are getting in the Logs...i am finding a way to tune that...amy be some JAVA_OPTIONS..(ideally it is not recommended to change t3 Timeout).
Are you trying to Upload Large amount of file to the WebService?
Example:
HelloWorldService service = new HelloWorldService_Impl();
HelloWorldPortType port = service.getHelloWorldPortTypeSoapPort();
int time=Integer.parseInt(args[1]);
System.out.println("\n\n\t Timeout is set for "+time+"-Seconds");
((Stub)port)._setProperty("weblogic.wsee.transport.read.timeout", time);
((Stub)port)._setProperty("weblogic.wsee.transport.connection.timeout",30);
port.sayHello("Jay");
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com/webservices/ (WebLogic Wonders Are Here)

Jolt for weblogic (5.1) and encryption ?

Hi.
I'm trying to use encryption between Jolt for Weblogic clients and Jolt servers
(JSL/JSH), but I can't get it work.
The JSL's "-Z" option is set to 40, and it boots without errors. Tuxedo 6.5 Security
add-on is installed. Everything works fine without the "-Z" option.
However, the Jolt client, while connecting to JSL, always catches a SessionException
with the following message:
Reason:NwHdlr: open: J_DH Bad Reply\nbea.jolt.JoltException: NwHdlr: open: J_DH
Bad Reply
and nothing is logged on the server side...
Is there something to configure or install on client (i.e. weblogic) side ? Has
anyone already succeeded in using Jolt's encryption ?
Any help welcome...
PS: I have posted this question on several groups, as far as it seems that nobody
knows about Jolt's encryption...

Hi Mathieu,
You may need to install a Tuxedo rolling patch. You need at least:
Tuxedo 6.4 Rolling Patch level 210,
Tuxedo 6.5 rolling patch level 47,
see the following CR:
CR016914 (Jolt only) DiffieHellman Key exchange for Jolt
Also, you may need to have WLS SP 10 installed in order to use
40-bit encryption. See CR 45413 with additional information in the Service
Pack release notes.
CR 45413: Added an international version of Jolt client which is required to talk
with International Tuxedo.
Scott Lynch
Michael Young <[email protected]> wrote:
Hi.
Try posting this to one or both of the following newsgroups:
weblogic.developer.interest.general or tuxedo.general. If you get no
response then I
suggest you open a case with BEA support.
Thanks,
Michael
Mathieu Chauvin wrote:
Hi.
I'm trying to use encryption between Jolt for Weblogic clients andJolt servers
(JSL/JSH), but I can't get it work.
The JSL's "-Z" option is set to 40, and it boots without errors. Tuxedo6.5 Security
add-on is installed. Everything works fine without the "-Z" option.
However, the Jolt client, while connecting to JSL, always catches aSessionException
with the following message:
Reason:NwHdlr: open: J_DH Bad Reply\nbea.jolt.JoltException: NwHdlr:open: J_DH
Bad Reply
and nothing is logged on the server side...
Is there something to configure or install on client (i.e. weblogic)side ? Has
anyone already succeeded in using Jolt's encryption ?
Any help welcome...
PS: I have posted this question on several groups, as far as it seemsthat nobody
knows about Jolt's encryption...--
Developer Relations Engineer
BEA Support

Jar for weblogic client applications?

Similar Messages

Maybe you are looking for