JNDI Administration

With the current version of the web console in WLS6.1SP1, you can view the
JNDI tree... (except for the com/env area)
Thats fine.
However, is there a way to modify primitive values from the administration
console? If yes, how? If no, are there any plans to be able to?
My problem is that I want to set some configuration settings - which are all
strings (e.g URL's of soap services, logging pattern layouts etc) or
ints(deal limits, timeout settings) and I want an administrator to be change
these settings in a production environment.
Do I have to write administration code - or is it already done?
Cheers, thanks.
-Nick

Using JMX can be very convinient here, but, unfortunately, WebLogic
doesn't support user MBeans (yet?)
Nick Minutello <[email protected]> wrote:
With the current version of the web console in WLS6.1SP1, you can view the
JNDI tree... (except for the com/env area)
Thats fine.
However, is there a way to modify primitive values from the administration
console? If yes, how? If no, are there any plans to be able to?
My problem is that I want to set some configuration settings - which are all
strings (e.g URL's of soap services, logging pattern layouts etc) or
ints(deal limits, timeout settings) and I want an administrator to be change
these settings in a production environment.
Do I have to write administration code - or is it already done?
Cheers, thanks.
-Nick--
Dimitri

Similar Messages

JNDI Administration in Weblogic 10.3

This is my code:
InitialContext initialContext = new InitialContext();
Context context = (Context) initialContext.lookup("java:comp/env");
bootstrapFlag = (Boolean) context.lookup("bootStrapFlag");
Could anyone guide me how to configure the "bootStrapFlag" as a JNDI entry in Weblogic 10.3
Also please let me know if java.net.URL entry can be created in the Weblogic JNDI.
Thanks
Jayakumar

Hi,
If you are using Framework like Spring ...then you can use the following technique as well : http://jaysensharma.wordpress.com/2010/04/06/bindingaccessing-jndi-names-using-spring-framework/
Plain Java Implementation
If you want to Bind any object in the Server JNDI Tree (Emp, java.net.URL) ...then you can also use InitialContext.bind(String) method.
Example:
Step1). Create a Class "Employee.java" suppose you want to bind the Employee Object in the Server JNDI Tree... Make Sure that the Object is declared as java.io.Serializable
package pack;
public class Employee implements java.io.Serializable
private int empNo;
public Employee()
System.out.println("\n\n\t Employee Object Instentiated...With EmpId:0");
public Employee(int empNo)
System.out.println("\n\n\t Employee Object Instentiated...With EmpId:"+empNo);
Step2). Compile it and make a Jar of it...like "Employee.jar".
Step3). Make this JAR available in the Server Classpath...or you can paste this Jar in the Domain/Lib directory:
Example: C:\bea103\user_projects\domains\7001_Domain_Name\lib
Step4). Restart the Server sothat it can pick up the Employee.jar from the Classpath.
Step5). Write another Program as a Client "BindingStartUp.java" to Bind this Object in the Server JNDI tree...
import java.rmi.*;
import javax.naming.*;
import java.util.*;
public class BindingStartUp
public final static String JNDI_FACTORY = "weblogic.jndi.WLInitialContextFactory";
private static String serverUrl ="t3://localhost:7001";
public static void main(String ar[])throws Exception
InitialContext ic=null;
try{
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);
env.put(Context.PROVIDER_URL, serverUrl);
ic = new InitialContext(env);
catch(Exception e){
System.out.println("\n\n\t Unable To Get The InitialContext => "+e);
try{
pack.Employee emp=new pack.Employee(1000);
ic.rebind("EmpJndiName",emp);
System.out.println("\n\n\t Employee Object Binded in the JNDI Tree Of Server Suuccessfully");
System.out.println("\n\n\t You can use (pack.Emp)ic.lookup(\"EmpJndiName\");");
System.out.println("\t To Lookup the Employee Object from the JNDI Tree");
catch(Exception e)
System.out.println("\n\n\t Unable To Bind => "+e);
e.printStackTrace();
Step6). Now as soon as you run this Client Program it will,Bind this Object in the Server JNDI tree...You can verify it from the AdminConsole---JNDITree section
Step7). Now u can write the Smilar code ...to Lookup the Object from JNDI tree....
You can use (pack.Emp)ic.lookup(\"EmpJndiName\");
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)
Edited by: Jay SenSharma on Feb 24, 2010 8:06 PM

Problem with JNDI and JSP in Tomcat

Hi,
Basically, what I've done is to use the Tomcat administration web
application to create the DataSource, which looks like it populated the
server.xml (see below). I then try to access the testconn.jsp, and am
getting that "Name java:comp is not bound in this Context" error.
I was wondering if anyone could tell me what I'm doing wrong?
Thanks,
Feri
My Configuration:
- Tomcat 5.0.19
- MySQL 4.0.18-nt
- mysql-connector-java-3.0.15-ga-bin.jar
server.xml:
<GlobalNamingResources>

<Environment name="simpleValue" type="java.lang.Integer" value="30"/>

<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved">
</Resource>
<ResourceParams name="UserDatabase">
<parameter>
<name>factory</name>
<value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
</parameter>
<parameter>
<name>pathname</name>
<value>conf/tomcat-users.xml</value>
</parameter>
</ResourceParams>

     <Context crossContext="true" debug="5" docBase="injury" path="/injury" reloadable="true">
     <Logger className="org.apache.catalina.logger.FileLogger" prefix="localhost_injury_log." suffix=".txt" timestamp="true"/>
          <Resource name="jdbc/injury" auth="Container"
type="javax.sql.DataSource">
</Resource>
<ResourceParams name="jdbc/injury">
     <parameter>
          <name>factory</name>
          <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
     </parameter>
