NET "Directory Naming" OK now using Sun Directory Server?

Directory Server Enterprise Edition is much more light-weight than OID, and I'm wondering now it is under the Oracle umbrella, if it can be used instead of OID for Directory naming?
Can't find anything online. Can anyone provide information?
Thanks
Kirk

Thanks Salman. However I think any LDAP V3 server should work. I've seen people set it up with other Vendors LDAP servers. When directory naming was first introduced, there wasn't the restriction of OID only, Novell Directory Services was also supported. You can still use Microsoft Active Directory. I THINK it was limited to OID more for support purposes.
Introduced in 8.1.6
http://download.oracle.com/docs/cd/A81042_01/DOC/network.816/a76933/concepts.htm#1016403

Similar Messages

  • Error while authenticating BPEL WorklistApplication using sun java server

    Hi,
    I have got a situation where i need to use sun java server to authenticate users and groups who can log into the BPEL worklist application.
    This is what i have done.
    I went to middleware services,BPEL,orabpel and to hw services.
    There i changed the Security provider to thrid party LDAP Server.
    the LDAP connection is successfull.
    But when i m loggin onto the Worklist App it says Username invalid .Somehow it autheticates against systemjazndata.xml file .But it's not supposed to do so and validate against the ldap.
    Any help is highly appreciated..

    Hi,
    I have got a situation where i need to use sun java server to authenticate users and groups who can log into the BPEL worklist application.
    This is what i have done.
    I went to middleware services,BPEL,orabpel and to hw services.
    There i changed the Security provider to thrid party LDAP Server.
    the LDAP connection is successfull.
    But when i m loggin onto the Worklist App it says Username invalid .Somehow it autheticates against systemjazndata.xml file .But it's not supposed to do so and validate against the ldap.
    Any help is highly appreciated..

  • EJB not getting bound to JNDI name using Sun App Server upon deployment

    Hello,
    I've created a very simple "HelloWorld" EJB (2.1-style) and have successfully deployed it to my local application server (Sun Java System App Server Platform Edition 9.0). I now want to invoke the EJB (I have single stateless session bean that returns a string) using a simple remote client app (the client app is executing outside of the app server within its own JVM).
    From my client app I am able to create the InitialContext object, but I get error when trying to lookup my EJB's home object. My client looks as follows:
                   jndiProperties = new Properties();
                   jndiProperties.put("java.naming.factory.initial",
                        "com.sun.jndi.cosnaming.CNCtxFactory");
                   jndiProperties.put("java.naming.provider.url",
                        "iiop://localhost:3700"); // ORB listener is listening on port 3700...
                   context = new InitialContext(jndiProperties);
                   home = context.lookup("ejb/HelloWorldEJB"); // this line throws an exception (line 54)
                   ...The exception I receive is:
                   [java] 234  ERROR [main] net.blueslate.sample.ejb.helloworld.HelloWorldClient     - javax.namin
    g.NameNotFoundException [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.
    org/CosNaming/NamingContext/NotFound:1.0]
         [java]     at com.sun.jndi.cosnaming.ExceptionMapper.mapException(ExceptionMapper.java:44)
         [java]     at com.sun.jndi.cosnaming.CNCtx.callResolve(CNCtx.java:453)
         [java]     at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:492)
         [java]     at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:470)
         [java]     at javax.naming.InitialContext.lookup(InitialContext.java:351)
         [java]     at net.blueslate.sample.ejb.helloworld.HelloWorldClient.main(HelloWorldClient.java:5
    4)
         [java] Caused by: org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/Naming
    Context/NotFound:1.0
         [java]     at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:72
         [java]     at org.omg.CosNaming._NamingContextExtStub.resolve(_NamingContextExtStub.java:406)
         [java]     at com.sun.jndi.cosnaming.CNCtx.callResolve(CNCtx.java:440)
         [java]     ... 4 moreHere is my ejb-jar.xml:
    <?xml version="1.0" encoding="UTF-8"?>
    <ejb-jar
         xmlns="http://java.sun.com/xml/ns/j2ee"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"
         version="2.1">
         <enterprise-beans>
              <session>
                   <ejb-name>HelloWorldEJB</ejb-name>
                   <home>net.blueslate.sample.ejb.helloworld.HelloWorldRemoteHome</home>
                   <remote>net.blueslate.sample.ejb.helloworld.HelloWorldRemote</remote>
                   <local-home>net.blueslate.sample.ejb.helloworld.HelloWorldLocalHome</local-home>
                   <local>net.blueslate.sample.ejb.helloworld.HelloWorldLocal</local>
                   <ejb-class>net.blueslate.sample.ejb.helloworld.impl.HelloWorldImpl</ejb-class>
                   <session-type>Stateless</session-type>
                   <transaction-type>Container</transaction-type>
              </session>
         </enterprise-beans>
    </ejb-jar>Here is my sun-ejb-jar.xml:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 9.0 EJB 3.0//EN" "http://www.sun.com/software/appserver/dtds/sun-ejb-jar_3_0-0.dtd">
    <sun-ejb-jar>
         <enterprise-beans>
              <ejb>
                   <ejb-name>HelloWorldEJB</ejb-name>
                   <jndi-name>HelloWorldEJB</jndi-name>
              </ejb>
         </enterprise-beans>     
    </sun-ejb-jar>I believe the root cause is that my EJB is not bound to a name within the app server. If I browse the "JNDI tree" from the app server admin console, I can see there is a root element "ejb," but there is nothing underneath. I guess I just expected to find the name of my EJB, "HelloWorldEJB." I swear I could have read somewhere in the documentation for the app server that when you deploy an EJB, the name of the EJB as specified by the "<ejb-name>" element of the ejb-jar.xml deployment descriptor gets automatically bound within the naming server to its home object.
    At this point I would appreciate any insight anyone might have regarding this problem. I suspect there is something extra I need to do when deploying my EJB so that its name gets binded to its home object; I just don't have a clue at this point what that is.
    I should also mention that I have played with the parameter passed to 'context.lookup()' - I tried passing: "ejb/HelloWorldEJB", "HelloWorldEJB", etc - nothing seems to work. FWIW, if I just pass in "ejb", I don't receive an exception (I was glad to see this work since the JNDI tree-view from the app server admin console shows "ejb" as one of the root-elements within the naming-tree - this indicated to me I was on the right track in my diagnosis of the problem; i.e., it's probably not a connectivity or protocol issue)
    Thank you very much for your time and help.

    Nevermind folks - I got it to work. All my configuration was correct; I had other issues with the ejb-jar file that the verifier informed me of (my previous deployments were with the verifier turned-off).

  • How do I use Sun Web Server 7.0u1 reverse proxy to change public URLs?

    Some of our installations use the Sun Web Server 7.0 (update 1, usually)
    for hosting some of the public resource and reverse-proxying other parts
    of the URI namespace from other backend servers (content, application
    and other types of servers).
    So far every type of backend server served a unique part of the namespace
    and there was no collision of names, and the backend resources were
    published in a one-to-one manner. That is, a backend resource like, say,
    http://appserver:8080/content/page.html would be published in the internet
    as http://www.publicsite.com/content/page.html
    I was recently asked to research whether we can rename some parts of
    the public URI namespace, to publish some or all resources as, say,
    http://www.publicsite.com/data/page.html while using the same backend
    resources.
    Another quest, possibly related in solution, was to make a tidy url for the
    first page the user opens of the site. That is, in the current solution when
    a visitor types the url "www.publicsite.com" in his or her browser, our web
    server returns an HTTP-302 redirect to the actual first page URL, so the
    browser sends a second request (and changes the URL in its location bar).
    One customer said that it is not "tidy". They don't want the URL to change
    right upon first rendering the page. They want the root page to be rendered
    instantly i the first HTTP request.
    So far I found that I can't solve these problems. I believe these problems
    share a solution because it relies on ability to control the actual URI strings
    requested by Sun Web Server from backend servers.
    Some details follow, now:
    It seems that the reverse proxy (Service fn="service-passthrough") takes
    only the $uri value which was originally requested by the browser. I didn't
    yet manage to override this value while processing a request, not even if
    I "restart" a request. Turning the error log up to "finest" I see that even
    when making the "service-passthrough" operation, the Sun Web Server
    still remembers that the request was for "/test" (in my test case below);
    it does indeed ask the backend server for an URI "/test" and that fails.
    [04/Mar/2009:21:45:34] finest (25095) www.publicsite.com: for host xx.xx.xx.83
    trying to GET /content/MainPage.html while trying to GET /test, func_exec reports:
    fn="service-passthrough" rewrite-host="true" rewrite-location="true"
    servers="http://10.16.2.127:8080" Directive="Service" DaemonPool="2b1348"
    returned 0 (REQ_PROCEED)My obj.conf file currently has simple clauses like this:
    # this causes /content/* to be taken from another (backend) server
    NameTrans fn="assign-name" from="/content" name="content-test" nostat="/content"
    # this causes requests to site root to be HTTP-redirected to a certain page URI
    <If $uri =~ '^/$'>
        NameTrans fn="redirect"
            url="http://www.publicsite.com/content/MainPage.html"
    </If>
    <Object name="content-test">
    ### This maps http://public/content/* to http://10.16.2.127:8080/content/*
    ### Somehow the desired solution should instead map http://public/data/* to http://10.16.2.127:8080/content/*
        Service fn="service-passthrough" rewrite-host="true" rewrite-location="true" servers="http://10.16.2.127:8080"
        Service fn="set-variable" set-srvhdrs="host=www.publicsite.com:80"
    </Object>
    I have also tried "restart"ing the request like this:
        NameTrans fn="restart" uri="/data"or desperately trying to set the new request uri like this:
        Service fn="set-variable"  uri="/magnoliaPublic/Main.html"Thanks for any ideas (including a statement whether this can be done at all
    in some version of Sun Web Server 7.0 or its opensourced siblings) ;)
    //Jim

    Some of our installations use the Sun Web Server 7.0 (update 1, usually)please plan on installing the latest service pack - 7.0 Update 4. these updates addresses potentially critical bug fixes.
    I was recently asked to research whether we can rename some parts of
    the public URI namespace, to publish some or all resources as, say,
    http://www.publicsite.com/data/page.html while using the same backend
    resources.> now, if all the resources are under say /data, then how will you know which pages need to be sent to which back end resources. i guess, you probably meant to check for /data/page.html should go to <back-end>/content/page.html
    yes, you could do something like
    - edit your corresponding obj.conf (<hostname>-obj.conf or obj.conf depending on your configuration)
    <Object name=¨default¨>
    <If $uri = ¨/page/¨>
    #move this nametrans SAF (for map directive - which is for reverse proxy within <if> clause)
    NameTrans.. fn=map
    </If
    </Object>
    and you could do https-<hostname>/bin/reconfig (dynamic reconfiguration) to check out if this is what you wanted. also, you might want to move config/server.xml <log-level> to finest and do your configuration . this way, you would get enough information on what is going on within your server logs.
    finally,when you are satisfied, you might have to run the following command to make your manual change into admin config repository.
    <install-root>/bin/wadm pull-config user=admin config=<hostname> <hostname>
    <install-root>/bin/wadm deploy-config --user=admin <hostname>
    you might want to check out this for more info on how you could use <if> else condition to handle your requirement.
    http://docs.sun.com/app/docs/doc/820-6599/gdaer?a=view
    finally, you might want to refer to this doc - which explains on ws7 request processing overview. this should provide you with some pointers as to what these different directives mean
    http://docs.sun.com/app/docs/doc/820-6599/gbysz?a=view
    >
    One customer said that it is not "tidy". They don't want the URL to change
    right upon first rendering the page. They want the root page to be rendered
    instantly i the first HTTP request.
    please check out the rewrite / restart SAF. this should help you.
    http://docs.sun.com/app/docs/doc/820-6599/gdada?a=view
    pl. understand that - like with more web servers - ordering of directives is very important within obj.conf. so, you might want to make sure that you verify the obj.conf directive ordering is what you want it to do..
    It seems that the reverse proxy (Service fn="service-passthrough") takes
    only the $uri value which was originally requested by the browser. I didn't
    yet manage to override this value while processing a request, not even if
    I "restart" a request. Turning the error log up to "finest" I see that even
    when making the "service-passthrough" operation, the Sun Web Server
    still remembers that the request was for "/test" (in my test case below);
    it does indeed ask the backend server for an URI "/test" and that fails.
    now, you are in the totally wrong direction. web server 7 includes a highly integrated reverse proxy solution compared to 6.1. unlike 6.1, you don´t have to download a separate plugin . however, you will need to manually migrate your 6.1 based reverse proxy settings into 7.0. please check out this blog link on how to set up a reverse proxy
    http://blogs.sun.com/amit/entry/setting_up_a_reverse_proxy
    feel free to post to us if you need any futher help
    you are probably better off - starting fresh
    - install ws7u4
    - use gui or CLI to create a reverse proxy and map one on one - say content
    http://docs.sun.com/app/docs/doc/820-6601/create-reverse-proxy-1?a=view
    if you don´t plan on using ws7 integrated web container (ability to process jsp/servlet), then you could disable java support as well. this should reduce your server memory footprint
    <install-root>/bin/wadm disable-java user=admin config=<hostname>
    <install-root>/bin/wadm create-reverse-proxy user=admin uri-prefix=/content server=<http://your back end server/ config=<hostname> --vs=<hostname>
    <install-root>/bin/wadm deploy-config --user=admin <hostname>
    now, you can check out the regular express processing and <if> syntax from our docs and try it out within <https-<hostname>/config/<hostname>-obj.conf> file and restart the server. pl. note that once you disable java, ws7 admin server creates <vs>-obj.conf and you need to edit this file and not default obj.conf for your changes to be read by server.
    >
    I have also tried "restart"ing the request like this:
    NameTrans fn="restart" uri="/data"
    ordering is very important here... you need to do this some thing like
    <Object name=default>
    <If not $restarted>
    NameTrans fn=restart uri from=/¨ uri=/foo.
    </If>

  • Using Sun Web Server 6.1 from the IDE

    Using JSE 8 with Sun Web Server 6.1 set as the target container, I have a SUNWS61deployment.xml file created.
    That didn't exist in JSE 7. Is it WS 6.1 SP4 or SP5 -related ?
    I also have ws61-sun-web.xml with a simple <sun-web-app/> tag (empty deployment descriptor).
    What should this file contain? Is it a replacement for sun-web.xml?
    Do I still need sun-web.xml? Its DTD declaration sounds like Sun
    App Server 7 (http://www.sun.com/software/sunone/appserver/dtds/sun-web-app_2_3-1.dtd)
    So you have plans to make "Sun Resources" (pools, JNDI resources, ...) created in the IDE be registerable directly in the Web Server just like it's possible with the sun app server?
    How safe is it to use JSE 8 with an older Web Server Service Pack (say 6.1SP1)?

    SUNWS61deployment.xml is created bythe IDE to be used internally and not to be used by the developer. This file wouldn't be sent to webserver after deployment.
    The ws61-sun-web.xml is sun-web.xml only and yes it is same as it is in Appserver7 as the webcontainer for both Webserver6.1 and Appserver7 are same. After deployment to webserver, ws61-sun-web.xml is renamed to Webserver as sun-web.xml by the IDE. When opened the developer can edit in the XML editor.
    The reason for having it as ws61-sun-web.xml in IDE is to avoid the clash between sun-web.xml of Appserver8.1 which is J2EE1.4 based whereas Webserver6.1 Web container is J2EE1.3 based.
    It should be okay to use any service pack of Webserver6.1 with JSE8
    Hope this helps

  • Best way to use Sun Web Server connection pooling with Web Application?

    I have a number of applications that run Oracle and MySQL queries via Sun Web Server 6.1. I use the Web Server's built-in connection pooling, which works fairly well.
    As an interface with the connections I receive from the Web Server, I use a class, which (1) accepts the SQL and database name from a tool, (2) Opens the connection, runs the SQL, closes the connection, (3) puts the content of the result set into a Vector of Hashtables, (4) returns that Vector to the tool.
    Why do I use this Vector? That way, in my applications, I don't have to deal with opening connections (or getting them from the pool) and I don't have to worry about closing connections, because that's done automatically by the interface class.
    Is this a dumb approach to use? I'm a bit paranoid about open DB connections, because we have had a number of problems where connections would not be closed, go stale in oracle, and clog up the database resources.
    Can you suggest a better way to (1) smartly control opening and closing connections, and (2) enabling fast database access?
    Sorry, but given this Java/Sun Web Server double topic, I'm going to post the same message on the Web Server board.
    Any tips?
    dailysun
    P.S. For instance, in my tool, I call the interface class in this manner:
    Vector results_v = Database.getSelect("SELECT * FROM TEST","database1");
    getSelect uses the first string as the SQL and the second string as the jndi name of the Web server's database resource. getSelect does all the context stuff to get a connection from the pool, runs the SQL, puts the resultset into a Vector of Hastables (where each row is one Hashtable), and returns the Vector.

    I have a number of applications that run Oracle and MySQL queries via Sun Web Server 6.1. I use the Web Server's built-in connection pooling, which works fairly well.
    As an interface with the connections I receive from the Web Server, I use a class, which (1) accepts the SQL and database name from a tool, (2) Opens the connection, runs the SQL, closes the connection, (3) puts the content of the result set into a Vector of Hashtables, (4) returns that Vector to the tool.
    Why do I use this Vector? That way, in my applications, I don't have to deal with opening connections (or getting them from the pool) and I don't have to worry about closing connections, because that's done automatically by the interface class.
    Is this a dumb approach to use? I'm a bit paranoid about open DB connections, because we have had a number of problems where connections would not be closed, go stale in oracle, and clog up the database resources.
    Can you suggest a better way to (1) smartly control opening and closing connections, and (2) enabling fast database access?
    Sorry, but given this Java/Sun Web Server double topic, I'm going to post the same message on the Web Server board.
    Any tips?
    dailysun
    P.S. For instance, in my tool, I call the interface class in this manner:
    Vector results_v = Database.getSelect("SELECT * FROM TEST","database1");
    getSelect uses the first string as the SQL and the second string as the jndi name of the Web server's database resource. getSelect does all the context stuff to get a connection from the pool, runs the SQL, puts the resultset into a Vector of Hastables (where each row is one Hashtable), and returns the Vector.

  • Visibroker Bind Error When Using Sun Application Server

    I have a servlet that utilizes Visibroker 3.4 to access CORBA objects. My servlet works fine when using Tomcat; however, when using the Sun Application Server 8.2 PE, the same code does not work. After a few second delay (timout?) then the following exception is thrown.
    org.omg.CORBA.NO_IMPLEMENT:
    Could not locate the following object:
         repository id : IDL:A3Server:1.0
         object name : mobile5A3Server
    vmcid: 0x0 minor code: 0 completed: No
         com.visigenic.vbroker.orb.ORB.bind(ORB.java:1282)
         com.visigenic.vbroker.orb.ORB.bind(ORB.java:1361)
         com.visigenic.vbroker.orb.ORB.bind(ORB.java:1171)
         A3AppGen.A3ServerHelper.bind(A3ServerHelper.java:31)
         A3AppGen.A3ServerHelper.bind(A3ServerHelper.java:27)
         A3SessionConnection.connect(A3SessionConnection.java:74)
    Has anyone experienced this and better, found the solution. Interesting fact is that this only occurs when using the .bind(orb(), serverName); call.
    Another servlet packaged in the same .war file receives an IOR and is able to successfully access the CORBA object using orb().string_to_object(serverIOR); with both Tomcat and Sun Application Server.
    Thanks for the help.

    Please list the content of 'asadminenv.conf'
    Alternatively, you could just manually create the instance as follows:
    asadmin.bat create-domain user admin adminport 4849 domaindir C:\Sun\AppServer\domains instanceport 8080 domain1

  • Sun Directory Server Password Policy Problems

    Hi,
    I am using Sun Directory Server and Sun AM (2005Q1).
    We are using SUN DS to configure the password policy to expire user passwords after 30 days.
    Also, the warning has been set to "one day before expiry". However, when the warning IS displayed to the user and the user changes his/her password on display of the warning, even though the user's password expiration timestamp attribute contains a new timestamp (which is 30 days hence the date of change), on next login user is AGAIN thrown the warning that his/her password will expire in "HH hours: MM mins".
    I do not understand what needs to be done to fix this. Any help would be appreciated.

    How is the user authenticated ? Through Access Manager or directly to the Directory Server ?
    Access Manager can be configured to handle Password expiration, and so can Directory Server. I would advise you to check which system is actually throwing the warning.
    Regards,
    Ludovic

  • Under Sun Directory Server, is phpLDAPadmin needed?

    We use Sun Directory Server 6.3. Do we need phpLDAPadmin? What are the advantages and disadvantages to use?
    Thank you in advance!

    As far as I know, PLA is just a web app that provides you an LDAP client interface, as well as Apache Directory Studio.
    You do not needed any LDAP client interface to administer Sun Directory Server 6.3, in theory (and if you like) you have all the available options via command line (dsadm, dsconf, ldapsearch/ldapmodify), but of course a GUI is something that may ease your tasks.
    Personally I can't see any specific advantages or disadvantages in using a given interface instead of another: it depends on which one fits better to your needs.
    regards,
    marco

  • Sun Directory 5.1 Solaris download

    Hi,
    We have a environment where one application still uses Sun Directory 5.1
    One of our nodes recently got corrupted and we want to reinstall sun directory 5.1 on it.
    I am not able to locate the solaris installable for this. Only 6 and above is available on edelivery.oracle.com
    Would anyone be able to point me to the correct link where I can download the solaris version?
    Regards,
    Anand.

    Hi Anand,
    In order to get access to very old versions you need to go through Oracle Support and open a Service Request.
    Hope this helps.
    Best regards
    Etienne

  • Different behavior using JSC and Sun App server 8.2 - why?

    I have developed a JSF application using Java Studio Creator 2.
    JSC2 uses Sun App Server 8.2 as the development application server.
    I also have Sun App Server 8.2 on a server that is used for deployment.
    When I run an application within the IDE, I get a set of behavior that I expect to see, but not when deployewd to the server.
    In particular, in one case, a grid created within a session bean is redrawn when running in the IDE but not when deployed.
    In another case, I attempt to read the value of the grid text field.
    In the IDE, I get a properly set 'submittedValue' property, but in the deployed environment, it is null.
    Why am I seeing differences in behavior between the two environments?
    How can I get the deployed version to work tge same as in the development enviroment.

    I am sorry but I don't understand. Which path specifically do you mean?
    dear mr/mises
    you have to change your path with net beans with8.2
    you will be solving your problems

  • Failure to Start JMS Service in Sun Java Server

    Hi,
    I'm using Sun Java Server on Unix platform with Java 5.
    When I start the Sun server I find the JMS service in in unable to start.
    Please find below the Error Log Trace I observe:
    [#|2005-11-18T04:19:13.320-0600|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms
    |_ThreadID=10;|JMS5037: Check permissions of MQ instance directory
    /home/jai/cts141/SUNWappserver/imq/var/instances|#]
    [#|2005-11-18T04:19:13.321-0600|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms
    |_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service
    broker instance imqbroker. Please refer to the JMS provider documentation for the exact
    location of this log file.|#]
    [#|2005-11-18T04:19:13.322-0600|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.cor
    e|_ThreadID=10;|CORE5071: An error occured during initialization
    com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection
    creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused
    (errno:4127)
            at
    com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:
    415)
            at com.sun.enterprise.server.PEMain.run(PEMain.java:224)
            at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:585)
            at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
    Caused by: com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection
    creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused
    (errno:4127)
            at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSConnectException(ExceptionHandler.ja
    va:233)    at 
    com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleConnectException(ExceptionHandler.ja
    va:180)
            at
    com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:172)
            at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:97)
            at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:50)
            at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandl
    er.java:53)
            at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
            at
    com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:271)
            at
    com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:107)
            at
    com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:92)
            at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:562)
            at
    com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1102)
            at
    com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1741)
            at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:588)
            at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:274)
            at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
            at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
            at om.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
            at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:734)
            at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:32
          at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:384)
            ... 7 more
    Caused by: java.net.ConnectException: Connection refused (errno:4127)
            at java.net.PlainSocketImpl.socketConnect(Native Method)
            at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
            at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
            at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
            at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:364)
            at java.net.Socket.connect(Socket.java:507)
            at java.net.Socket.connect(Socket.java:457)
            at java.net.Socket.<init>(Socket.java:365)
            at java.net.Socket.<init>(Socket.java:178)
            at
    com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:152)
            ... 25 more
    |#]
    [#|2005-11-18T04:19:13.327-0600|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.cor
    e|_ThreadID=10;|Server Startup failed. Exiting...|#][
    * The JMS service is unable to start on the port 7676 which I find free .
    * The directory /home/jai/cts141/SUNWappserver/imq/var/instances also holds all permissions to all users
    * The log for MQ startup gets created if I explicitly run the script imqbrokerd located at /home/jai/cts141/SUNWappserver/imq/bin.
    But this script does not get executede when the server is started .
    But all these JMS startup happens fine when I start the sever setup with
    previous version of Java (Java 1.4.2).
    Please clarify the same.
    Thanks in Advance,
    Jay

    I guess if you don't start the managed servers with NodeManager they do come up?
    Not sure if this is related, but did you take a look at MOS note 1336100.1? It basically says there was a failure during configuration of NodeManager; it is not entirely related to forms but to FMW 11.1.1.5 which is somehow the version number of forms 11.1.2. A cause of it is that NodeManager isn't using the correct script when starting a managed server; this also sounds a little bit like your problem...
    Regarding the OutOfMemory exception you might look at note 1312573.1; it is related to running WLS as windows services (without NodeManager); but it might as well apply to running the Servers with NodeManager.
    It might be a shot in the dark, but it might be worth a try.
    In any case when running into (forms related) troubles with weblogic I found very little specific forms related informations on weblogic; this is probably due to the fact that forms doesn't make much use of weblogic at all (all in all most of the work is done by the good old fashioned C- forms runitmes); but the generic notes on weblogic often did the trick.
    cheers

  • Advantaged of SUN LDAP Server over OID

    Hi all,
    Can any body tell me the use of SUN LDAP Server instead of Oracle Directory Server......What all advantages we have to use SUN LDAP Server instead of OID....
    Regards
    Kumar

    If no one tells you can assume there is no advantage, simple.

  • How to properly terminate SSL at Sun Proxy Server?

    Hi:
    Client is using Sun Proxy Server (4.0.x) as a reverse proxy to a host with Sun Application Server Enterprise Edition with Access Manager / Portal / Identity Manager deployed as J2EE apps.
    For access through proxy with http, it is properly seen by AM as an http URL. But for access through proxy with https, it is seen by AM as an https URL.
    My suspicion is that the Proxy Server is not properly configured to terminate SSL at the proxy. However, I do not have enough experience with Sun Proxy Server to confirm. Below is the configuration file.
    Any ideas? My novice theory is that the multiple mapping rules are causing some sort of conflict. Perhaps the connect rule for port 443? All of the examples I have been able to find for mapping rules are from http to http or a local file, NOT https to http and vice-versa. Are these rules correct?
    Any help is greatly appreciated!
    Thanks,
    Gerald
    --- (start: obj.conf) --
    # You can edit this file, but comments and formatting changes
    # might be lost when the admin server makes changes.
    Init fn="flex-init" access="$accesslog" format.access="%Ses->client.ip% - %Req->vars.auth-user% [%SYSDATE%] \"%Req->reqpb.clf-request%\" %Req->srvhdrs.clf-status% %Req->vars.p2c-cl% %Req->vars.remote-status% %Req->vars.r2p-cl% %Req->headers.content-length% %Req->vars.p2r-cl% %Req->vars.c2p-hl% %Req->vars.p2c-hl% %Req->vars.p2r-hl% %Req->vars.r2p-hl% %Req->vars.xfer-time%"
    Init fn="init-proxy" timeout="300" timeout-2="15"
    <Object name="default">
    AuthTrans fn="match-browser" browser=".*MSIE.*" ssl-unclean-shutdown="true"
    NameTrans fn="reverse-map" from="http://pcmdv2.client.net:5111/idm" to="https://offlinebusiness.client.net:25002/idm" rewrite-location="true" rewrite-content-location="true"
    NameTrans fn="reverse-map" from="http://localhost:35007/deas" to="https://offlinebusiness.client.net:25002/deas" rewrite-location="true" rewrite-content-location="true"
    NameTrans fn="reverse-map" from="http://pcmdv2.client.net:5111" to="https://offlinebusiness.client.net:25002" rewrite-location="true" rewrite-content-location="true"
    NameTrans fn="map" from="https://offlinebusiness.client.net:25002" to="http://pcmdv2.client.net:5111" rewrite-host="true"
    NameTrans fn="map" from="https://offlinebusiness.client.net:25002/deas" to="http://localhost:35007/deas" rewrite-host="true"
    NameTrans fn="map" from="https://offlinebusiness.client.net:25002/idm" to="http://pcmdv2.client.net:5111/idm" rewrite-host="true"
    NameTrans fn="map" from="/deas" to="http://localhost:35007/deas" rewrite-host="true"
    NameTrans fn="map" from="/idm" to="http://pcmdv2.client.net:5111/idm" rewrite-host="true"
    NameTrans fn="map" from="/" to="http://pcmdv2.client.net:5111" rewrite-host="true"
    PathCheck fn="url-check"
    ObjectType fn="forward-ip" hdr="Proxy-ip"
    Service fn="deny-service"
    AddLog fn="flex-log" name="access"
    </Object>
    <Object name="file">
    PathCheck fn="unix-uri-clean"
    PathCheck fn="find-index" index-names="index.html"
    ObjectType fn="type-by-extension"
    ObjectType fn="force-type" type="text/plain"
    Service fn="send-file"
    </Object>
    <Object ppath="ftp://.*">
    ObjectType fn="cache-enable" query-maxlen="10" log-report="off"
    ObjectType fn="cache-setting" lm-factor="0.10" max-uncheck="7200"
    Service fn="proxy-retrieve"
    </Object>
    <Object ppath="http://.*">
    ObjectType fn="cache-enable" query-maxlen="10" log-report="off"
    ObjectType fn="cache-setting" lm-factor="0.10" max-uncheck="7200"
    Service fn="proxy-retrieve" method="*"
    </Object>
    <Object ppath="https://.*">
    Service fn="proxy-retrieve"
    </Object>
    <Object ppath="gopher://.*">
    ObjectType fn="cache-enable" query-maxlen="10" log-report="off"
    ObjectType fn="cache-setting" lm-factor="0.10" max-uncheck="7200"
    Service fn="proxy-retrieve"
    </Object>
    <Object ppath="connect://.*:443">
    Service fn="connect" method="CONNECT"
    </Object>
    <Object ppath="connect://.*:563">
    Service fn="connect" method="CONNECT"
    </Object>
    --- (end: obj.conf) --

    Isn't there two overlapping rules? Perhaps that confuses the SWPS?
    NameTrans fn="map" from="https://offlinebusiness.client.net:25002" to="http://pcmdv2.client.net:5111" rewrite-host="true"
    NameTrans fn="reverse-map" from="http://pcmdv2.client.net:5111" to="https://offlinebusiness.client.net:25002" rewrite-location="true" rewrite-content-location="true"
    and
    NameTrans fn="map" from="https://offlinebusiness.client.net:25002/idm" to="http://pcmdv2.client.net:5111/idm" rewrite-host="true"
    NameTrans fn="reverse-map" from="http://pcmdv2.client.net:5111/idm" to="https://offlinebusiness.client.net:25002/idm" rewrite-location="true" rewrite-content-location="true"
    covers the same URLs

  • Integrating Sun App Server with WebSphere MQ

    Hi,
    I am using Sun App server V8.1 . I also have a websphere MQ v5.3 installed in my system. I want to integrate this MQ with the App server.
    I created a queueManager and a Queue in MQ and using the JMSAdmin console of the Mq, i created jndi lookup resources using INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
    In the application server side, i created a Resource adapter using the command:
    create-resource-adapter-config --property SupportsXA=true:ProviderIntegrationMode=jndi:RMPolicy=OnePerPhysicalConnection:JndiProperties=java.naming.factory.url.pkgs\\=com.ibm.mq.jms.naming,java.naming.factory.initial\\=com.sun.jndi.fscontext.RefFSContextFactory,java.naming.provider.url\\=file\\:D\\:\\MQ:LogLevel=finest mqra
    Then i deployed this resource adaptor using the command :
    deploy name mqra target server "D:\Sun\AppServer\lib\addons\resourceadapters\genericjmsra\genericra.rar"
    Using this resource adapter i created a connection pool, connector resource and an admin object using the commands
    create-connector-connection-pool raname mqra connectiondefinition javax.jms.QueueConnectionFactory transactionsupport  XATransaction property ConnectionFactoryJndiName=MQQCF mymqpool
    create-connector-resource --poolname mymqpool jms/MyMqQCF
    create-admin-object raname mqra restype javax.jms.Queue --property DestinationJndiName=RTQueue jms/MyMqQueue
    After that, i wrote a java code to lookup these resources and put a message into the queue.
    This is the snippet of my java code
    InitialContext ic = new InitialContext();
    QueueConnectionFactory cnxFact = (QueueConnectionFactory)ic.lookup("jms/MyMqQCF");
    Queue qu = (Queue)ic.lookup("jms/MyMqQueue");
    try {               
    QueueConnection qConn = cnxFact.createQueueConnection();
    QueueSession qSess = qConn.createQueueSession(false,Session.AUTO_ACKNOWLEDGE);
    QueueSender qSend = qSess.createSender(qu);
    TextMessage msg = qSess.createTextMessage();
    msg.setText("1");
    qSend.send(msg);
    qConn.close();
    I am getting an exception in the line, QueueConnection qConn = cnxFact.createQueueConnection();
    here is the stack trace
    java.lang.ClassCastException: com.ibm.mq.jms.MQQueueConnectionFactory
    at com.sun.genericra.outbound.ManagedQueueConnectionFactory.createXAConnection(ManagedQueueConnectionFactory.java:45)
    at com.sun.genericra.outbound.AbstractManagedConnectionFactory.createPhysicalConnection(AbstractManagedConnectionFactory.java:127)
    at com.sun.genericra.outbound.AbstractManagedConnectionFactory.createManagedConnection(AbstractManagedConnectionFactory.java:111)
    at com.sun.enterprise.resource.ConnectorAllocator.createResource(ConnectorAllocator.java:90)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.getUnenlistedResource(IASNonSharedResourcePool.java:437)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.internalGetResource(IASNonSharedResourcePool.java:355)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.getResource(IASNonSharedResourcePool.java:250)
    at com.sun.enterprise.resource.PoolManagerImpl.getResourceFromPool(PoolManagerImpl.java:213)
    at com.sun.enterprise.resource.PoolManagerImpl.getResource(PoolManagerImpl.java:174)
    at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:286)
    at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:145)
    at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:121)
    at com.sun.genericra.outbound.ConnectionFactory.createConnection(ConnectionFactory.java:69)
    at com.sun.genericra.outbound.ConnectionFactory.createQueueConnection(ConnectionFactory.java:101)
    Can anybody help???

    bump
    update:
    So to avoid this problem I added spring.jar to the server classpath. that got rid of this message but then it started complaining that its missing struts2 core jar..i added that in server classpath as well...I did same for 4 other files and in the end it said 'bean for xwork has already been initialized' (because all these jars are in the application as well).
    So I am stuck. if I add all jars to server classpath..it says beans have already been initialized. If I take out the jars from server classpath then it says that stuff is missing (eg. contextLoader.properties missing - orig post)
    again, all this goes away when I restart the server..so i am just trying to avoid having to restart server every code change.

Maybe you are looking for