WLS 6.1 - wls 5.1 lookup.

Hi
I face a problem with having to lookup an EJB hosted on a 5.1 server from a
6.1 server.
As I've read in an earlier post in this newsgroup WLS6.1 -> 5.1 naming
factories are not compatible. (Resulting in a
javax.naming.CommunicationException)
As the classnames and packages are identical on 5.1 and 6.1 for JNDI
including the 5.1 factory in the server's classpath is not an option.
Does anyone know of a workaround? (Or a magical compatiblity switch or
something...)
Best regards.
Trond Strømme, Software Engineer, mogul technology.

I think you can recompile the 5.1 EJB with the -iiop option and access it with
env.put(Context.PROVIDER_URL, "iiop://somehost:7001");
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
I haven't tried this between 6.1 and 5.1 but it works between 6.1 and 6.0 which
are also incompatible for normal t3 communication.
See: http://e-docs.bea.com/wls/docs61/rmi_iiop/API_rmi_iiop.html#1054561
for mmore details.
trond strømme wrote:
Hi
I face a problem with having to lookup an EJB hosted on a 5.1 server from a
6.1 server.
As I've read in an earlier post in this newsgroup WLS6.1 -> 5.1 naming
factories are not compatible. (Resulting in a
javax.naming.CommunicationException)
As the classnames and packages are identical on 5.1 and 6.1 for JNDI
including the 5.1 factory in the server's classpath is not an option.
Does anyone know of a workaround? (Or a magical compatiblity switch or
something...)
Best regards.
Trond Strømme, Software Engineer, mogul technology.

Similar Messages

Message transmission from Wls 7 to Wls 8 and then to Wls10

Hi All,
We are currently doing a POC in which we are using Wls 7, Wls 8.1 and Wls 10 . The basic idea of the POC is that we need to post a message on Wls 7, and from Wls 7 the message should reach Wls 8.1 and inturn from Wls 8.1 it should reach Wls 10. For this communication to take place we have configured message bridges on the respective servers.
But the problem that we are facing is, we are not bale to transmit message from one Wls server to other, from Wls 7 to Wls 8 and also from 8 to 10.
We are gettin the following error:-
<Error> <Security> <090473> <ServerIdentity failed validation, downgrading to anonymous.>
Can anybody please help on this.
Regards,
Rakesh

If this is just a POC, you might try enabling Domain Trust on each of the domains (here is the 10.3 link, probably different in 8.1 and 7.0):
http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/security/EnableTrustBetweenDomains.html
In a production environment there are other security implications for doing this willy nilly, that I recommend you read the docs and post questions in the WLS Security forum.

JSTL WLS 7 to WLS 8.1 Upgrade Issues

We have a web app that currently runs on WLS 7. We have been asked to upgrade the app to WLS 8.1 recently. Most of the screen have ported fine, but there are a couple of screens that seem to be throwing fits. It could be a JDK/JRE issue, but here is the scenario
          jstl looks up a string variable property which is set to either "Y" or "N". Using WLS 7, it comes back as either "Y" or "N". But when I run the same code with WLS81, it comes back as "true" or "false".
          Looking at the property right before it returns always shows the correct value. When I look into the parameters and values, they seem to match the above statements as well (Y,N,true,false).
          Here is an interesting twist though. If I switch the JDK to 1.4 on WLS7, it also changes to "true" and "false". I have tried both sun and jrockit jvms to no avail.
          Has anyone seen this behavior?
          Thanks,
          Ashar

That's almost what I said but not quite, you should not have any trouble, but this is the real world hence my suggestion to backup properly first.
As for Yosemite I don't know the answer yet, I would expect it to be a no but we'll have to wait and see.

EJB Migration Problem (WLS 9.2 = WLS 10.3.2)

Hi,
we are migrating Stateful, Stateless, and Message Driven Bean from wls 9.2 to wls 10.3.2. There is no compile error. But workshop shows Error: "Failed to retrieve WLS runtime for EJB processing".
Thank you very much for your input.
John

Hi,
we are migrating Stateful, Stateless, and Message Driven Bean from wls 9.2 to wls 10.3.2. There is no compile error. But workshop shows Error: "Failed to retrieve WLS runtime for EJB processing".
Thank you very much for your input.
John

Corba - differences between WLS 7.02 / WLS 8.1