<parameter>
<name>username</name>
<value>root</value>
</parameter>
<parameter>
<name>password</name>
<value>root</value>
</parameter>
     <parameter>
<name>driverClassName</name>
<value>com.mysql.jdbc.Driver</value>
</parameter>
     <parameter>
<name>url</name>
<value>jdbc:mysql://localhost:3306/injury</value>
</parameter>
     <parameter>
          <name>maxIdle</name>
          <value>30</value>
     </parameter>
     <parameter>
          <name>maxActive</name>
          <value>10</value>
     </parameter>
     <parameter>
          <name>maxWait</name>
          <value>10000</value>
     </parameter>
</ResourceParams>
     </Context>

</GlobalNamingResources>
\webapps\injury\WEB-INF\web.xml:
<resource-ref>
<description>Resource reference to a factory for java.sql.Connection instances that may be used for talking to a particular database that is configured in the server.xml file.</description>
<res-ref-name>jdbc/injury</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
\webapps\injury\testconn.jsp
<%@ page import="java.sql.*" %>
<%@ page import="javax.sql.*" %>
<%@ taglib prefix="ct" uri="/injury" %>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1250">
<h1>Connection test</h1>
<ct:connection name="jdbc/injury">
<%
Statement stmt= conn.createStatement();
ResultSet rs;
rs = stmt.executeQuery("select * from user");
while (rs.next()){
%><%=rs.getString(1)%><%=rs.getInt(2) %><br><%
rs.close();
stmt.close();
%>
</ct:connection>
ConnectionTag.java
import java.io.*;
import java.sql.*;
import javax.servlet.*;
import javax.servlet.jsp.*;
import javax.servlet.jsp.tagext.*;
import javax.naming.*;
import javax.sql.*;
import javax.sql.DataSource;
public class ConnectionTag extends TagSupport implements TryCatchFinally {
private Connection conn;
// JNDI name of the connection
private String name;
public void setName(String name)
     this.name = name;
public int doStartTag()
     throws JspException
     try {
     Context env = (Context) new InitialContext().lookup("java:comp/env");
     DataSource ds = (DataSource) env.lookup(name);
     if (ds != null)
          conn = ds.getConnection();
     } catch (Exception e) {
     throw new JspException(e);
     if (conn == null)
     throw new JspException("can't open connection " + name);
     pageContext.setAttribute("conn", conn);
     return EVAL_BODY_INCLUDE;
public void doCatch(Throwable t)
     throws Throwable
     throw t;
public void doFinally()
     try {
     Connection conn = this.conn;
     this.conn = null;
     pageContext.removeAttribute("conn");
     conn.close();
     } catch (Exception e) {
Tomcat 5.0\conf\Catalina\localhost\injury.xml
<?xml version='1.0' encoding='utf-8'?>
<Context displayName="Injury" docBase="E:\Tomcat 5.0\webapps\injury" path="/injury" className="org.apache.catalina.core.StandardContext"
cachingAllowed="true" charsetMapperClass="org.apache.catalina .util.CharsetMapper" cookies="true" crossContext="false" debug="0"
mapperClass="org.apache.catalina.core.StandardContextMapper" useNaming="true" wrapperClass="org.apache.catalina.core.StandardWrapper" >
<Resource auth="Container" description="Resource reference to a factory for java.sql.Connection instances that may be used for talking to a particular database that is configured in the server.xml file." name="jdbc/injury" type="javax.sql.DataSource"/>
<ResourceLink global="jdbc/injury" name="injury" type="javax.sql.DataSource"/>
</Context>

Hi,
First of all, you can find alot of information about this in the forum about jsp's.
I think a good thing to do is not to put your context tag directly into the server.xml file.
What you should do is create a context.xml file with the context-tag in it, and put it in the META-INF directory of your .war file. Upon deployment to tomcat5 this file will be extracted from the war, copied to the conf\enginename\hostname directory, and it will be renamed to contextName.xml.
I think you are developing directly into the webapps directory, and I believe you should avoid that and use the deployment feature of the manager web-app or you should use the deployertool from you ide or standalone ant.
anyway, for starters try to remove the context tag from the server.xml file as described above, and check out the jsp / jdbc forums for simular problems and answers.
good luck

How to delete conext entries in JNDI tree after undeployment?

Hi,
When I deploy an EAR or JAR file with EJBs, they bind in the JNDI server.
When I undeploy the application the beans are no longer bound to the JNDI
tree, but the contexts they created remain.
For example, I deploy a bean that binds its home object to the following
entry in the JNDI:
myapp/mymodule/MyBean
When I undeploy MyBean, the context myapp/mymodule remain.
Is there an utility to remove these entries or do I have to develop my own
utility? I did not find anything in the administration console to do this.
This has been a source of some trouble, because sometimes I get error
messages when I want to redeploy the beans.
Thanks in advance,
Vegeta

Please don't cross post. see my reply in the ejb newsgroup.
Thanks,
Michael
Vegeta wrote:
Hi,
When I deploy an EAR or JAR file with EJBs, they bind in the JNDI server.
When I undeploy the application the beans are no longer bound to the JNDI
tree, but the contexts they created remain.
For example, I deploy a bean that binds its home object to the following
entry in the JNDI:
myapp/mymodule/MyBean
When I undeploy MyBean, the context myapp/mymodule remain.
Is there an utility to remove these entries or do I have to develop my own
utility? I did not find anything in the administration console to do this.
This has been a source of some trouble, because sometimes I get error
messages when I want to redeploy the beans.
Thanks in advance,
Vegeta--
Michael Young
Developer Relations Engineer
BEA Support

Error while using webmethod JMS provider with JNDI

Hi,
I am using webmethod JMS provider (not SAP JMS) with JNDI to connect to webmethod with XI. Central J2EE adapter engine is used and the comm chaneel is configured in with appropriate Provider JNDI Server address, initial context factory, Name of queue connection factory etc.
While activated the adapter short log shows: Adapter has not provided any status information about this channel"
In the detailed log following error message is displayed: "Obtained connection factory: null#"
#1.5 #001A4BAC31000052000001520000152200045090BF28DACA#1214482519514#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC31000052000001530000152200045090BF28DB65#1214482519514#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Looking up connection factory under name NAIP_XIQueueConnectionFactory#
#1.5 #001A4BAC31000052000001540000152200045090BF28E42E#1214482519516#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Obtained connection factory: null#
#1.5 #001A4BAC31000052000001550000152200045090BF28E4B3#1214482519516#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC31000052000001560000152200045090BF28E528#1214482519516#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC31000052000001570000152200045090BF28E5A9#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Info##Java###Sucessfully executed CF invocations for connection factory object: for profile: #2#<null>#ConnectionProfile of channel: CC_RCV_JMS_SAPJNDIon node: 3010950 having object id: e4413a5265a436459e271d5e0dd4859b#
#1.5 #001A4BAC31000052000001580000152200045090BF28E64E#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC31000052000001590000152200045090BF28E6CA#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC310000520000015A0000152200045090BF28E741#1214482519517#com.sap.aii.adapter.jms.core.common.StringUtils##com.sap.aii.adapter.jms.core.common.StringUtils.isBlank(String str)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC310000520000015B0000152200045090BF28E7C3#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Creating connection...#
#1.5 #001A4BAC310000520000015C0000152200045090BF28EB51#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Warning##Java###Catching #1#java.lang.NullPointerException
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection(ConnectorImpl.java:198)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:166)
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:186)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:151)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:235)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:154)
at com.sap.aii.adapter.jms.core.channel.AdapterImpl.doAddUpdateChannel(AdapterImpl.java:404)
at com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(AdapterImpl.java:376)
at com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl$1.run(ChannelLifecycleCallbackImpl.java:51)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
#1.5 #001A4BAC310000520000015D0000152200045090BF28EC6A#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Error##Plain###[[ChannelName:CC_RCV_JMS_SAPJNDI,ChannelId: e4413a5265a436459e271d5e0dd4859b]] Error adding/updating channel.#
#1.5 #001A4BAC310000520000015E0000152200045090BF28ECF8#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC310000520000015F0000152200045090BF28ED76#1214482519519#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl##com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl.channelAdded().run()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC3100005F000000660000152200045090BF65478A#1214482523474#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl.channelAdded(Channel channel)#AAAAAAAAA#108##n/a##002ee500437911dd99cf001a4bac3100#SAPEngine_Application_Thread[impl:3]_29##0#0#Path##Plain###Exiting method#
Please let me know anyone has come accross the problem or has idea how to solve it. Thanks.

Hi,
Ask ur basis admin to restart JMS adpater From Vis administrator and try again to activate the comm channel.
Hope this will solve ur problem and once again check connection fatcory and Queue name provided by Webmethod admin.
Regards,
Srini

Problems with the JNDI in Websphere App Server for Linux .

I'm working with EJBs and I have tested mine with WTE in VAJ. The problem is when I try to access them on a remote client. What I have done so far:
1:export the bean group to a Jar File
for the administration "Web page"
2:add an application by selecting the good Jar file
3:I set the JNDI name
4:save the new server configuration
5: restart the WAS server.
We have tryed to bind on the initial context (from
CNInitialContextFactory) and we had an Operation not supported exception. The lookup was giving a exception saying that it couldn't find the object. (We think that the CNInitialContextFactory is unknown on the server.
We are wondering if there could be some compatibility issue because the server uses java 1.3 and us 1.2.2 (VAJ 3.5.3). On the linux Server java 1.1.8 is also installed but WAS comes with its own java version. The path in the administration "web page" for the path for java is set. (the path from linux console is on java1.1.8 but that shouldn't matter right ? )
thanks for your help

Compatibility issues would not through an ObjectNotFound Exception. Maybe the problem is as simple as a class path issue. What object was not found- the Context class or the Object that you were attempting to bind to some name?

JNDI conflict for WTC in cluster env

I found this error when starting more than one managed server in clustered environment.
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start: You tried to bind
an object under the name tuxedo.services.TuxedoConnection in the JNDI tree. The
object you have bound from 161.215.254.40 is non clusterable and you have tried
to bind more than once from two or more servers. Such objects can only deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start: You tried to bind
an object under the name tuxedo.services.TuxedoConnection in the JNDI tree. The
object you have bound from 161.215.254.41 is non clusterable and you have tried
to bind more than once from two or more servers. Such objects can only deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start: You tried to bind
an object under the name tuxedo.services.TuxedoCorbaConnection in the JNDI tree.
The object you have bound from 161.215.254.40 is non clusterable and you have
tried to bind more than once from two or more servers. Such objects can only deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start: You tried to bind
an object under the name tuxedo.services.TuxedoCorbaConnection in the JNDI tree.
The object you have bound from 161.215.254.41 is non clusterable and you have
tried to bind more than once from two or more servers. Such objects can only deployed
from one server.>
Please help.

Hi Salim,
Salim Djaffar wrote:
"A. Honghsi Lo" <[email protected]> wrote:
Hi Salim,
Salim Djaffar wrote:
I have a stateless ejb using this context to get the same JNDI namefrom tuxedo
connection factory. This ejb is deployed as clustered. I deployed thisejb into
many managed servers in the cluster. In other word every managed serverdeploys
this ejb.
I also have the web server configured with clustered plugin, but Iguess it has
nothing to do with it.
Isn't the wtc_config.xml stanza "WlsClusterName" a little misleadingsince it
does not support cluster at all ?Yes, it is kind of misleading. It is not used in WTC and will be removed
from dtd
(and document) in the future.
Besides in the admin console, I configured the WTC startup target to"cluster".
Is there any advise to overcome this problem ?I can't think of a good way to overcome this problem. One thing you
can do is to
target WTC to a WLS in the cluster. One drawback is that you have only
one WTC in
the cluster.
Honghsi
Does it mean I have to use RMI/IIOP to do the lookup to one particular server
for WTC ?No. The RMI/IIOP lookup is specific for CORBA NS lookup. It won't help you at
all.
>
Will WTC be available for clustered in the future ?There will be some changes to WTC that will make it possible for you to deploy WTC
instance on every WL server in the cluster. There are some administration (and
configuration) restrictions associate with it if you want to be able to do load
balancing and fail over.
Hong-Hsi :-)
>
>
Thanks.
Please help.
"A. Honghsi Lo" <[email protected]> wrote:
Hi Salim,
The current version of WTC will have this problem. Because the connection
factory is bound
to the same name in JNDI tre. However, the first WTC booted in the
WLS
cluster should
still be available to use.
BTW, I am interested in knowing how you use WTC currently, and howyou
plan to use in the
future.
Honghsi
Salim Djaffar wrote:
I found this error when starting more than one managed server in
clustered
environment.
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start:
You
tried to bind
an object under the name tuxedo.services.TuxedoConnection in the
JNDI
tree. The
object you have bound from 161.215.254.40 is non clusterable and
you
have tried
to bind more than once from two or more servers. Such objects can
only
deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start:
You
tried to bind
an object under the name tuxedo.services.TuxedoConnection in the
JNDI
tree. The
object you have bound from 161.215.254.41 is non clusterable and
you
have tried
to bind more than once from two or more servers. Such objects can
only
deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start:
You
tried to bind
an object under the name tuxedo.services.TuxedoCorbaConnection in
the
JNDI tree.
The object you have bound from 161.215.254.40 is non clusterable
and
you have
tried to bind more than once from two or more servers. Such objectscan only deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start:
You
tried to bind
an object under the name tuxedo.services.TuxedoCorbaConnection in
the
JNDI tree.
The object you have bound from 161.215.254.41 is non clusterable
and
you have
tried to bind more than once from two or more servers. Such objectscan only deployed
from one server.>
Please help.