In WLS 7.02 the following piece of code works, but in WLS 8.1 I get an exception
on the last line (see the log below). Would someone have a clue why it’s not working
with WLS 8.1
Note: if you want to send me an email, remove the NOSPAM
TIA !
public OimSessionInstance openSession() throws EomSessionException {
Properties props = new Properties();
props.put("org.omg.CORBA.ORBInitialPort", (new Short(corbaPortNumber)).toString());
props.put("org.omg.CORBA.ORBInitialHost", serverHost);
try {
orb = ORB.init((String[]) null, props);
String[] services = orb.list_initial_services();
// setting up the CORBA stuff
org.omg.CORBA.Object objRef = orb.resolve_initial_references("NameService");
EomSessionException: class EomSession, method corbaConnection to OIM : exception
: org.omg.CORBA.MARSHAL: Exception waiting for response; nested exception is:
java.io.EOFException: GIOP protocol error vmcid: 0x0 minor code: 0
completed: No
at EomDefaultConnection.openSession(EomDefaultConnection.java:114)
at EomSession.<init>(EomSession.java:78)

"Alain Pigeon" <[email protected]> wrote:
>
In WLS 7.02 the following piece of code works, but in WLS 8.1 I get an
exception
on the last line (see the log below). Would someone have a clue why it’s
not working
with WLS 8.1
Note: if you want to send me an email, remove the NOSPAM
TIA !
public OimSessionInstance openSession() throws EomSessionException {
Properties props = new Properties();
props.put("org.omg.CORBA.ORBInitialPort", (new Short(corbaPortNumber)).toString());
props.put("org.omg.CORBA.ORBInitialHost", serverHost);
try {
orb = ORB.init((String[]) null, props);
String[] services = orb.list_initial_services();
// setting up the CORBA stuff
org.omg.CORBA.Object objRef = orb.resolve_initial_references("NameService");
EomSessionException: class EomSession, method corbaConnection to OIM
: exception
: org.omg.CORBA.MARSHAL: Exception waiting for response; nested exception
is:
java.io.EOFException: GIOP protocol error vmcid: 0x0 minor
code: 0
completed: No
at EomDefaultConnection.openSession(EomDefaultConnection.java:114)
at EomSession.<init>(EomSession.java:78)Found a solution:
In WLS7.0 the code automatically returned the SUN ORB found in the rt.jar. But
in WLS8.1 you have to force it to the SUN ORB by specifying it in the properties
file used to instantiate the ORB.
Example:
public OimSessionInstance openSession() throws EomSessionException {
String ORBClassName = "com.sun.corba.se.internal.iiop.ORB";
String ORBSingletonClassName = "com.sun.corba.se.internal.corba.ORBSingleton";
Properties props = new Properties();
props.put("org.omg.CORBA.ORBClass" , ORBClassName);
props.put("org.omg.CORBA.ORBSingletonClass" , ORBSingletonClassName);
props.put("org.omg.CORBA.ORBInitialPort", (new Short(corbaPortNumber)).toString());
props.put("org.omg.CORBA.ORBInitialHost", serverHost);
try {
orb = ORB.init((String[]) null, props);
String[] services = orb.list_initial_services();
// setting up the CORBA stuff
org.omg.CORBA.Object objRef = orb.resolve_initial_references("NameService");

Transaction difference in WLS 5.1 & WLS 6.1

I have a CMP that does a simple read & update on a file on the AS400. When I
run
this on version 5.1 of Weblogic everything works fine. When I run the same exact
bean
on version 6.1 of WLS I get an SQLException that looks like this.
=======
java.sql.SQLException: [SQL7008] IN901F in DATAIP not valid for operation.
at com.ibm.as400.access.JDError.throwSQLException(JDError.java:359)
at com.ibm.as400.access.AS400JDBCStatement.commonExecute(AS400JDBCStatem
ent.java:570)
at com.ibm.as400.access.AS400JDBCPreparedStatement.executeUpdate(AS400JD
BCPreparedStatement.java:914)
at weblogic.jdbc.jts.Statement.executeUpdate(Statement.java:503)
at com.as400.product.ejb.In901f_yrautr__WebLogic_CMP_RDBMS.ejbStore(In90
1f_yrautr__WebLogic_CMP_RDBMS.java:1207)
====
I found a couple of newsgroups that suggest this type of error is due to "journaling"
not being turned on for that file. Journaling deals with commit / rollback functionality
on the AS400. That would suggest to me that it has to do with my transaction
settings
in my bean, but I have all transactions set to "Never". So my question is, why
would
this work on WLS 5.1 but not on WLS 6.1?? Both versions are using the exact same
file with journaling turned off. It is an EJB 1.1 bean. Any ideas other than
trying to turn on the journaling feature for that file??

I have a CMP that does a simple read & update on a file on the AS400. When I
run
this on version 5.1 of Weblogic everything works fine. When I run the same exact
bean
on version 6.1 of WLS I get an SQLException that looks like this.
=======
java.sql.SQLException: [SQL7008] IN901F in DATAIP not valid for operation.
at com.ibm.as400.access.JDError.throwSQLException(JDError.java:359)
at com.ibm.as400.access.AS400JDBCStatement.commonExecute(AS400JDBCStatem
ent.java:570)
at com.ibm.as400.access.AS400JDBCPreparedStatement.executeUpdate(AS400JD
BCPreparedStatement.java:914)
at weblogic.jdbc.jts.Statement.executeUpdate(Statement.java:503)
at com.as400.product.ejb.In901f_yrautr__WebLogic_CMP_RDBMS.ejbStore(In90
1f_yrautr__WebLogic_CMP_RDBMS.java:1207)
====
I found a couple of newsgroups that suggest this type of error is due to "journaling"
not being turned on for that file. Journaling deals with commit / rollback functionality
on the AS400. That would suggest to me that it has to do with my transaction
settings
in my bean, but I have all transactions set to "Never". So my question is, why
would
this work on WLS 5.1 but not on WLS 6.1?? Both versions are using the exact same
file with journaling turned off. It is an EJB 1.1 bean. Any ideas other than
trying to turn on the journaling feature for that file??

Webservice Migration Problems (WLS 9.2 - WLS 10.3.2)

Hi,
we're upgrading our weblogic server from version 9.2 to 10.3.2. Everything runs just fine in my testing environment except for the webservices we have.
We have 6 webservices (JAX-RPC) which use a generic set of xml schema types to which each webservice offers specialized types that extend the supertype. Here comes the problem: The ant tasks wsdlc and clientgen from wls 9.2 generates java classes that do extend from the superclass. Unfortunatley the same call from the wls 10.3.2 results in a loss of class hierarchy.
Example:
<xs:complexType name="personinfo">
<xs:sequence>
<xs:element name="firstname" type="xs:string"/>
<xs:element name="lastname" type="xs:string"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="fullpersoninfo">
<xs:complexContent>
<xs:extension base="personinfo">
<xs:sequence>
<xs:element name="address" type="xs:string"/>
<xs:element name="city" type="xs:string"/>
<xs:element name="country" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
On WLS 9.2 this results in the following:
class Personinfo {
class Fullpersoninfo extends Personinfo {
On WLS 10.3.2. the result differs:
class Personinfo implements Serializable {
class Fullpersoninfo implements Serializable {
Is there any way to tell the wls 10.3.2 to generate a jax-rpc webservice that obeys the extension directive?
I look forward to your replies =)
Regards,
Johannes Bialek

Hi Jay,
thanks for the reply. Unfortunately using the other ant task doesn't seem to help. This is a WLS8.2 Version of Clientgen (which used the attribute "clientjar" rather than "destDir"/"destFile" and expected "packagename" as a required parameter). I tried id and it seems to have a couple of problems with schema files imported in included schema files. I worked around this by importing in the schema files from the wsdl itself, but now I get a "weblogic.xml.schema.binding.BindingException: ERROR: during code compilation".
Full stack trace:
weblogic.xml.schema.binding.BindingException: ERROR: during code compilation
at weblogic.xml.schema.binding.internal.codegen.Compiler.invoke_compiler(Compiler.java:581)
at weblogic.xml.schema.binding.internal.codegen.Compiler.compile_descriptors(Compiler.java:380)
at weblogic.xml.schema.binding.internal.codegen.Compiler.compile(Compiler.java:290)
at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.addTypesInSchemas(XSDTypeMappingBuilder.java:140)
at weblogic.xml.schema.binding.internal.TypeMappingBuilderBase.processSchemaTypes(TypeMappingBuilderBase.java:310)
at weblogic.webservice.tools.build.internal.Schema2JavaImpl.doTypeMapping(Schema2JavaImpl.java:317)
at weblogic.webservice.tools.build.internal.Schema2JavaImpl.run(Schema2JavaImpl.java:204)
at weblogic.webservice.tools.build.internal.WSDL2JavaImpl.run(WSDL2JavaImpl.java:258)
at weblogic.webservice.tools.build.internal.ClientGenImpl.getTypeMappingFromWSDL(ClientGenImpl.java:747)
at weblogic.webservice.tools.build.internal.ClientGenImpl.doClientGenFromWsdl(ClientGenImpl.java:419)
at weblogic.webservice.tools.build.internal.ClientGenImpl.run(ClientGenImpl.java:359)
at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.doClientGen(ClientGenTask.java:375)
at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:229)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.Main.runBuild(Main.java:758)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
Caused by: java.io.IOException: Compiler failed executable.exec: null
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
at weblogic.xml.schema.binding.internal.codegen.Compiler.invoke_compiler(Compiler.java:575)
... 41 more
Shouldn't we be able to use a 9.2 weblogic.jar for creating webservices that run on a 10.3.2?
Regards,
Johannes

WLS/IIS - protect WLS http service

Hello,
we are currently investigating the use of WLS with IISproxy. IIS is our
preferred web server as we have to use a plugin on top of the web server
that is only available for IIS. This plugin is a tool to protect the web
server.
Our goal is to protect the access to our site with this plugin. So I
have some questions around the protection of the WLS http service:
Can I disable the webLogic HTTP service? The logic says No as IIS has
to proxy te request to this service.
Can I restrict the access to the webLogic HTTP service based on the IP
address of the client? In other words, I just want IIS able to talk to
WLS http service.
franck
PS: We use WLS 5.1 sp6.

Check the spelling of the property name. According to
http://www.weblogic.com/docs51/classdocs/javadocs/weblogic/security/net/Conn
ectionFilter.html it's connectionFilter not ConnectionFilter.
Also, be aware there are security holes in WL 5.1 prior to SP9, don't leave
it into production on SP6 only
"Franck Fourel" <[email protected]> wrote in message
news:[email protected]..
>
I have a look to this connection filter. This is what we need.
I've tried to install it on my server (wls 5.1 sp6), but it does not work.The
WLS log says that the connection filter property
(weblogic.security.net.ConnectionFilter) is not correct: "Found undeclared
property" in the log and the server does not restart when this property is
set.
Is there some limitations to use this filter with the WLS version we use ?
thanks
Alf wrote:
Check
"Installing a Connection Filter",
http://e-docs.bea.com/wls/docs60/adminguide/cnfgsec.html#1063398 and
"Filtering Network Connections" in
http://e-docs.bea.com/wls/docs60/security/prog.html
"Franck Fourel" <[email protected]> wrote in message
news:[email protected]..
Hello,
we are currently investigating the use of WLS with IISproxy. IIS is
our
preferred web server as we have to use a plugin on top of the webserver
that is only available for IIS. This plugin is a tool to protect theweb
server.
Our goal is to protect the access to our site with this plugin. So I
have some questions around the protection of the WLS http service:
Can I disable the webLogic HTTP service? The logic says No as IIS has
to proxy te request to this service.
Can I restrict the access to the webLogic HTTP service based on theIP
address of the client? In other words, I just want IIS able to talk to
WLS http service.
franck
PS: We use WLS 5.1 sp6.

Oracle 11g Support For WLS 10 and WLS 9.2

Hi,
Does anyone know where I can find out definatively when Weblogic 10 and 9.2 will officially support Oracle 11g ?
Any official BEA sources here.
Cheers
Simon

There is only one real answer here: test it and test it thoroughly. Asking this question here is pointless, you cannot trust anyone here to give you advice you can rely on. Whatever is said, you have to validate the claims anyway.
Or did you think that Oracle employees were going to answer your question? If so, you are sadly mistaken. Oracle charges money for giving technical support.

EJB 3.0 lookup with WLS 10.3.0

Hello everyone,
1: Our application runs on Weblogic Application Server,version 10.3.0
2: In our system,we need to deploy an EJB conforming to the EJB 3.0 specification.
Please find the sample code for our UAT environment as below :
/*The remote interface*/
package com.serverside.ejb.session;
import javax.ejb.Remote;
@Remote
public interface ASimpleSessionBeanRemote {
 public void printThis(String print);
/*The bean class*/
package com.serverside.ejb.session;
import javax.ejb.Remote;
import javax.ejb.Stateless;
* Session Bean implementation class ASimpleSessionBean
@Stateless(name="ASimpleSessionBean", mappedName = "ASimpleSessionEJB")
@Remote(ASimpleSessionBeanRemote.class)
public class ASimpleSessionBean implements ASimpleSessionBeanRemote {
* Default constructor.
public ASimpleSessionBean() {
// TODO Auto-generated constructor stub
 @Override
 public void printThis(String print) {
 // TODO Auto-generated method stub
 System.out.println("ASimpleSessionBean : "+print);
3: The above files when packaged in jar get deployed on the server successfully.
4: As per EJB 3.0 specification,the deployement descriptors are not mandatory.Hence,the jar doesn't include ejb-jar.xml and weblogic-ejb-jar.xml
5: Please find below,the EJB3.0 annotations reference as per the Weblogic Application Server Documentation :
Annotation : @Stateless
Package: javax.ejb.Stateless
Attribute : mappedName
Description :
Specifies the product-specific name to which the stateless session bean should be mapped.
You can also use this attribute to specify the JNDI name of this stateless session bean. WebLogic Server uses the value of the mappedName attribute when creating the bean’s global JNDI name. In particular, the JNDI name will be:
mappedName#name_of_businessInterface
where name_of_businessInterface is the fully qualified name of the business interface of this session bean.
For example, if you specify mappedName="bank" and the fully qualified name of the business interface is com.CheckingAccount, then the JNDI of the business interface is bank#com.CheckingAccount.
6: Conforming to the above specification, the sample EJB deployed on our application server has the binding name(as reflected in the jndi tree) as follows :
ASimpleSessionEJB#com.serverside.ejb.session.ASimpleSessionBeanRemote
A jndi lookup using this name succeeds :
InitialContext.doLookup("ASimpleSessionEJB#com.serverside.ejb.session.ASimpleSesionBeanRemote");
7: Now,we want the binding name to be a simple string i.e the lookup must be something like :
InitialContext.doLookup("ASimpleSessionEJB");
8: To implement point-7,we tried using the ejb-jar.xml and weblogic-ejb-jar.xml as follows :
->ejb-jar.xml
<?xml version="1.0" encoding="ASCII"?>
<ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:ejb="http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" version="3.0">
<display-name>ejb</display-name>
<enterprise-beans>
 <session>
 <ejb-name>ASimpleSessionBean</ejb-name>
 <ejb-ref>
 <ejb-ref-name>ASimpleSessionEJB</ejb-ref-name>
 <remote>com.serverside.ejb.session.ASimpleSessionBeanRemote</remote>
 <mapped-name>ASimpleSessionEJB</mapped-name>
 </ejb-ref>
 </session>
</enterprise-beans>
</ejb-jar>
->weblogic-ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-ejb-jar xmlns:wls="http://www.bea.com/ns/weblogic/weblogic-ejb-jar" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd http://www.bea.com/ns/weblogic/weblogic-ejb-jar http://www.bea.com/ns/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd">
<wls:weblogic-enterprise-bean>
 <wls:ejb-name>ASimpleSessionBean</wls:ejb-name>
 <wls:stateless-session-descriptor>
 <wls:business-interface-jndi-name-map>
 <wls:business-remote>ASimpleSessionBeanRemote</wls:business-remote>
 <wls:jndi-name>ASimpleSessionEJB</wls:jndi-name>
 </wls:business-interface-jndi-name-map></wls:stateless-session-descriptor>
 <wls:jndi-name>ASimpleSessionEJB</wls:jndi-name>
</wls:weblogic-enterprise-bean>
</wls:weblogic-ejb-jar>
9: Inspite of the point-8,the binding name remains as follows :
ASimpleSessionEJB#com.serverside.ejb.session.ASimpleSessionBeanRemote
10: Please guide us about the solution and implementation to attend point-7.
Thanks

user13531611 wrote:
10: Please guide us about the solution and implementation to attend point-7.
ThanksOkay. I guide you... to the correct forum branch, because this is a Weblogic specific problem. Server specific issues hardly ever get resolved in the Enteprise Javabeans thread.
http://forums.oracle.com/forums/category.jspa?categoryID=193
Make a new post there and if you are really decent you post a link to it here so in the off-chance that someone capable to help finds this post and thus can follow it to your real thread.

No Lock & Edit button in WLS 10 Console

I don't have the Lock & Edit button in the WLS 10 Console. I know that this could be turned on and off in previous versions of WebLogic in the config.xml file, but I didn't find this anywhere in the documentation anymore.
Can anybody tell me how to make the Lock & Edit buton visible again in WebLogic 10.3a?
Thanx
Peter

Here is my config.xml ( I guess I cannot just attach it):
<?xml version='1.0' encoding='UTF-8'?>
<domain xsi:schemaLocation="http://www.bea.com/ns/weblogic/920/domain.xsd" xmlns="http://www.bea.com/ns/weblogic/920/domain" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xacml="http://www.bea.com/ns/weblogic/90/security/xacml">
 <name>IOP5</name>
 <domain-version>10.3.0.0</domain-version>
 <security-configuration>
 <name>IOP5</name>
 <realm>
 
 <sec:auditor xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-auditorType">
 <sec:name>CSRealmCSAuditor</sec:name>
 <prov:audit-logger-name>@audit.WLSAuditChannel</prov:audit-logger-name>
 <prov:use-wls-log-handler>false</prov:use-wls-log-handler>
 <prov:providers-logs-enabled>false</prov:providers-logs-enabled>
 </sec:auditor>
 <sec:authentication-provider xsi:type="wls:saml-identity-asserter-v2Type">
 <sec:name>SAMLIdentityAsserter</sec:name>
 <wls:name-mapper-class-name>com.csg.cs.security.wls.authentication.saml.SAMLNameMapperImpl</wls:name-mapper-class-name>
 </sec:authentication-provider>
 <sec:authentication-provider xsi:type="prov:cssaml-authenticatorType" xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xmlns:dom="http://www.bea.com/ns/WebLogic/920/domain" xmlns:xsi1="xsi">
 <sec:name>CS SAML Authenticator</sec:name>
 <sec:control-flag>OPTIONAL</sec:control-flag>
 </sec:authentication-provider>


 <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-identity-asserterType">
 <sec:name>CS Identity Asserter</sec:name>
 <prov:credentials-validators>X.509=com.csg.cs.security.wls.authentication.pki.ext.CSPKICredentialValidator</prov:credentials-validators>
 </sec:authentication-provider>
 <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-principal-authenticatorType">
 <sec:name>CS Principal Authenticator</sec:name>
 <sec:control-flag>OPTIONAL</sec:control-flag>
 <prov:credential-validator>com.csg.cs.security.wls.authentication.pki.ext.CSPrincipalCredentialValidator</prov:credential-validator>
 </sec:authentication-provider>
 <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:csb1-authenticatorType">
 <sec:name>CS B1 Authenticator</sec:name>
 <sec:control-flag>OPTIONAL</sec:control-flag>
 
 </sec:authentication-provider>
 <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-authenticatorType">
 <sec:name>CS Authentication Provider</sec:name>
 <sec:control-flag>SUFFICIENT</sec:control-flag>
 <prov:log-in-module-class-name>com.csg.cs.security.wls.authentication.ldap.LDAPAtnLoginModuleImpl</prov:log-in-module-class-name>
 <prov:assertion-module-class-name>com.csg.cs.security.wls.authentication.ldap.LDAPAtnLoginModuleImpl</prov:assertion-module-class-name>
 </sec:authentication-provider>
 <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-internal-identity-asserterType">
 <sec:name>CS Internal Identity Asserter</sec:name>
 </sec:authentication-provider>
 <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-data-layer-providerType">
 <sec:name>CS Data Layer Security Provider</sec:name>
 <sec:control-flag>OPTIONAL</sec:control-flag>
 <prov:key-alias>SYSTEM</prov:key-alias>
 <prov:key-store-pass-phrase-encrypted>{3DES}aqglyJbnET5qUuwQ1cujHw==</prov:key-store-pass-phrase-encrypted>
 <prov:key-pass-phrase-encrypted>{3DES}aqglyJbnET5qUuwQ1cujHw==</prov:key-pass-phrase-encrypted>
 </sec:authentication-provider>
 <sec:role-mapper xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-role-mapperType">
 <sec:name>CS Role Mapper</sec:name>
 <sec:role-deployment-enabled>true</sec:role-deployment-enabled>
 <prov:is-debug>false</prov:is-debug>
 <prov:application-role-mapper-class-name></prov:application-role-mapper-class-name>
 </sec:role-mapper>
 <sec:authorizer xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-authorizerType">
 <sec:name>CS Authorization Provider</sec:name>
 </sec:authorizer>
 <sec:credential-mapper xsi:type="sam:saml2-credential-mapperType" xmlns:sam="http://www.bea.com/ns/weblogic/90/security/saml2">
 <sec:name>SAML2CredentialMapper</sec:name>
 <sam:issuer-uri>http://www.credit-suisse.com</sam:issuer-uri>
 <sam:name-qualifier>CS_SWISS_TEST_PROTECTIONDOMAIN</sam:name-qualifier>
 <sam:name-mapper-class-name>com.csg.cs.security.wls.authentication.saml.SAML2NameMapperImpl</sam:name-mapper-class-name>
 </sec:credential-mapper>
 <sec:credential-mapper xsi:type="wls:saml-credential-mapper-v2Type" xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers">
 <sec:name>SAMLCredentialMapper</sec:name>
 <wls:issuer-uri>http://www.credit-suisse.com</wls:issuer-uri>
 <wls:name-qualifier>CS_SWISS_TEST_PROTECTIONDOMAIN</wls:name-qualifier>
 <wls:name-mapper-class-name>com.csg.cs.security.wls.authentication.saml.SAMLNameMapperImpl</wls:name-mapper-class-name>
 </sec:credential-mapper>
 <sec:credential-mapper xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-credential-mapperType">
 <sec:name>CSCredentialMapper</sec:name>
 </sec:credential-mapper>
 <sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
 <sec:cert-path-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cert-path-providerType">
 <sec:name>CS Certificate Path Provider</sec:name>
 <prov:cert-path-validator-class-name>com.csg.cs.security.wls.authentication.cert.ext.CSPKICertPathValidator</prov:cert-path-validator-class-name>
 </sec:cert-path-provider>
 <sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
 <sec:deploy-role-ignored>true</sec:deploy-role-ignored>
 <sec:deploy-policy-ignored>true</sec:deploy-policy-ignored>
 <sec:deploy-credential-mapping-ignored>false</sec:deploy-credential-mapping-ignored>
 <sec:fully-delegate-authorization>true</sec:fully-delegate-authorization>
 <sec:security-dd-model>Advanced</sec:security-dd-model>
 <sec:name>CSRealm</sec:name>
 <sec:delegate-m-bean-authorization>true</sec:delegate-m-bean-authorization>
 </realm>
 <default-realm>CSRealm</default-realm>
 <anonymous-admin-lookup-enabled>true</anonymous-admin-lookup-enabled>
 <credential-encrypted>{3DES}Zk0PFQd/y2JbBwcVCkoTVA==</credential-encrypted>
 <connection-filter>com.csg.cs.security.wls.net.ConnectionFilterImpl</connection-filter>
 <connection-logger-enabled>true</connection-logger-enabled>
 </security-configuration>
 <server>
 <name>IOPWLS5</name>
 <reverse-dns-allowed>true</reverse-dns-allowed>
 <ssl>
 <use-java>true</use-java>
 <enabled>true</enabled>
 
 <ciphersuite>TLS_RSA_WITH_RC4_128_SHA</ciphersuite>
 <ciphersuite>TLS_RSA_WITH_3DES_EDE_CBC_SHA</ciphersuite>
 <cert-authenticator></cert-authenticator>
 <hostname-verifier>com.csg.cs.security.wls.net.SSL.ext.CSPKIHostNameVerifier</hostname-verifier>
 <hostname-verification-ignored>false</hostname-verification-ignored>
 <export-key-lifespan>500</export-key-lifespan>
 <client-certificate-enforced>false</client-certificate-enforced>
 <listen-port>7002</listen-port>
 <two-way-ssl-enabled>true</two-way-ssl-enabled>
 <server-private-key-alias>tipd.csintra.net</server-private-key-alias>
 <server-private-key-pass-phrase-encrypted>{3DES}mQrgg0qTDHAhuU+2FACgZQ==</server-private-key-pass-phrase-encrypted>
 <ssl-rejection-logging-enabled>true</ssl-rejection-logging-enabled>
 <inbound-certificate-validation>BuiltinSSLValidationAndCertPathValidators</inbound-certificate-validation>
 <outbound-certificate-validation>BuiltinSSLValidationOnly</outbound-certificate-validation>
 </ssl>
 <log>
 <rotate-log-on-startup>true</rotate-log-on-startup>
 <logger-severity>Notice</logger-severity>
 <stdout-severity>Notice</stdout-severity>
 <log-file-filter xsi:nil="true" />
 <stdout-filter xsi:nil="true" />
 <domain-log-broadcast-severity>Notice</domain-log-broadcast-severity>
 <domain-log-broadcast-filter xsi:nil="true" />
 <memory-buffer-filter xsi:nil="true" />
 <redirect-stdout-to-server-log-enabled>true</redirect-stdout-to-server-log-enabled>
 <redirect-stderr-to-server-log-enabled>true</redirect-stderr-to-server-log-enabled>
 </log>
 <machine xsi:nil="true"></machine>
 <listen-port>7001</listen-port>
 <listen-port-enabled>true</listen-port-enabled>
 <cluster xsi:nil="true"></cluster>
 <web-server>


 <send-server-header-enabled>false</send-server-header-enabled>
 </web-server>
 <iiop-enabled>false</iiop-enabled>
 <listen-address>127.0.0.1</listen-address>
 <staging-directory-name>./stage</staging-directory-name>
 <classpath-servlet-disabled>true</classpath-servlet-disabled>
 <key-stores>CustomIdentityAndCommandLineTrust</key-stores>
 <custom-identity-key-store-file-name>./keystores/identity.properties</custom-identity-key-store-file-name>
 <custom-identity-key-store-type>CS_PKI</custom-identity-key-store-type>
 <custom-identity-key-store-pass-phrase-encrypted>{3DES}DbuNFX1jQ5s=</custom-identity-key-store-pass-phrase-encrypted>
 <custom-trust-key-store-file-name>./keystores/trustedca.properties</custom-trust-key-store-file-name>
 <custom-trust-key-store-type>CS_PKI</custom-trust-key-store-type>
 <custom-trust-key-store-pass-phrase-encrypted>{3DES}DbuNFX1jQ5s=</custom-trust-key-store-pass-phrase-encrypted>
 </server>
 <embedded-ldap>
 <name>IOP5</name>
 <credential-encrypted>{3DES}nQpvTCkYlf4h4+8bAEI7JH8pg2Zo4uqNrVEu9bfYSr8=</credential-encrypted>
 </embedded-ldap>
 <administration-port-enabled>true</administration-port-enabled>
 <administration-port>9999</administration-port>
 <configuration-version>10.3.0.0</configuration-version>
 <app-deployment>
 <name>IOPA_root</name>
 <target>IOPWLS5</target>
 <source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPA/root.ear</source-path>

 <security-dd-model>Advanced</security-dd-model>
 <staging-mode>nostage</staging-mode>
 </app-deployment>
 <app-deployment>
 <name>IOPD_prsysmgmt</name>
 <target>IOPWLS5</target>
 <source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPD/prsysmgmt.ear</source-path>

 <security-dd-model>Advanced</security-dd-model>
 <staging-mode>nostage</staging-mode>
 </app-deployment>
 <app-deployment>
 <name>IOPC_prhelp</name>
 <target>IOPWLS5</target>
 <source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPC/prhelp.ear</source-path>

 <security-dd-model>Advanced</security-dd-model>
 <staging-mode>nostage</staging-mode>
 </app-deployment>
 <app-deployment>
 <name>IOPA_prpc_j2ee14</name>
 <target>IOPWLS5</target>
 <source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPA/prpc_j2ee14.ear</source-path>

 <security-dd-model>Advanced</security-dd-model>
 <staging-mode>nostage</staging-mode>
 </app-deployment>
 <app-deployment>
 <name>IOPB_prdbutil</name>
 <target>IOPWLS5</target>
 <source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPB/prdbutil.ear</source-path>

 <security-dd-model>Advanced</security-dd-model>
 <staging-mode>nostage</staging-mode>
 </app-deployment>



 <library>
 <name>CSWSPolicySAML11#[email protected]</name>
 <target>IOPWLS5</target>
 <source-path>C:\cs\appsrv\bin\wl10.3a\wlfw\lib\WSS11SAML1WSPolicy.jar</source-path>
 <deployment-order>1</deployment-order>
 <security-dd-model>Advanced</security-dd-model>
 <staging-mode>nostage</staging-mode>
 </library>
 <library>
 <name>CSWSPolicySAML20#[email protected]</name>
 <target>IOPWLS5</target>
 <source-path>C:\cs\appsrv\bin\wl10.3a\wlfw\lib\SAML2WSPolicy.jar</source-path>
 <deployment-order>1</deployment-order>
 <security-dd-model>Advanced</security-dd-model>
 <staging-mode>nostage</staging-mode>
 </library>






 
 <jms-server>
 <name>PRJMS_Server</name>
 <target>IOPWLS5</target>
 </jms-server>
 <jmx>
 <management-ejb-enabled>false</management-ejb-enabled>
 </jmx>
 <shutdown-class>
 <name>CSServerLifeCycleShutdown</name>
 <target>IOPWLS5</target>
 <class-name>com.csg.cs.security.wls.CSServerLifeCycleShutdown</class-name>
 </shutdown-class>
 <startup-class>
 <name>CSServerLifeCycle</name>
 <target>IOPWLS5</target>
 <class-name>com.csg.cs.security.wls.CSServerLifeCycle</class-name>
 <failure-is-fatal>true</failure-is-fatal>
 <load-before-app-deployments>true</load-before-app-deployments>
 <load-before-app-activation>false</load-before-app-activation>
 </startup-class>

 <jms-system-resource>
 <name>PRJMS_Module</name>
 <target>IOPWLS5</target>
 <sub-deployment>
 <name>PRJMS_Subdeployment</name>
 <target>PRJMS_Server</target>
 </sub-deployment>
 <sub-deployment>
 <name>PRJMS_Subdeployment_Topic</name>
 <target>PRJMS_Server</target>
 </sub-deployment>
 <descriptor-file-name>jms/prjms_module-jms.xml</descriptor-file-name>
 </jms-system-resource>
 <admin-server-name>IOPWLS5</admin-server-name>
 <jdbc-system-resource>
 <name>pega-rules</name>
 <target>IOPWLS5</target>
 <descriptor-file-name>jdbc/pega-rules-jdbc.xml</descriptor-file-name>
 </jdbc-system-resource>

 

 <webservice-security>
 <name>default_wss</name>
 <webservice-token-handler>
 <name>CSTokenHandler</name>
 <class-name>com.csg.cs.security.wls.authentication.wsee.TokenHandler</class-name>
 <token-type>ut</token-type>
 <handling-order>0</handling-order>
 </webservice-token-handler>
 </webservice-security>
</domain>
Regards
Peter

How can use EJB local call in WLS 7.0 without EAR

I have web application as jsp files.
and I made .jar for some EJBs
and I used local call for calling EJB from jsps in WLS 6.1
but in WLS 7.0 .. occured error calling EJB as Local call
while JNDI lookup.
So I packed all applications as EAR and deployed then all works good.
but in developing I want to use JSPs as jsp files.
There is no way to use Local call to EJB in WLS 7.0 without packing EAR ? (like
WLS 6.1)

The way JNDI lookups were implemented in 6.1 allowed to deploy individual ejb-jars
and access their local interfaces via JNDI lookups from other ejb-jars during
development. In production all ejb-jars will be packaged into an ear.
This is extremely helpful on large projects. E.g. my current project has over
120 CMP entity beans and over 40 session beans. Even on 2GHz class machine with
1Gb memory and JDK 1.4 (to enable full-speed debugging) it takes almost a minute
to deploy the ear (no matter whether it is exploded or not). It takes minutes
with 1.3 and debugging turned on.
6.1 implementation allowed to "pre-deploy" relatively static ejb-jars and still
access their local interfaces (by putting them on WL system classpath and deploying
as individual ejb-jars, so classes are accessible to local clients; it requires
WL restart when they are changed, but they don't change often). So during development
only changed jars (typically session facade) need to be redeployed on changes,
which takes only seconds. We didn't have problem with JNDI lookup performance
since we use the EJBHomeFactory pattern.
The behind-the-scene JNDI optimization "improvement" introduced in 7.0 makes it
no longer possible to use this technique, since even though classloading still
works in the same way, no objects are bound to JNDI tree and thus could not be
access from another ejb-jar. This significantly impacts developer productivity
(in our large project). It's not only about minutes lost (which btw makes hours
over time), it just disrupts developer's train of thought to have such long round
trip times. In fact this is the reason we are not going to migrate to WL 7.0.
Is it possible to provide an option to turn this "optimization" off and actually
bind JNDI objects?
Thank you,
Sergey
"Dimitri I. Rakitine" <[email protected]> wrote:
Park <[email protected]> wrote:
Thanks Rakitine.
I wonder if I use EAR while developing could I apply changes to EARwhithout packing
again.Sure - you can simply deploy your app as an 'exploded' EAR during development.
There is no probelm delivering time but in developing time ..
If I can not use that kind of way how can I make modification ?
Plz. let me know.
And I have one more question.
When I use EAR I met some problem.
I packed all JSP into one .war file.
fot that I had to inclde requred classes into .war because jsps usethese classes.
then I packed EAR file with WAR and some EJB jar files.
After then I deployed EAR file to WLS.
But If remove classes from classpth while EJB deploying Error occured.Because
EJBs reference these classes.
I thoght if I packed classes into .WAR .. there is no problem.
But Error occured.
I have to include classes into classpth for that ? or
Any mistakes in my way.No, you do not have to add anything to the system classpath. In fact,
you should
make sure that none of your application classes are in the system classpath.
thank you.
"Dimitri I. Rakitine" <[email protected]> wrote:
Yup, that appears to be the difference between 6.1 and 7.0 - in
6.1 success of a local invocation depended only on the Classloaders
arrangement, so everything worked when you added your classes to the
system classpath. In 7.0 looks like it also depends on the application
context - that's why you cannot do a JNDI lookup from another deployment
unit.
Is there any reason why you do not want to use EAR's ???
Park <[email protected]> wrote:
in WLS 6.1 ..
I have EJB as jar files. (deployed each to WLS)
and I added EJB interface class to classpath.
and I made WebApplication as Directory (not war file).
in that webappication jsp call EJB as Local interface.
These environment .. local call workes well in WLS 6.1.
but in 7.1 not works .. (JNDI look up error)
of course Remote call works well. and If I make EAR .. works well.
Rob Woollen <[email protected]> wrote:
You can have an exploded EAR and have it work.
Can you give some more detail on how you are deploying in 6.1. Is
it
an
exploded EAR, or do you have the ejb interfaces in the classpath?
This behavior should not have changed between 6.1 and 7.0.
-- Rob
park wrote:
I have web application as jsp files.
and I made .jar for some EJBs
and I used local call for calling EJB from jsps in WLS 6.1
but in WLS 7.0 .. occured error calling EJB as Local call
while JNDI lookup.
So I packed all applications as EAR and deployed then all works
good.
but in developing I want to use JSPs as jsp files.
There is no way to use Local call to EJB in WLS 7.0 without packingEAR ? (like
WLS 6.1)
Dimitri
Dimitri

EJB protection and SPIs in WLS 9.1 ?

I am trying to port an Authorization provider to WLS 9.1 which was working fine in WLS 7 and WLS 8.1 to perform EJB protection.
I have the
isAccessAllowed(Subject subject, Map roles, Resource resource, ContextHandler handler,Direction direction)
method in my Authorization provider impl class.
In WLS 7 and WLS 8.1 the Resource object was getting filled correctly with the type of resource.
But when I was testing this on WLS 9.1 by accessing an EJB method (remotely and locally) the Resource object type was <jndi> instead of <ejb>
Did anybody encounter this problem. Basically I am trying to get hold of the details of the EJB being accessed in the custom authorization SPI provider and check permission for the EJB method and act accordingly.
But the Resource object of isAccessAllowed is not filling the <ejb> type and details. It is always filling in it with <jndi> lookup details.
Thanks
Prem

hi
Currently I am using
req.getHeader("WL-Proxy-Client-Cert")
to get the client certificate and then i do the following to get the X509 cert format
 if (pemCert != null && pemCert.length() > 0 ){
 pemCertBuff.append("-----BEGIN CERTIFICATE-----");
 pemCertBuff.append(pemCert);
 pemCertBuff.append("-----END CERTIFICATE-----");
 System.out.println("CertificateUtil:getFingerPrint: pemCertBuff --"+pemCertBuff.toString());
 X509Certificate certs = null;
 try {
 CertificateFactory cf = CertificateFactory.getInstance("X.509");
 ByteArrayInputStream bis = new ByteArrayInputStream(pemCertBuff.toString().getBytes());
 weblogic.security.PEMInputStream pemIs = new weblogic.security.PEMInputStream(bis);
 BufferedInputStream bufis = new BufferedInputStream(pemIs);
 certs = (X509Certificate)cf.generateCertificate(bufis);
 } catch (CertificateException e) {
 // TODO Auto-generated catch block
 e.printStackTrace();
 } catch (IOException e) {
 // TODO Auto-generated catch block
 e.printStackTrace();
And I am able to get the certificate, but I need to know is there any other elegant way to get the certificate as we did using weblogic.security.X509 class?
Please help!!
Message was edited by:
rmkandan

WLS 10.3 ClassCastException obtaining JDBC connection

I have a problem obtaining a JDBC connection in a java client application, using a WLS Datasource.
- I've configured a JDBC datasource in a WLS 10.3 instance, using the Oracle thin driver (not the XA version) - and have successfully targetted this to my server and tested the connection via the console.
- When viewing the JNDI Tree for the server, the Datasource is visible as expected.
However, when I attempt to use a simple client program to obtain a datasource and JDBC connection I get the following error :
java.lang.ClassCastException : weblogic.jdbc.common.internal.ConnectionEnv cannot be cast to java.io.Serializable
Debugging shows a datasource is obtained and that the ClassCastException is thrown when an attempt is made to get a connection from the datasource. Note this code has been used successfully for previous WLS versions to obtain and test a connection (WLS 8.1 - WLS 10) and follows the expected steps :
Hashtable<String, String> ht = new Hashtable<String, String>();
ht.put( Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory" );
ht.put( Context.PROVIDER_URL, "t3://localhost:7001");
javax.naming.Context ctx = new InitialContext( ht );
ds = (javax.sql.DataSource) ctx.lookup( pDataSourceName );
Connection con = ds.getConnection();
The client app has the following Jars on the classpath :
wlclient.jar
jdk1.6.0_07 runtime jar
The client code has been built using jdk1.6.0_07
i) Can you confirm if any additional libraries are required on the classpath
ii) Please indicate if there are any special steps required to obtain a JDBC connection in WLS 10.3
Thanks for your help.
Edited by: user554713 on 23-Dec-2008 02:27

In a Java client the HashTable properties are required to be set.
Context ctx = null;
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
ht.put(Context.PROVIDER_URL, "t3://localhost:7001");
try { ctx = new InitialContext(ht);
// Use the context in your program }
catch (NamingException e) { // a failure occurred }
finally { try {ctx.close();} catch (Exception e)
{ // a failure occurred } }Edited by: dvohra16 on Dec 10, 2009 5:39 PM

XML-RPC in WLS 8.1

Hello,
Currently I am trying to write an application to accept XML-RPC communication
in BEA WebLogic 8.1 from an XML RPC Client. But I am stuck with the implementation
of Server module, which I am trying to do with Web Logic 8.1 Workshop. Is there
any direct support of XML RPC (JAX_RPC) in WLS 8.1 other than basic HTTP-XML?
I have implemented a stand alone Server and Client XML RPC communication using
APACHE's(old helma) XML-RPC implementation and it is working fine. Now I am trying
to do the same Server side functionalities in WLS.
Suppose WLS 8.1 doesn't have any direct support for XML-RPC, Did you come across
any method to use any other third party implementation (Eg. Apache) along with
WLS8.1?
It will be very very helpful, if you could guide me to sort out this messy situation.
Thank you in advance.
warm regards,
Sankaran

Hello,
You might try your question in the workshop newsgroup:
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.workshop
No SOAP?
Bruce
SANKARAN wrote:
>
Hello,
Currently I am trying to write an application to accept XML-RPC communication
in BEA WebLogic 8.1 from an XML RPC Client. But I am stuck with the implementation
of Server module, which I am trying to do with Web Logic 8.1 Workshop. Is there
any direct support of XML RPC (JAX_RPC) in WLS 8.1 other than basic HTTP-XML?
I have implemented a stand alone Server and Client XML RPC communication using
APACHE's(old helma) XML-RPC implementation and it is working fine. Now I am trying
to do the same Server side functionalities in WLS.
Suppose WLS 8.1 doesn't have any direct support for XML-RPC, Did you come across
any method to use any other third party implementation (Eg. Apache) along with
WLS8.1?
It will be very very helpful, if you could guide me to sort out this messy situation.
Thank you in advance.
warm regards,
Sankaran

WLS 6.1 - wls 5.1 lookup.

Similar Messages

Maybe you are looking for