Problem in JNDI Lookup of Deployable Proxy from the logon par file

Hi,
I have customized the Logon par file and have a functionality to call a webservice when the Password Reset happens.
<b>from the ResetPassword.jsp , SAPMLogonLogic.java is getting called ,and there is a method called performResetPassword().</b>
I am calling a Deployable Proxy in that method by using the below code,
<b>Gateway objGateway=(SMSGateway)ctx.lookup("java:comp/env/MailProxy");
MailGatewayViDocument objSMSGatewayViDocument=(MailGatewayViDocument )objGateway.getLogicalPort("wsPort_Document",MailGatewayViDocument.class);
objMailGatewayViDocument.sendMail(...);</b>
I am getting the Exception,
<b>com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at java:comp, the whole lookup name is java:comp/env/MailProxy.</b>
I have deployed the Deployable Proxy in the J2EE Engine and add this API Jar as the External Library (Project >Properties>Java Build Path ---> Add External jars...Added the .jar file generated in the Proxy Project).
<b>Please let me know the possible solutions where i can call a deployable proxy inside the logon par file</b>.
Thanks and Regards,
Sekar

Hi,
I have fixed this error by changing the lookup as follows.
InitialContext ctx=new InitialContext();
Gateway objGateway=(Gateway)ctx.lookup("wsclients/proxies/sap.com/GatewayProxy/com.ms.sap..GatewayProxy");
Just open Visual Administrator and look for the path under wsclients for proper naming.
Thanks and Regards,
Sekar
Edited by: Sekar M on Jan 16, 2008 6:10 PM

Dynamic configuration of connection JNDI name in adapter service

I have a requirement to connect to multiple E-Business Suite instances and databases based on data in the message. I've created some adapter services, and it seems that the way each adapter service decides which instance to connect with is in the WSDL of that service:
<service name="RaiseEvent">
<port name="RaiseEvent_pt" binding="tns:RaiseEvent_binding">
<jca:address location="eis/Apps/VIS03_LNAX30B"/>
</port>
</service>
That snippet is from an Oracle Apps Adapter service, but there's similar code in the WSDL for database adapter services as well. The "eis/Apps/VIS03_LNAX30B" value is the name of the connection factory set up in my OC4J instance administration, specifying the database/EBS instance to use. Manually changing that value at design-time and redeploy works to connect to a different instance.
Is there any way to make that "jca:address location" attribute be a value that I pass into the adapter service, instead of hardcoding it into the WSDL?
Thanks,
Skip

I have tried to assign values to the OutBoundDBHeaderType to try invoke another JNDI, but does not seem to work.
The setup that I used was
Have 2 databases A and B.
Have the same procedure setup in both the databases.
Have 2 JNDIs setup to point to the databases A and B named as eis/DB/A and eis/DB/B.
Initially created a DB Adapter pointing to JNDI - A.
Created a variable of the OutboundDBHeaderType message type.
Tried to assign the dataSourceName as eis/DB/B in the BPEL process.
This doe not seem to change the JNDI, the calls continue going to A.

Passing Objects: ServletContext versus JNDI

I am currently developing a Web application that uses a variation of the (often recommended) model-view-controller architecture. Specifically, I have a single Front Controller Servlet that identifies what the request is for, and then delegates processing to an appropriate RequestHandler object. As implied by the name, the RequestHandler object has access to the original HttpServletRequest object.
In its init() method, the Front Controller Servlet prepares a pool of database connections. Each RequestHandler will obtain a connection through a DataSource object (in accordance with "best practices" for using the JDBC 2.0 Optional Extension). Then, the RequestHandler will retrieve data from the database, instantiate a Java Bean, and pass the Bean on to a corresponding JSP page for display.
Here is my dilemma: what is the best way to make the DataSource available to the RequestHandler objects?
Most sources suggest registering the DataSource with JNDI, but - as far as I can tell - this seems to require "administrative" access to the Web application server. For example, performing this action with Tomcat 4.0 requires modification of the server.xml file (as described at http://jakarta.apache.org/tomcat/tomcat-4.0-doc/jndi-resources-howto.html).
I would prefer to just stuff the DataSource into the ServletContext so that it is accessible throughout my Web application. (Then my DataSource would not be accessible, via JNDI, to other applications on the same server - such as in a shared hosting environment.) However, the problem is that my helper classes - the RequestHandlers - are not Servlets or JSPs (just regular classes), and therefore do not have access to a ServletConfig and, consequently, cannot access the ServletContext. Of course, I could stuff a reference to the ServletContext in every HttpServletRequest before passing it on to the helpers, but that doesn't seem "clean."
So, to summarize this lengthy inquiry,
(1) How can helper classes (i.e., not Servlets) access the Web application context (ServletContext)?
(2) What are the advantages/disadvantages to using JNDI to expose resources, versus simply storing objects in the ServletContext object, when trying to make resources available throughout a single Web application?
Thanks!
- Scott
[email protected]

Right you deal two problems:
1 The passing of servletcontext to helper classes. You can avoid this by creating a web application and storing it in a war file. You place all your servlets/jsp/helper classes in the war file according to a given structure. Each war file has a web.xml file. The web.xml file has all mappings between names in the program and the references to the objects. The web.xml can also have references between jndi names and references using the <env-entry> tag. There is only one servletcontext per web application. You can place all the information that both helper classes and servlets use e.g. jndi references into the web.xml. It is possible for the servletcontext and helper classes to refer to the same web.xml.So you have no need to exchange a servletContext reference around. See information on servletcontext interface:
http://java.sun.com/products/servlet/2.2/javadoc/javax/servlet/ServletContext.html
Second the question of isolating Datasources between applications. Could you not password protect the datasources so that access is only permissible if you have the correct password? Hence you can control the use of the datasource.
There are a number of tools to create a war application and to add jndi references to a war file.
You can use the graphical deployment tool from Sun's J2EE implementation.
All details for creating a war file are: http://java.sun.com/j2ee/tutorial/1_3-fcs/doc/WebComponents3.html
There are facilites to register environment variables like DataSources using the tool - look in the J2EE tutorial under configuring web clients.
Or you can use the packager tool found in Sun's J2EE application:
http://java.sun.com/j2ee/j2sdkee/techdocs/guides/ejb/html/Tools7.html
You can then port these war files onto tomcat to be hosted.
You will need to download the J2EE implementation.
For information on how to structure your web application and create a war file see: http://java.sun.com/j2ee/j2sdkee/techdocs/guides/ejb/html/Tools7.html
All information to create J2EE components:
http://developer.java.sun.com/developer/onlineTraining/J2EE/Intro/
Hope this helps.

"View JNDI tree" link not visible under monitoring tab of myserver?

Hi,
The link "View JNDI tree" as mentioned in chapter 18 of administration guide is
not visibile on my installation of 6.1 beta.
Is there some configuration setting that i need to do to make this link visible.
I am having problems with installation and running of my resource adapter. I wanted
to check whether the JNDI name is registered properly and there i ran into this
problem of no link available.
Regards
Manish

They moved this into a popup menu that you get to using a right click
in the tree view in the left frame. There are lots and lots of new
admin goodies available by right clicking on nodes of the tree. It
took me a while to discover this myself. :)
Ben
On 20 Jun 2001 10:29:12 -0800, Manish Verma <[email protected]> wrote:
>
The link "View JNDI tree" as mentioned in chapter 18 of
administration guide is not visibile on my installation of 6.1 beta.

Trouble with DeployManager and user administrator

i have the following error during the task of deployment of a WD app. The user administrator isn't blocked coz' i unblocked recently. but it continue show me that error. Any idea to solve my problem. Thanx in advance
this is the log:
Settings
SDM host : veccs1011
SDM port : 50218
URL to deploy : file:/C:/DOCUME1/Mariana/LOCALS1/Temp/temp34919MyWDproject.ear
Result
=> deployment aborted : file:/C:/DOCUME1/Mariana/LOCALS1/Temp/temp34919MyWDproject.ear
Aborted: development component 'MyWDproject'/'local'/'LOKAL'/'0.2006.05.09.15.43.06':
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [veccs1011] with user name: [Administrator] Check your login information. Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Access Denied.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
Deployment exception : The deployment of at least one item aborted

Hi
WHy dont you try changing the sdm password . have a llok at this forum thread for changing the sdm password
SDM password not working
Hope this helps , please mark points for helpful answers.
regards
rajeshkr

Change (or add) a password to Active Directory with Java and JNDI

I've create a new account in LDAP with attributs, It's ok. But a can't initialize the password, i've tryed some samples without result.
Maybe it's a SSL problem (i don't know why, i read it somewhere).
my code :
import java.util.*;
import java.io.*;
import java.net.*;
import javax.naming.Context;
import javax.naming.NameAlreadyBoundException;
import javax.naming.NamingException;
import javax.naming.directory.DirContext;
import javax.naming.directory.InitialDirContext;
import javax.naming.directory.BasicAttributes;
import javax.naming.directory.BasicAttribute;
import javax.naming.directory.ModificationItem;
public class addUser {
     private static final String UNICODE = "Unicode";
     private static final String UNICODE_PASSWORD = "unicodePwd";
     public addUser() {}
     private Hashtable env;
     private DirContext ctx;
     private void _initialize()
     String jndiURL = "ldap://DOMAINSRV:389/";
     String initialContextFactory = "com.sun.jndi.ldap.LdapCtxFactory";
     String authenticationMode = "simple";
     String contextReferral = "ignore";
     String principal = "[email protected]";
     String credentials = "oce";
     env = new Hashtable();
     env.put(Context.INITIAL_CONTEXT_FACTORY, initialContextFactory);
     env.put(Context.PROVIDER_URL, jndiURL);
     env.put(Context.SECURITY_AUTHENTICATION, authenticationMode);
     env.put(Context.SECURITY_PRINCIPAL, principal);
     env.put(Context.SECURITY_CREDENTIALS, credentials);
     env.put(Context.REFERRAL, contextReferral);
     public boolean createUser()
     try
          ctx = new InitialDirContext(env);
          ctx.destroySubcontext("cn=FBXX,cn=users,DC=gedeon,DC=fr");
          BasicAttributes attrs = new BasicAttributes();
          BasicAttribute ocs = new BasicAttribute("objectclass");
          ocs.add("user");
          attrs.put(ocs);
          BasicAttribute sa = new BasicAttribute("sAMAccountName", "FBXX");
          attrs.put(sa);
          BasicAttribute na = new BasicAttribute("name", "FRANCOIS BERTOUX");
          attrs.put(na);
          BasicAttribute sn = new BasicAttribute("sn", "BERT");
          attrs.put(sn);
          BasicAttribute up = new BasicAttribute("userPrincipalName", "[email protected]");
          attrs.put(up);
          BasicAttribute ua = new BasicAttribute("userAccountControl", "512");
          attrs.put(ua);
          BasicAttribute dn = new BasicAttribute("displayName", "FRA BERT");
          attrs.put(dn);
          BasicAttribute gn = new BasicAttribute("givenName", "FRA");
          attrs.put(gn);
          BasicAttribute des = new BasicAttribute("description", "CECI EST MON TEST");
          attrs.put(des);
          BasicAttribute cp = new BasicAttribute("codePage", "0");
          attrs.put(cp);
          BasicAttribute cc = new BasicAttribute("countryCode", "0");
          attrs.put(cc);
          BasicAttribute it = new BasicAttribute("instanceType", "4");
          attrs.put(it);
          ctx.createSubcontext("cn=FBXX,cn=users,DC=gedeon,DC=fr", attrs);
          changePassword ("cn=FBXX,cn=users,DC=gedeon,DC=fr", "TOTO" , "FBX");
          ctx.close();
     catch (NameAlreadyBoundException nex)
          System.out.println("User ID is already in use, please select a different user ID ...");
     catch (Exception ex)
          System.out.println("Failed to create user account... Please verify the user information...");
          ex.printStackTrace();
     return true;
public final void changePassword(
String argRDN,
String argOldPassword,
String argNewPassword)
throws NamingException
     ModificationItem modificationItem[] = new ModificationItem[2];
     try
          modificationItem[0] = new ModificationItem(DirContext.REMOVE_ATTRIBUTE,new BasicAttribute("unicodePwd",(byte[])this.encodePassword(argOldPassword)));
          modificationItem[1] = new ModificationItem(DirContext.ADD_ATTRIBUTE,new BasicAttribute("unicodePwd",(byte[])this.encodePassword(argNewPassword)));
     catch (UnsupportedEncodingException e1)
          System.out.println("changePassword(String argOldPassword, String argNewPassword)" +
          "Passwordchange failed: " + e1.toString());
          throw new RuntimeException(e1.toString());
     try
          ctx.modifyAttributes(argRDN, modificationItem);
     catch (NamingException e1)
          System.out.println(
          "changePassword(String argOldPassword, String argNewPassword)" +
          "Passwordchange failed : " + e1.toString());
          throw e1;
private byte[] encodePassword(String pass) throws UnsupportedEncodingException
     final String ATT_ENCODING = "Unicode";
     // Agree with MS's ATTRIBUTE_CONSTRAINT
     String pwd = "\"" + pass +"\"";
     byte bytes[] = pwd.getBytes(ATTENCODING);
     // strip unicode marker
     byte bytes[] = new byte [_bytes.length - 2];
     System.arraycopy(_bytes, 2, bytes, 0,_bytes.length - 2);
     return bytes;
     public static void main(String[] args)
          addUser testUser = new addUser();
          testUser._initialize();
          testUser.createUser();
And the result is :
changePassword(String argOldPassword, String argNewPassword)Passwordchange failed : javax.naming.OperationNotSupportedException: [LDAP: erro
r code 53 - 00002077: SvcErr: DSID-03190ADF, problem 5003 (WILL_NOT_PERFORM), data 0
]; remaining name 'cn=FBXX,cn=users,DC=gedeon,DC=fr'
Failed to create user account... Please verify the user information...
javax.naming.OperationNotSupportedException: [LDAP: error code 53 - 00002077: SvcErr: DSID-03190ADF, problem 5003 (WILL_NOT_PERFORM), data 0
]; remaining name 'cn=FBXX,cn=users,DC=gedeon,DC=fr'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:2804)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2677)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2483)
at com.sun.jndi.ldap.LdapCtx.c_modifyAttributes(LdapCtx.java:1285)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_modifyAttributes(ComponentDirContext.java:253)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:170)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:159)
at javax.naming.directory.InitialDirContext.modifyAttributes(InitialDirContext.java:144)
at addUser.changePassword(addUser.java:129)
at addUser.createUser(addUser.java:92)
at addUser.main(addUser.java:167)
And with "userPassword" no error but no change.
Please, help.
Thanks

Hello!
I have a new variant of the set password problem, and as i did not get any longer with a big running application i wrote a small standalone program to connect to an Active Directory server, and, hm, it works! I can login with a account which has administrator priveledges, i can set passwords, works fine, unless, and now it gets a little bit curious, unless i change the VM.
Everything works fine with a jdk 1.5.0_07, but if i switch over to the fine new 1.6.0_16, the login works still but the change of a password leads to a not so fine javax.naming.OperationNotSupportedException: [LDAP: error code 53 - 0000001F: SvcErr: DSID-031A0FC0, problem 5003 (WILL_NOT_PERFORM), data 0.
As i use the same cacerts file, i do not really understand what is failing here, anyone who has an idea?

TOMCAT 5.0 - JNDI Connection Fails

Hey guys,!
Just wanted to test a JNDI datasource I created through the Tomcat administrator with a simple code in a Servlet, here's the snipped code:
               System.out.println("Starting initial context");
               Context initCtx = new InitialContext();
               Context envCtx = (Context) initCtx.lookup("java:comp/env");
               DataSource ds = (DataSource)
               envCtx.lookup("jdbc/OFI4");
               Connection conn = ds.getConnection();
               //... use this connection to access the database ...
               conn.close();
The thing is, I'm getting an error that I've google for the las couple of days and have not found any helpful answers about it, the error message is:
org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null'
     at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:780)
     at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540)
     at test2.doGet(test2.java:68)
Caused by: java.sql.SQLException: No suitable driver
     at java.sql.DriverManager.getDriver(DriverManager.java:243)
     at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:773)
thank u people, any hel will be greatly appreciated.!
Regards,
Esteban

Hey guys....!
I figured out the way to make the JNDI connection work and I can tell you, it DOES work. Apparently, there are some troubles when creating the JNDI datasource by using the Tomcat Administration tool.
Follow this steps to sort this issue out:
1. Delete any of the datasources u've created by using the Tomcat Administrator make sure that no tags regarding these datasources remains in the server.xml file
2. Include the Resource tag in your application web.xml, as follows:
     <resource-ref>
     <description>DB Connection</description>
<res-ref-name>jdbc/OFICDB</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
     </resource-ref>
3. Create a xml file named exact as your application (i.e app1, testApp...) and place it at CATALINAHOME/conf/Catalina/localhost. The document content must be as the following (please note that you must change values such as database name, username, password). This files is associated to an application called testCR3
<?xml version='1.0' encoding='utf-8'?>
<Context path="/testCR3" docBase="testCR3" debug="5" reloadable="true" crossContext="true" workDir="work\Catalina\localhost\testCR3">>
<Logger className="org.apache.catalina.logger.FileLogger" prefix="localhost_textCR3_log." suffix=".txt" timestamp="true"/>
<Resource name="jdbc/OFICDB" auth="Container" type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/OFICDB">
<parameter>
<name>factory</name>
<value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
</parameter>
<parameter>
<name>driverClassName</name>
<value>oracle.jdbc.driver.OracleDriver</value>
</parameter>
<parameter>
<name>url</name>
<value>jdbc:oracle:thin:@12.145.12.134:1521:OFICDB</value>
</parameter>
<parameter>
<name>username</name>
<value>user1value>
</parameter>
<parameter>
<name>password</name>
<value>pwd1</value>
</parameter>
<parameter>
<name>maxActive</name>
<value>20</value>
</parameter>
<parameter>
<name>maxIdle</name>
<value>10</value>
</parameter>
<parameter>
<name>maxWait</name>
<value>-1</value>
</parameter>
</ResourceParams>
</Context>
If u have any additional troubles, do not hesitate to let me know.
Best regards,
E10
Message was edited by:
E10

LDAP Groups not displaying correctly in EP User Administration

I am having difficulty configuring EP to pull my Active Directory groups correctly. Currently, it is pulling a list of objects that have an objectClass of 'organizationalUnit', instead of 'group' which is how it is set-up inn Active Directory. I have tried setting the objectClass = group in the direct editing of the UM Configuration, but that does not seem to matter. Each time I change the configuration, I am re-starting the J2EE engine.
Any suggestions would be greatly appreciated
ume.acl.validate_cached_acls=FALSE
ume.admin.account_privacy=FALSE
ume.admin.addattrs=
ume.admin.allow_selfmanagement=TRUE
ume.admin.auto_password=TRUE
ume.admin.create.redirect=
ume.admin.debug_internal=FALSE
ume.admin.display.redirect=
ume.admin.modify.redirect=
ume.admin.nocache=FALSE
ume.admin.password.migration=false
ume.admin.phone_check=TRUE
ume.admin.search_maxhits=1000
ume.admin.search_maxhits_warninglevel=200
ume.admin.self.addattrs=
ume.admin.selfreg_company=FALSE
ume.admin.selfreg_guest=TRUE
ume.admin.selfreg_sus=FALSE
ume.admin.selfreg_sus.adapterid=SUS
ume.admin.selfreg_sus.adminrole=
ume.admin.selfreg_sus.deletecall=TRUE
ume.allow_nested_groups=TRUE
ume.allow_nested_roles=FALSE
ume.authenticationFactory=com.sap.security.core.logon.imp.SAPJ2EEAuthenticator
ume.cache.acl.default_caching_time=1800
ume.cache.acl.initial_cache_size=10000
ume.cache.acl.permissions.default_caching_time=3600
ume.cache.acl.permissions.initial_cache_size=100
ume.cache.default_cache=distributableCache
ume.cache.group.default_caching_time=3600
ume.cache.group.initial_cache_size=500
ume.cache.notification_time=0
ume.cache.principal.default_caching_time=3600
ume.cache.principal.initial_cache_size=500
ume.cache.role.default_caching_time=3600
ume.cache.role.initial_cache_size=500
ume.cache.user.default_caching_time=3600
ume.cache.user.initial_cache_size=500
ume.cache.user_account.default_caching_time=3600
ume.cache.user_account.initial_cache_size=500
ume.company_groups.description_template=Company
ume.company_groups.displayname_template= ()
ume.company_groups.enabled=FALSE
ume.company_groups.guestusercompany_enabled=TRUE
ume.company_groups.guestusercompany_name=Guest Users
ume.db.connection_pool.j2ee.is_unicode=FALSE
ume.db.connection_pool.j2ee.jta_transaction_support_enabled=FALSE
ume.db.connection_pool.j2ee.xatransactions_used=FALSE
ume.db.connection_pool_type=SAP/BC_UME
ume.db.or_search.max_arguments=50
ume.db.parent_search.max_arguments=300
ume.db.use_default_transaction_isolation=FALSE
ume.ldap.access.action_retrial=2
ume.ldap.access.auxiliary_naming_attribute.grup=
ume.ldap.access.auxiliary_naming_attribute.uacc=
ume.ldap.access.auxiliary_naming_attribute.user=
ume.ldap.access.auxiliary_objectclass.grup=
ume.ldap.access.auxiliary_objectclass.uacc=
ume.ldap.access.auxiliary_objectclass.user=
ume.ldap.access.base_path.grup=DC\=left,DC\=sand
ume.ldap.access.base_path.uacc=
ume.ldap.access.base_path.user=DC\=sand
ume.ldap.access.context_factory=com.sun.jndi.ldap.LdapCtxFactory
ume.ldap.access.creation_path.grup=
ume.ldap.access.creation_path.uacc=
ume.ldap.access.creation_path.user=
ume.ldap.access.dynamic_group_attribute=
ume.ldap.access.dynamic_groups=FALSE
ume.ldap.access.flat_group_hierachy=MIXED
ume.ldap.access.msads.control_attribute=userAccountControl
ume.ldap.access.msads.control_value=512
ume.ldap.access.msads.grouptype.attribute=grouptype
ume.ldap.access.msads.grouptype.value=4
ume.ldap.access.multidomain.enabled=FALSE
ume.ldap.access.naming_attribute.grup=ou
ume.ldap.access.naming_attribute.uacc=
ume.ldap.access.naming_attribute.user=
ume.ldap.access.objectclass.grup=group
ume.ldap.access.objectclass.uacc=
ume.ldap.access.objectclass.user=
ume.ldap.access.server_name=myserver
ume.ldap.access.server_port=3232
ume.ldap.access.server_type=
ume.ldap.access.size_limit=0
ume.ldap.access.ssl=FALSE
ume.ldap.access.ssl_socket_factory=com.sap.security.core.server.https.SecureConnectionFactory
ume.ldap.access.time_limit=0
ume.ldap.access.user=domain
svc_user
ume.ldap.access.user_as_account=TRUE
ume.ldap.blocked_accounts=Administrator,Guest
ume.ldap.blocked_groups=Administrators,Guests
ume.ldap.blocked_users=Administrator,Guest
ume.ldap.cache_lifetime=300
ume.ldap.cache_size=100
ume.ldap.connection_pool.connect_timeout=0
ume.ldap.connection_pool.max_connection_usage_time_check_interval=120000
ume.ldap.connection_pool.max_idle_connections=5
ume.ldap.connection_pool.max_idle_time=300000
ume.ldap.connection_pool.max_size=10
ume.ldap.connection_pool.max_wait_time=60000
ume.ldap.connection_pool.min_size=1
ume.ldap.connection_pool.monitor_level=0
ume.ldap.connection_pool.retrial=5
ume.ldap.connection_pool.retrial_interval=10000
ume.ldap.default_group_member=cn\=DUMMY_MEMBER_FOR_UME
ume.ldap.default_group_member.enabled=FALSE
ume.ldap.record_access=FALSE
ume.ldap.unique_grup_attribute=
ume.ldap.unique_uacc_attribute=samaccountname
ume.ldap.unique_user_attribute=samaccountname
ume.persistence.batch.page_size=25
ume.persistence.data_source_configuration=dataSourceConfiguration_ads_deep_readonly_db.xml
ume.persistence.pcd_roles_data_source_configuration=dataSourceConfiguration_PCDRoles.xml
ume.persistence.ume_roles_data_source_configuration=dataSourceConfiguration_UMERoles.xml
ume.principal.cache_group_hierarchy=TRUE
ume.principal.cache_indirect_parents=TRUE
ume.principal.cache_role_hierarchy=TRUE

Hi Doug,
I request your help on this. I am faced with a similar issue.
In my WinAD system, one user can be stored in multiple groups. However, the tree-structure is also present in my Windows AD hierarchy. Hence I am either using a Flat hierarchy or a Mixed hierarchy.
Changing the Datasource Configuration file to a Flat Readonly didn't solve the issue. The AD group path mentioned is correct and hence the group is visible in EP. However, I am not sure what should the UserPath be (As for now, I have kept it the same as the Group path).
Request you to please let me know what should the userpath be.
Rgds,
Sree

JNDI Administration

Similar Messages

Maybe you are looking for