Weblogic question

How do we configure WLS 8.1 or 9.2 to look for the license files (license.bea) in an alternate location? The platform is Solaris.
e.g. I usually install WLS in /opt/bea and this is also where the license.bea file resides. I would like to configure WLS to look for the license in /etc/license.bea.
Thanks and regards,
Vishal

Vishal,
I do not know of any way to change where Weblogic looks for the file. I
believe it will always look in your BEA_HOME directory.
However, on a Linux/Unix system you can always use symlinks to
accomplish what you want.
ie:
#$ ln -s /opt/bea/license.bea /etc/license.bea
Regards,
Ilan
Vishal Gupta wrote:
How do we configure WLS 8.1 or 9.2 to look for the license files (license.bea) in an alternate location? The platform is Solaris.
e.g. I usually install WLS in /opt/bea and this is also where the license.bea file resides. I would like to configure WLS to look for the license in /etc/license.bea.
Thanks and regards,
Vishal

Similar Messages

  • Answer to Weblog Question for Sumith Rajagopalan

    Sumith Rajagopalan I hope that you read the BSP question forum as well as the weblogs.  You posted a question in the discussion forum on the following weblog:
    /people/thomas.jung3/blog/2004/08/09/bsp-download-to-excel-in-unicode-format
    For some reason I can no longer post comments to this or any other weblog right now.  I assume there is problem on the SDN side.  Therefore I thought I would post the answer here until the problem is resolved. 
    It appears to be a simple typo in your code. You had:
    response->set_header_field(
    name = 'content_disposition'
    value = 'attachment;filename=webforms.xls' ).
    The correct code is:
      response->set_header_field(
          name = 'content-disposition'
          value = 'attachment;
          filename=webforms.xls' ).
    Please note that is is a dash not an underscore in the content-disposition header field name.

    Yes Thomas, it was the typo.  Thanks.  It is working perfectly now.

  • Weblogic & JAAS

    Hi all,
    I am using Oracle Weblogic 10.3 and I want to use JAAS authentication. As a start, I checked the sample code given at
    SAMPLES_HOME\server\examples\src\examples\security\jaas.
    I have few questions:
    1. In SampleClient.java:
    -We're first retrieving the authenticated subject :
    Subject subject = loginContext.getSubject();
    -Then , we perform SampleAction
    -Then we call the weblogic.security.Security.Security.runAs(subject, sampleAction);
    I noticed that SampleAction and SampleClient are dependent on Weblogic. In SampleClient, we're calling the weblogic runAS method.
    Theoretically, JAAS is independent of the application server. Is there a way to implement JAAS with Weblogic in a way that it is independent of Weblogic?
    I have to run my application on multiple AS (Oracle weblogic 10.3, JBoss). I want to check if it is possible to write the code once for JAAS (e.g: one LoginModule) for both servers ?
    2. In the sample given, they are using the UsernamePasswordLoginModule which is located in Weblogic.jar. And in the documentation it is said, that if you want to write your own LoginModule, you must have it call the weblogic.security.auth.Authenticate.authenticate() method to perform the login.
    Can you explain please why?
    In JAAS, it is said that my application-layer code deals primarily with a LoginContext. Underneath that LoginContext is a set of one or more dynamically configured LoginModules, which handle the actual authentication using the appropriate security infrastructure (JndiLoginModule, RdbmsLoginModule).
    In fact, I need to be able to create the JAAS files once for all application servers (e.g: Weblogic, Jboss). As I noticed from the research I have done, this is not possible now because we must call the Weblogic authenticate in the login module.
    This said, when using JAAS with Weblogic, I must write JAAS classes for Weblogic; and when using JAAS with JBoss, I must write JAAS classes for JBOSS.
    Is this true? Is there another method to implement JAAS in a way that it will be totally independent of the Application Server?
    Thank you in advance.

    Try asking your weblogic question in the... weblogic forums!
    https://forums.oracle.com/forums/category.jspa?categoryID=193

  • CC&B LoginModule for Weblogic Change of Password

    Hi All,
    I realise this is more of a Weblogic question, though I'm specifically after a working example of LoginModule that can be used within CC&B on Weblogic to:
    a) Force users to change their password if their password is reset;
    b) Force users to change their password if their password is expired (for example after 30 days);
    b) Plus preferably also allow users to change their password on demand.
    Can anyone point me at some examples of this (preferably also highlighting what needs to be set-up within Weblogic from an admin perspective to allow password expiry)?
    Note - Kerberos Authentication is not currently an option, hence I need just basic JSP login modules.
    Cheers,
    Matt

    Hi All ..
    Thanks for reply .
    I m new in this company. but once the password was changed by ex-DBA before my arrival in this company and that too created problems in RAC. This is what my PM says.
    I think some where this password is given at the time of RAC installation .
    What were the problems ? have gone with ex-DBA.
    I have to look into it.
    Can you figure out the possible problems ?
    plz help.
    Regards,
    Edited by: Cool_DBA on Nov 21, 2008 1:38 AM

  • How to start weblogic server with non system user

    I want to start wls6.1 as an nt service with different user name other than
    system.
    Thanks
    Madhu

    I have installed weblogic server as an nt service. In install Nt service
    cmd, if I make any change in the script, I have to uninstall and install it
    again. I do not know where to specify the weblogic.management.username =(Non
    system user)
    I have created a user name in NT server and added them to Administrator
    group. I have also modified in file realm propertes i.e to boot and shutdown
    the non system user.
    I have to start weblogic server as a non system user.
    Thanks
    Madhu
    I think I replied to some of the questions when I found out the answers.
    Only thing I did was hit reply, instead of reply group. Might it went to
    persons e-mail. That might be the reason, the answers I posted is not found
    in the newsgroup
    Thanks
    freelance_code_inspector <[email protected]> wrote in message
    news:[email protected]..
    "m holur" <[email protected]> wrote in message
    news:<3bfbafce$[email protected]>...
    I want to start wls6.1 as an nt service with different user name otherthan
    system.Madhu,
    Specify weblogic.management.username={Non system user} in your -D
    option. BTW, just curious, have observed that u have been posting a
    lot of weblogic questions lately, did u find out the answers? If so, u
    should share it back to this community.
    Regards
    drit
    Freelance Java Developer/Code Inspector
    http://www.geocities.com/doc_i_t/CodeInspectionService.html

  • Got weblogic.socket.MaxMessageSizeExceededException

    We use web start to call a session to query database.
    We also add the parameter -Dweblogic.MaxMessageSize=200000000 in jnlp.
    The following are the jnlp.
    <?xml version="1.0" encoding="utf-8"?>
    <jnlp spec="1.0+" codebase="http://localhost:7011/testws/" href="testws.jnlp">
         <information>
              <title>Jnlp Testing</title>
              <vendor>test</vendor>
              <homepage href="http://localhost:7011/" />
              <description>Testing</description>
         </information>
         <resources>
              <j2se version="1.6+" java-vm-args="-Xmx1G -Dweblogic.MaxMessageSize=value"/>
              <jar href="TestJnlp.jar" />
         </resources>
         <application-desc main-class="com.test.Application1" />
    </jnlp>
    However, we still got weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '10000080' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3'.
    Where should we add '-Dweblogic.MaxMessageSize'?
    Thanks.

    Sounds like you need to set it on the server. It's a WebLogic question in any case, nothing to do with (i) JNLP (ii) this forum or (iii) this site. Locking.

  • Embedded LDAP password issue in Weblogic 7

    Is this normal? Seems odd to me...
    After installing weblogic 7 using the wizard and giving a new password other than "weblogic" for the "weblogic" user, and after using boot.properties to get an encrypted version, the embedded LDAP servers for both admin and managed servers do not seem to have the new password.
    If I try to use JNDI to get a JMX MBean Home on the managed server, I get an exception saying I have the wrong password for "weblogic".
    After using the admin console to change the password to the value it supposedly already has, the embedded LDAP servers for both the admin and consumer have a new (encrypted but presumably correct) password but the JNDI call still fails.
    After undeploying and redeploying the relevant web application the JNDI call succeeds.
    Killing and restarting the admin and managed servers does not seem to be relevant. Setting the read replica on startup flag doesn't seem to help. This is mostly on testing on the petstore example. This may be relevant since at some point BEA changed the user/password for it to "weblogic/weblogic"
    QUESTIONS:
    Does anybody understand why this is happening?
    Any ideas for fixes that avoid bouncing and redeployment?
    ---Paul O

    Never mind...
    I think I have solved this with the help of an LDAP browser and a custom JNDI/JMX password tester.
    One problem that threw me off was that changes that were thought to be happening in testing were not really "taking"
    due to precompilation of JSPs. I had thought that redeploying made the correct password "take" but actually it was helping changes in the code to take effect. Another problem that I believe but have yet to verify contributed to the confusion and a related failure to log is that once a user is rejected repeatedly, Weblogic locks the account for a half hour by default.
    The bottom line is it really pays to use instruments that tell you what the actual state of affairs is as conjectures are often wrong for unexpected reasons.
    ---Paul O
    Paul O'Rorke wrote:
    Is this normal? Seems odd to me...
    After installing weblogic 7 using the wizard and giving a new password
    other than "weblogic" for the "weblogic" user, and after using
    boot.properties to get an encrypted version, the embedded LDAP servers
    for both admin and managed servers do not seem to have the new password.
    If I try to use JNDI to get a JMX MBean Home on the managed server, I
    get an exception saying I have the wrong password for "weblogic".
    After using the admin console to change the password to the value it
    supposedly already has, the embedded LDAP servers for both the admin and
    consumer have a new (encrypted but presumably correct) password but the
    JNDI call still fails.
    After undeploying and redeploying the relevant web application the JNDI
    call succeeds.
    Killing and restarting the admin and managed servers does not seem to be
    relevant. Setting the read replica on startup flag doesn't seem to
    help. This is mostly on testing on the petstore example. This may be
    relevant since at some point BEA changed the user/password for it to
    "weblogic/weblogic"
    QUESTIONS:
    Does anybody understand why this is happening?
    Any ideas for fixes that avoid bouncing and redeployment?
    ---Paul O

  • Weblogic server with OIM non-root

    Friends,
    I am installing OIAM on top of Weblogic Server on CentOSLinux OS .
    The problem is i want to install weblogic server and OIAM with non-root so that it does not have security issues.
    When i try to install weblogic i am unable to install it with normal user rights in /opt dir it requires root access. As per the document oiam install on top of weblogic should not be a problem but the major issue is running weblogic with non-root.
    pls let me know abt install and running weblogic as a non-root user, or a pointer to the documentation.
    thank you

    I have installed weblogic server as an nt service. In install Nt service
    cmd, if I make any change in the script, I have to uninstall and install it
    again. I do not know where to specify the weblogic.management.username =(Non
    system user)
    I have created a user name in NT server and added them to Administrator
    group. I have also modified in file realm propertes i.e to boot and shutdown
    the non system user.
    I have to start weblogic server as a non system user.
    Thanks
    Madhu
    I think I replied to some of the questions when I found out the answers.
    Only thing I did was hit reply, instead of reply group. Might it went to
    persons e-mail. That might be the reason, the answers I posted is not found
    in the newsgroup
    Thanks
    freelance_code_inspector <[email protected]> wrote in message
    news:[email protected]..
    "m holur" <[email protected]> wrote in message
    news:<3bfbafce$[email protected]>...
    I want to start wls6.1 as an nt service with different user name otherthan
    system.Madhu,
    Specify weblogic.management.username={Non system user} in your -D
    option. BTW, just curious, have observed that u have been posting a
    lot of weblogic questions lately, did u find out the answers? If so, u
    should share it back to this community.
    Regards
    drit
    Freelance Java Developer/Code Inspector
    http://www.geocities.com/doc_i_t/CodeInspectionService.html

  • WebLogic with WebSphere MQ as an XA resource

    I have been using WebLogic MDBs with WebSphere MQ as an external JMS provider. We just bought MQ Extended Client that would let external transaction managers do XA management with MQ. I have looked at IBM's document @
              http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf. This document indicates that Weblogic cannot be used to do XA with MQ; only three txn managers are mentioned - CICS, Encina, and Tuxedo.
              I don't believe that to be true because it says that it can be used with any XA compliant transaction manager. Is anyone aware of documents showing how to configure a WebLogic server (expecially MDBs) to use MQ extended client to do XA?

    WL is an XA compliant TM, and many customers use it with MQ. For more information, you can start with this FAQ:
              http://e-docs.bea.com/wls/docs81/faq/interop.html#268632
              Also see the notes I've appended below.
              Finally, you can search this newsgroup - you will see that your question comes up quite a bit.
              Tom, BEA
              JMS Integration of Foreign Vendors with BEA WebLogic Server
              The following notes are derived mostly from "http://dev2dev.bea.com/technologies/jms/index.jsp".
              For additional questions, a good forum for WebLogic questions in general is "newsgroups.bea.com". These can be mined for information by using Google's newsgroup search function.
              JMS Integration Overview
              - For integration with "non-Java" and/or "non-JMS" platforms, see "Non-Java Integration Options" below.
              - For a foreign JMS vendor to participate in a WL transaction it must support XA. Specifically, it must support the javax.jms.XA* interfaces.
              - In WL versions 6.0 and up it is possible to make synchronous calls to foreign JMS vendors participate in a WL transaction as long as the foreign vendor supports XA.
              - WL 6.0 and 6.1 MDBs can be driven by foreign vendors non-transactionally. They can be driven transactionally by a select few foreign vendors (MQ is not part of the select few)
              - WL 7.0 and later, MDBs can be driven by foreign vendors transactionally and non-transationally.
              - WL 6.1 and later WL provides a messaging bridge feature. Messaging bridges forward messages between any two JMS destinations, including foreign destinations, and can transfer messages transactionally or non-transactionally.
              - WL 8.1 JMS provides additional features that simplify transactional and JNDI integration of foreign vendors. See http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
              Integration with 8.1 Details
              A good overview of 8.1 JMS interop capability is the presentation "Integrating Foreign JMS Providers with BEA WebLogic Server" here:
              http://www.bea.com/content/files/eworld/presentations/Wed_03_05_03/Application_Servers/1097-Foreign_JMS_Providers_WLS.pdf
              This document refers to helpful new 8.1 features, which simplify integration. These include:
              http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#accessing_foreign_providers
              http://edocs.bea.com/wls/docs81/jms/j2ee_components.html#1033768
              And are also summarized here (under interoperability):
              http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
              Also read the MDB documentation, which extensively covers integrating foreign vendors:
              http://edocs.bea.com/wls/docs81/ejb/message_beans.html
              The 8.1 features are likely sufficient for most 8.1 integration needs, and you may not need to refer "Using Foreign JMS Providers With WLS" white-paper mentioned below.
              Integration with 6.1 and 7.0 Details
              Read the "Using Foreign JMS Providers With WLS" white-paper:
              http://dev2dev.bea.com/products/wlserver/whitepapers/jmsproviders.jsp
              Note that this white-paper does not take into account 8.1 features.
              For 7.0 read the extensive 8.1 MDB documentation, which largely also applies to 7.0:
              http://edocs.bea.com/wls/docs81/ejb/message_beans.html
              Non-Java Integration Options
              - WL JMS has a JNI based C client which is available for Windows and some UNIX platforms. This C client supports 7.0 and up, and will be officially packaged with WLS in 9.0 (virtually unchanged). The C API is currently only supported through the jms newsgroup. See "JMS C API", here:
              http://dev2dev.bea.com/technologies/jms/index.jsp
              - WL supports direct Windows COM access through its "JCOM" feature. This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
              http://e-docs.bea.com/wls/docs61/jcom.html
              http://e-docs.bea.com/wls/docs70/jcom/
              http://e-docs.bea.com/wls/docs81/jcom/
              - Similar to JCOM, but more advanced, WL supports IIOP standard based access on multiple platforms. You can use the BEA Tuxedo C client for this purpose (no license fee). This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
              http://e-docs.bea.com/wls/docs81/rmi_iiop/
              http://e-docs.bea.com/wls/docs70/rmi_iiop/
              http://e-docs.bea.com/wls/docs61/rmi_iiop/
              Unlike most other approaches, the IIOP client approach also allows the client to begin and commit user (JTA) transactions (not configured).
              - If you already have a BEA Tuxedo license, one option is communicate through BEA Tuxedo (which has various APIs on Windows) and configure a WebLogic Server to respond to these requests via the WTC bridge. Search for "WTC" in the BEA docs. Unlike most other approaches, the Tuxedo API approach also allows the client to begin and commit user (JTA) transactions.
              - Another approach is to interop via web-service standards. Or even to simply to invoke a servlet on the WL server using a basic HTTP call from Windows. These in turn can invoke the JMS API. There is a white-paper on "Interoperability Study of BEA WebLogic Workshop 8.1 and Microsoft .NET 1.1 Web Services", that demonstrates web-services here:
              http://ftpna2.bea.com/pub/downloads/WebLogic-DotNet-Interop.pdf
              - Yet another approach is to use a third party product that is designed to wrap any JMS vendor. There are even open source versions. In no particular order, here are some examples: Open3 WinJMS, CodeMesh, Active JMS, SpiritSoft
              - Finally, there are .NET/C/C++ integration libraries that not specific to JMS, some examples are JNBridge, Jace, and CodeMesh.
              Notes on MQ Remote Capable XA Clients
              Until recently, IBM MQ JMS clients could not work transactionally unless they were running on the same host as their MQ server. This is a limitation unique to MQ that was relaxed with the introduction of IBM's new "WebSphere MQ Extended Transactional Client". See:
              http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf
              The product is new, and for some reason, configuration of this client seems to be tricky, even when WebLogic is not involved at all. Oddly, the main sticking point seems to be simply making sure that class paths refer to the required IBM jars:
              - Required on WLS where MQ objects are bound into JNDI:
              com.ibm.mq.jar, com.ibm.mqjms.jar
              - Required only if MQ objects are bound into JNDI on a different server:
              com.ibm.mq.jar
              If there are problems when using this client, first get it to work using a pure IBM client without any BEA classes involved. Once that is working, search the WL JMS newsgroup for answers and/or contact BEA customer support.
              Notes on Oracle AQ Integration
              If problems are encountered integrating Oracle's built-in queuing (Oracle AQ) JMS client, there is publicly available wrapper code that can aid integrating AQ directly into MDBs, JMS, or the messaging bridge. The solution is titled "Startup class to bind AQ/Referenceable objects to WLS JNDI", is not supported by BEA, and is posted to:
              http://dev2dev.bea.com/codelibrary/code/startupclass.jsp
              Caveats:
              The solution doesn't directly support concurrent consumers. Perhaps Oracle requires that concurrent consumers each have a unique JMS connection? As a work-around, parallel message processing can be achieved indirectly by forwarding AQ messages into a WL JMS destination - which do support concurrent processing.
              Up-to-date versions of Oracle may be required. For more information, google search the weblogic.developer.interest.jms newsgroup for "Oracle" and "AQ".
              The solution doesn't seem to support transactions, it may be possible to extend it to do so.
              MDB Thread Pool Notes
              WL7.0SP? and WL8.1 and later support the "dispatch-policy" field to specify which thread pool an MDB uses to run its instances. In most cases this field should be configured to help address potential performance issues and/or dead-locks:
              http://edocs.bea.com/wls/docs81/ejb/DDreference-ejb-jar.html#dispatch-policy
              (Note that "dispatch-policy" is ignored for non-transactional foreign vendors; in this case, the MDB "onMessage" callback runs in the foreign vendor's thread.)
              MDB Concurrency Notes
              Queue MDBs driven by foreign providers can run multiple instances concurrently. Topic MDBs driven by foreign providers are limited to one instance (not sure, but transactional foreign driven topic MDBs may not have this limitation). The size of the thread pool that the MDB runs in and the "max-beans-in-free-pool" descriptor limit how many instances run concurrently.
              Design Guide-Lines and Performance Tuning Notes
              The "WebLogic JMS Performance Guide" white-paper contains detailed design, performance, and tuning information for Clustering, Messaging Bridge, JMS, and MDBs.
              http://dev2dev.bea.com/products/wlserver/whitepapers/WL_JMS_Perform_GD.jsp

  • First JSP in WebLogic

    Can anyone answer basic troubleshooting WebLogic question?
              My simple.jsp fails. Server creates _simple.java file, but no
              _simple.class throwing the following:
              java.lang.NumberFormatException: error=2 at
              java.lang.Integer.parseInt(Integer.java:409)
              at java.lang.Integer.parseInt(Integer.java:458)
              at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled
              Code)
              at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:174)
              at
              weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:164)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:99)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:123)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:742)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:686)
              at
              weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:247
              at
              weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
              at
              weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
              Perhaps it happens on the way of compiling it. Why NumberFormat though?
              But I was able to manually compile
              _simple.java and then page
              worked. Can you suggest anything?
              Boris Garubuzov,
              Published at www.atop.com/privan,
              e-mail: [email protected],
              mailing address: PO Box 715, Seattle, Wa, 98111-0715, USA,
              residential address 616 NW 89 Street (corner of Greenwood Avenue),
              telephones: 206-374-1271 (office), 206-781-1895 (home).
              

    send ur simple jsp code and also check that u have made the proper setting
              in the property files,
              i.e. the path of javac is right ,also the path of the directory where ur
              jsp's are translated in servlets is not in the weblogic classpath.
              Hope this helps
              Bye
              Parag B.Bhagwat
              Boris Garbuzov <[email protected]> wrote in message
              news:[email protected]...
              > Can anyone answer basic troubleshooting WebLogic question?
              > My simple.jsp fails. Server creates _simple.java file, but no
              > _simple.class throwing the following:
              > -----------------------------------
              > java.lang.NumberFormatException: error=2 at
              > java.lang.Integer.parseInt(Integer.java:409)
              > at java.lang.Integer.parseInt(Integer.java:458)
              > at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled
              > Code)
              > at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:174)
              > at
              >
              weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:16
              4)
              >
              > at
              >
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              :99)
              >
              > at
              >
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              :123)
              >
              > at
              >
              >
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              l.java:742)
              >
              > at
              >
              >
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              l.java:686)
              >
              > at
              >
              >
              weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
              Manager.java:247
              >
              > )
              > at
              >
              weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
              >
              > at
              > weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
              >
              > ---------------------------------
              > Perhaps it happens on the way of compiling it. Why NumberFormat though?
              > But I was able to manually compile
              >
              > _simple.java and then page
              > worked. Can you suggest anything?
              >
              >
              > -------------------------
              > Boris Garubuzov,
              > Published at www.atop.com/privan,
              > e-mail: [email protected],
              > mailing address: PO Box 715, Seattle, Wa, 98111-0715, USA,
              > residential address 616 NW 89 Street (corner of Greenwood Avenue),
              > telephones: 206-374-1271 (office), 206-781-1895 (home).
              >
              >
              

  • MQ/WebLogic Topology and Architecture

    I am new to MQ and am trying to get my head around a couple of basic "big
              picture" things; I'll explain what I think is going on and hopefully someone
              will jump in when I'm off in the weeds. I need to do is integrate a J2EE
              application with a legacy MQ system and as you might expect, I cannot alter
              that system, I must accommodate it (which J2EE is designed to do).
              MQ is designed to be distributed; the idea that you'll install an MQ Server
              on every Application Server machines seems like a special case. In my case,
              it's academic.
              First MQ itself:
              There appears to be some internal and proprietary things MQ needs to do for
              efficiency and possibly historical reasons. To achieve that, you must install
              an MQ Client on each machine so that access appears to be local for Applications
              that talk to MQ. I have written some code that talks directly to the server
              using some of the Client libraries and I was able to send but could not get
              messages off the queue; I found some documentation that said that this would
              be the case in some circumstances. I suspect that the reason for this is
              that I may have not used the "correct" client libraries since I found some
              example code that doesn't yet run (we can ignore that for now).
              The Client install does give you Java classes that provide connectivity and
              it implies JMS support but in what form, since the classes appear to use
              proprietary code?
              Does the Client have the ability to run as a JMS Server that appears to be
              a local JMS nexus that I can talk to with standard JNDI lookups?
              WebLogic J2EE Integration:
              The ultimate goal here is to integrate an existing MQ installation so I can
              send and recieve from a J2EE Application I am working on.
              I have been reading that there's at least three different ways to make this
              connection.
              1) Roll your own using the proprietary lib clients in a startup class
              2) Using WebLogic's Bridge technology
              3) Use WebLogic's Foreign Destination configuration.
              Detailed questions below by item number:
              1) -> I understand that directly using IBM's client libraries is supposed
              to function the same as running the Client locally, that doesn't sound like
              it would give the scalability of pooling and that solution won't route to
              drive MDBs.
              2) -> A lot of posts state that for WL/MQ integration this is not necessary.
              I don't know a lot about the specifics of what I will need to do to talk
              to this other system yet, I am just trying to get my head around the general
              cases.
              3) -> This is the most appealing to me since it sounds like it is a matter
              of using the WL console to set up the JMS destination once I have the correct
              libraries in the server's classpath. It would seem that the JMS queues look
              like they are local, I can drive MDBs from this with all the manageability
              built in. However, does the server use the same provider factory class as
              I would in my own code or are there special considerations?
              Comments and pointing to specific reading encouraged (don't just say, to
              read the 677 page Java MQ docs).
              Thanks

    Wow! All I can say is "Thanks", it's gonna take we a while to get through
              all this but I do appreciate the help. I tried to get the Client stuff installed
              on my Linux dev box but it's not clear which rpms are needed and some complained
              because I am still running RH7.3. I am in the process of moving to a supported
              platform RHEL3.x or above... stay tuned.
              Hello Tom,
              > Hi!
              >
              > If you haven't already done it, the best place to start is to read
              > through the entire "Integrating Remote JMS Providers" FAQ:
              >
              > http://e-docs.bea.com/wls/docs81/faq/interop.html
              >
              > I'm also appending my own integration notes which mention MQ (and
              > which you may have already run across). I update these notes from
              > time to time. Enjoy!
              >
              > Tom, BEA
              >
              > JMS Integration of Foreign Vendors with BEA WebLogic Server
              > -----------------------------------------------------------
              >
              > The following notes are derived mostly from
              > "http://dev2dev.bea.com/technologies/jms/index.jsp".
              >
              > For additional questions, a good forum for WebLogic questions in
              > general is "newsgroups.bea.com". These can be mined for information by
              > using Google's newsgroup search function.
              >
              > JMS Integration Overview
              > ------------------------
              > - For integration with "non-Java" and/or "non-JMS" platforms, see
              > "Non-Java Integration Options" below.
              >
              > - For a foreign JMS vendor to participate in a WL transaction it must
              > support XA. Specifically, it must support the javax.jms.XA*
              > interfaces.
              >
              > - In WL versions 6.0 and up it is possible to make synchronous calls
              > to foreign JMS vendors participate in a WL transaction as long as the
              > foreign vendor supports XA.
              >
              > - WL 6.0 and 6.1 MDBs can be driven by foreign vendors
              > non-transactionally. They can be driven transactionally by a select
              > few foreign vendors (MQ is not part of the select few)
              >
              > - WL 7.0 and later, MDBs can be driven by foreign vendors
              > transactionally and non-transationally.
              >
              > - WL 6.1 and later WL provides a messaging bridge feature. Messaging
              > bridges forward messages between any two JMS destinations, including
              > foreign destinations, and can transfer messages transactionally or
              > non-transactionally.
              >
              > - WL 8.1 JMS provides additional features that simplify transactional
              > and JNDI integration of foreign vendors. See
              > http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features and
              > http://e-docs.bea.com/wls/docs81/faq/interop.html
              >
              > Integration with 8.1 Details
              > ----------------------------
              > To start, first read the "Integrating Remote JMS Providers FAQ"
              > (released in Dec 2004) at:
              > http://e-docs.bea.com/wls/docs81/faq/interop.html
              >
              > A good overview of 8.1 JMS interop capability is the presentation
              > "Integrating Foreign JMS Providers with BEA WebLogic Server" here:
              >
              > http://www.bea.com/content/files/eworld/presentations/Wed_03_05_03/App
              > lication_Servers/1097-Foreign_JMS_Providers_WLS.pdf
              >
              > This document refers to helpful new 8.1 features, which simplify
              > integration. These include:
              > http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#accessing_
              > foreign_providers
              > http://edocs.bea.com/wls/docs81/jms/j2ee_components.html#1033768
              > And are also summarized here (under interoperability):
              > http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
              > Also read the MDB documentation, which extensively covers integrating
              > foreign vendors:
              >
              > http://edocs.bea.com/wls/docs81/ejb/message_beans.html
              >
              > The 8.1 features are likely sufficient for most 8.1 integration needs,
              > but you may want to refer to the "Using Foreign JMS Providers With
              > WLS" white-paper mentioned below, which is 7.0 specific but contains
              > specific examples of configuring non-WebLogic JMS vendors. See also
              > notes on "MQ" below.
              >
              > Integration with 6.1 and 7.0 Details
              > ------------------------------------
              > Read the "Using Foreign JMS Providers With WLS" white-paper:
              >
              > http://dev2dev.bea.com/products/wlserver/whitepapers/jmsproviders.jsp
              >
              > Note that this white-paper does not take into account 8.1 features.
              >
              > For 7.0 read the extensive 8.1 MDB documentation, which largely also
              > applies to 7.0:
              >
              > http://edocs.bea.com/wls/docs81/ejb/message_beans.html
              >
              > Non-Java Integration Options
              > ----------------------------
              > - WL JMS has a JNI based C client which is available for Windows and
              > some UNIX platforms. This C client supports 7.0 and up, and will be
              > officially packaged with WLS in 9.0 (virtually unchanged). The C API
              > is currently only supported through the jms newsgroup. See "JMS C
              > API", here:
              >
              > http://dev2dev.bea.com/technologies/jms/index.jsp
              >
              > - WL supports direct Windows COM access through its "JCOM" feature.
              > This doesn't include the JMS API, but one can invoke EJBs which in
              > turn invoke JMS. See
              >
              > http://e-docs.bea.com/wls/docs61/jcom.html
              >
              > http://e-docs.bea.com/wls/docs70/jcom/
              >
              > http://e-docs.bea.com/wls/docs81/jcom/
              >
              > - Similar to JCOM, but more advanced and supported on more platforms,
              > WL supports access via the standard IIOP protocol. You can use the
              > BEA Tuxedo C client for this purpose (no license fee). This doesn't
              > include the JMS API, but one can invoke EJBs which in turn invoke JMS.
              > See
              > http://e-docs.bea.com/wls/docs81/rmi_iiop/
              > http://e-docs.bea.com/wls/docs70/rmi_iiop/
              > http://e-docs.bea.com/wls/docs61/rmi_iiop/
              > Unlike most other approaches, the IIOP client approach also allows the
              > client to begin and commit user (JTA) transactions (not configured).
              > - If you already have a BEA Tuxedo license, one option is communicate
              > through BEA Tuxedo (which has various APIs on Windows) and configure a
              > WebLogic Server to respond to these requests via the WTC bridge.
              > Search for "WTC" in the BEA docs. Unlike most other approaches, the
              > Tuxedo API approach also allows the client to begin and commit user
              > (JTA) transactions.
              >
              > - Another approach is to interop via web-service standards. Or even to
              > simply to invoke a servlet on the WL server using a basic HTTP call
              > from the client. These operation in turn can invoke the JMS API.
              > There is a white-paper on "Interoperability Study of BEA WebLogic
              > Workshop 8.1 and Microsoft .NET 1.1 Web Services", that demonstrates
              > web-services here:
              > http://ftpna2.bea.com/pub/downloads/WebLogic-DotNet-Interop.pdf
              >
              > - Yet another approach is to use a third party product that is
              > designed to wrap any JMS vendor. There are even open source
              > versions. In no particular order, here are some examples: Open3
              > WinJMS, CodeMesh, Active JMS, SpiritSoft
              >
              > - Finally, there are .NET/C/C++ integration libraries that are not
              > specific to JMS, some examples are JNBridge, Jace, and CodeMesh.
              >
              > Notes on MQ Remote Capable XA Clients
              > -------------------------------------
              > Until recently, IBM MQ JMS clients could not work transactionally
              > unless they were running on the same host as their MQ server. This is
              > a limitation unique to MQ that was relaxed with the introduction of
              > IBM's new "WebSphere MQ Extended Transactional Client". See:
              >
              > http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf
              >
              > The product is new, and for some reason, configuration of this client
              > seems to be tricky, even when WebLogic is not involved at all. Oddly,
              > the main sticking point seems to be simply making sure that class
              > paths refer to the required IBM jars:
              >
              > - Required on WLS where MQ objects are bound into JNDI:
              > com.ibm.mq.jar, com.ibm.mqjms.jar
              >
              > - Required only if MQ objects are bound into JNDI on a different
              > server: com.ibm.mq.jar
              >
              > If there are problems when using this client, first get it to work
              > using a pure IBM client without any BEA classes involved. Once that
              > is working, search the WL JMS newsgroup for answers and/or contact BEA
              > customer support.
              >
              > Notes on Oracle AQ Integration
              > ------------------------------
              > If problems are encountered integrating Oracle's built-in queuing
              > (Oracle AQ) JMS client, there is publicly available wrapper code that
              > can aid integrating AQ directly into MDBs, JMS, or the messaging
              > bridge. The solution is titled "Startup class to bind
              > AQ/Referenceable objects to WLS JNDI", is not supported by BEA, and is
              > posted to:
              >
              > http://dev2dev.bea.com/codelibrary/code/startupclass.jsp (older
              > version) http://xa-compliant-oracleaq.projects.dev2dev.bea.com (newer
              > version)
              >
              > Caveats:
              >
              > It may be that the solution doesn't directly support concurrent
              > consumers. Perhaps Oracle requires that concurrent consumers each
              > have a unique JMS connection? As a work-around, parallel message
              > processing can be achieved indirectly by forwarding AQ messages into a
              > WL JMS destination - which do support concurrent processing.
              >
              > Up-to-date versions of Oracle may be required. For more information,
              > google search the weblogic.developer.interest.jms newsgroup for
              > "Oracle" and "AQ".
              >
              > MDB Thread Pool Notes
              > ---------------------
              > WL7.0SP? and WL8.1 and later support the "dispatch-policy" field to
              > specify which thread pool an MDB uses to run its instances. In most
              > cases this field should be configured to help address potential
              > performance issues and/or dead-locks:
              >
              > http://edocs.bea.com/wls/docs81/ejb/DDreference-ejb-jar.html#dispatch-
              > policy
              >
              > (Note that "dispatch-policy" is ignored for non-transactional foreign
              > vendors; in this case, the MDB "onMessage" callback runs in the
              > foreign vendor's thread.)
              >
              > MDB Concurrency Notes
              > ---------------------
              > Queue MDBs driven by foreign providers can run multiple instances
              > concurrently. Topic MDBs driven by foreign providers are limited to
              > one instance (not sure, but transactional foreign driven topic MDBs
              > may not have this limitation). The size of the thread pool that the
              > MDB runs in and the "max-beans-in-free-pool" descriptor limit how many
              > instances run concurrently.
              >
              > Design Guide-Lines and Performance Tuning Notes
              > -----------------------------------------------
              > The "WebLogic JMS Performance Guide" white-paper contains detailed
              > design, performance, and tuning information for Clustering, Messaging
              > Bridge, JMS, and MDBs.
              >
              > http://dev2dev.bea.com/products/wlserver/whitepapers/WL_JMS_Perform_GD
              > .jsp
              >

  • Created weblogic domain, but can't start on wls 10, using config.sh on linx

    Here is the, I haven't done anything but run, the auto created startWebLogic.sh
    don't know why it's screaming about the boot.properties being wrong, is there a specific variable I can see in the scripts to explicit set location .
    I tried deleting, and recreated the domains so many times no luck, I don't know what I am doing wrong, first time starting out on weblogic 10
    there is no managed server etc..
    domian_home/servers/AdminServer/security
    boot.properties
    # Generated by Configuration Wizard on Wed Jul 16 17:40:36 EDT 2008
    username={3DES}hH53ykFNGmRbKURntGa/UQ==
    password={3DES}hH53ykFNGmRbKURntGa/UQ==
    JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m
    WLS Start Mode=Development
    CLASSPATH=:/oss/bsimple/wls_10_0_1/patch_wlw1001/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/oss/bsimple/wls_10_0_1/patch_wls1001/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/oss/bsimple/wls_10_0_1/jdk6/lib/tools.jar:/oss/bsimple/wls_10_0_1/wlserver_10.0/server/lib/weblogic_sp.jar:/oss/bsimple/wls_10_0_1/wlserver_10.0/server/lib/weblogic.jar:/oss/bsimple/wls_10_0_1/modules/features/weblogic.server.modules_10.0.1.0.jar:/oss/bsimple/wls_10_0_1/modules/features/com.bea.cie.common-plugin.launch_2.1.2.0.jar:/oss/bsimple/wls_10_0_1/wlserver_10.0/server/lib/webservices.jar:/oss/bsimple/wls_10_0_1/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/oss/bsimple/wls_10_0_1/modules/net.sf.antcontrib_1.0b2.0/lib/ant-contrib.jar::/oss/bsimple/wls_10_0_1/wlserver_10.0/common/eval/pointbase/lib/pbclient51.jar:/oss/bsimple/wls_10_0_1/wlserver_10.0/server/lib/xqrl.jar::
    PATH=/oss/bsimple/wls_10_0_1/wlserver_10.0/server/bin:/oss/bsimple/wls_10_0_1/modules/org.apache.ant_1.6.5/bin:/oss/bsimple/wls_10_0_1/jdk6/jre/bin:/oss/bsimple/wls_10_0_1/jdk6/bin:/oss/bsimple/bin:/oss/java/j2sdk1.4.2_17/bin:/bin:/sbin:/usr/bin:/opt/datasvcs/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/oss/ant/bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    java version "1.6.0_07"
    Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
    Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)
    Starting WLS with line:
    /oss/bsimple/wls_10_0_1/jdk6/bin/java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -Xverify:none -da -Dplatform.home=/oss/bsimple/wls_10_0_1/wlserver_10.0 -Dwls.home=/oss/bsimple/wls_10_0_1/wlserver_10.0/server -Dweblogic.home=/oss/bsimple/wls_10_0_1/wlserver_10.0/server -Dwli.home=/oss/bsimple/wls_10_0_1/wlserver_10.0/integration -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/oss/bsimple/wls_10_0_1/patch_wlw1001/profiles/default/sysext_manifest_classpath:/oss/bsimple/wls_10_0_1/patch_wls1001/profiles/default/sysext_manifest_classpath -Dweblogic.management.username=system -Dweblogic.management.password=development -Dweblogic.Name=AdminServer -Djava.security.policy=/oss/bsimple/wls_10_0_1/wlserver_10.0/server/lib/weblogic.policy weblogic.Server
    <Jul 16, 2008 5:47:20 PM EDT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
    /oss/bsimple/wls_10_0_1/wlserver_10.0/platform/lib/p13n/p13n-schemas.jar:/oss/bsimple/wls_10_0_1/wlserver_10.0/platform/lib/p13n/p13n_common.jar:/oss/bsimple/wls_10_0_1/wlserver_10.0/platform/lib/p13n/p13n_system.jar:/oss/bsimple/wls_10_0_1/wlserver_10.0/platform/lib/wlp/netuix_common.jar:/oss/bsimple/wls_10_0_1/wlserver_10.0/platform/lib/wlp/netuix_schemas.jar:/oss/bsimple/wls_10_0_1/wlserver_10.0/platform/lib/wlp/netuix_system.jar:/oss/bsimple/wls_10_0_1/wlserver_10.0/platform/lib/wlp/wsrp-client.jar:/oss/bsimple/wls_10_0_1/wlserver_10.0/platform/lib/wlp/wsrp-common.jar>
    <Jul 16, 2008 5:47:20 PM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 10.0-b23 from Sun Microsystems Inc.>
    <Jul 16, 2008 5:47:21 PM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.0 MP1 Thu Oct 18 20:17:44 EDT 2007 1005184 >
    <Jul 16, 2008 5:47:22 PM EDT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /oss/bsimple/bea-new/license.bea>
    <Jul 16, 2008 5:47:22 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Jul 16, 2008 5:47:22 PM EDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Jul 16, 2008 5:47:23 PM EDT> <Notice> <Log Management> <BEA-170019> <The server log file /oss/bsimple/wls_10_0_1/user_projects/domains/bsimple/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
    <Jul 16, 2008 5:47:26 PM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Jul 16, 2008 5:47:26 PM EDT> <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>
    <Jul 16, 2008 5:47:26 PM EDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
    weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
    at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    Truncated. see log file for complete stacktrace
    >
    <Jul 16, 2008 5:47:26 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Jul 16, 2008 5:47:26 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Jul 16, 2008 5:47:26 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    <?xml version="1.0" encoding="UTF-8"?>
    <domain xsi:schemaLocation="http://www.bea.com/ns/weblogic/90/security
    http://www.bea.com/ns/weblogic/90/security.xsd
    http://www.bea.com/ns/weblogic/90/security/wls
    http://www.bea.com/ns/weblogic/90/security/wls.xsd
    http://www.bea.com/ns/weblogic/90/security/xacml
    http://www.bea.com/ns/weblogic/90/security/xacml.xsd
    http://www.bea.com/ns/weblogic/920/domain
    http://www.bea.com/ns/weblogic/920/domain.xsd" xmlns="http://www.bea.com/ns/weblogic/920/domain" xmlns:sec="http://www.bea.com/ns/we
    blogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    >
    <name>bsimple</name>
    <domain-version>10.0.1.0</domain-version>
    <security-configuration xmlns:xacml="http://www.bea.com/ns/weblogic/90/security/xacml">
    <name>bsimple</name>
    <realm>
    <sec:authentication-provider xsi:type="wls:default-authenticatorType"/>
    <sec:authentication-provider xsi:type="wls:default-identity-asserterType">
    <sec:active-type>AuthenticatedUser</sec:active-type>
    </sec:authentication-provider>
    <sec:role-mapper xsi:type="xacml:xacml-role-mapperType"/>
    <sec:authorizer xsi:type="xacml:xacml-authorizerType"/>
    <sec:adjudicator xsi:type="wls:default-adjudicatorType"/>
    <sec:credential-mapper xsi:type="wls:default-credential-mapperType"/>
    <sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"/>
    <sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
    <sec:name>myrealm</sec:name>
    </realm>
    <default-realm>myrealm</default-realm>
    <credential-encrypted>{3DES}M0uIyUu+rkaqCqDjqdxMKlkKjcpsblHYWXLU9bR4i2BWw0C01mePtB3yrEk1avk9/eTY2JmIjZTSxAklRM8wJgwnXNC3f9LS</cr
    edential-encrypted>
    <node-manager-username>weblogic</node-manager-username>
    <node-manager-password-encrypted>{3DES}hH53ykFNGmRbKURntGa/UQ==</node-manager-password-encrypted>
    </security-configuration>
    <server>
    <name>AdminServer</name>
    <listen-address/>
    </server>
    <embedded-ldap>
    <name>bsimple</name>
    <credential-encrypted>{3DES}ICXW2sS2alNzN1Aqcs+jAUhyGBUfVgIZhKwMcJS2nck=</credential-encrypted>
    </embedded-ldap>
    <configuration-version>10.0.1.0</configuration-version>
    <admin-server-name>AdminServer</admin-server-name>
    </domain>

    Hi All,
    I am using the Bea Application server 10.0.MP1 and want to start the respective app servers using nohup ./startWeblogic.sh.
    However every time I use the nuhup.out command, it complains with the error:
    <Jul 19, 2011 2:01:53 AM CDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitial
    izationException: Authentication for user denied
    weblogic.security.SecurityInitializationException: Authentication for user denied
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
    at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    Truncated. see log file for complete stacktrace
    >
    <Jul 19, 2011 2:01:53 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Jul 19, 2011 2:01:53 AM CDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Jul 19, 2011 2:01:53 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    I have been reading your threads and have created the boot.properties file. I have placed in the following directory:
    - /tezaam/apps/bea/user_projects/domains/xxx_domain/security
    The boot.properties file contains two lines:
    username=weblogic
    password=weblogic
    Question: Is is in the correct directory path or should it reside elsewhere as I am not using a nodemanager and start each AdminServer on its own.
    Appreciate feedback.
    Thanks
    Tony

  • Auto start weblogic

    Hi all,
    I want to autostart the weblogic server everytime after the server
    is rebooted. Since the weblogic server is installed and run as user
    "peter". How can I do it in the solaris??
    Rgds,
    unplug

    Jesse,
    I did the following.
    make a copy of startWebLogic.sh in init.d.
    make a link of startWebLogic.sh as S99WebLogic in rc3.d
    make a link of startWebLogic.sh as K99WebLogic in rc0.d
    Are there any problems in the above actions??
    Does the initialization script run by root?? I think so.
    So is there any problems if the startWebLogic.sh is own by
    other user (not root) for the above actions??
    thanks,
    unplug
    Jesse E Tilly wrote:
    >
    [email protected] (unplug) wrote in <[email protected]>:
    Hi all,
    I want to autostart the weblogic server everytime after the server
    is rebooted. Since the weblogic server is installed and run as user
    "peter". How can I do it in the solaris??
    Rgds,
    unplugUnplug,
    This is really more of a Solaris administration question than a WebLogic
    question. I will give you a head start, but I really recommend that if
    you're going to develop or deploy on a Solaris system that you consider
    hiring a Solaris administrator or taking admin classes and certifications
    on your own if you're gonna be the admin. Solaris can be powerful, but you
    have enough rope to hang yourself and your corporation in 8 easy
    characters, "rm -Rf /".
    Solaris uses what's called SysVInit (Linux does, BSD does not). The init
    scripts are based on the system's runlevel (a number 0-7). Usually 6 is
    reserved for reboot, 0 for shutdown, 1 for single-user and 2-5 for various
    run states. One of my systems, for example, defaults to level 3. You can
    check this in /etc/inittab. Look for initdefault and the number next to
    it. Depending on the runlevel, init (the Unix initialization program) runs
    an rc script. For 3 this is rc3. This can be found at /etc/rc3. It will
    run various checks and variable settings then run the scripts found in
    /etc/rc3.d (d for directory, get it?). There is a README (or should be)
    that describes how the scripts are run, should be made, etc. In Linux,
    these scripts are soft links to another group of scripts. In Solaris,
    that's not always the case.
    Anyway, to shorten this up, you're gonna want a weblogic start script
    (S99Weblogic) for rc3.d and a kill script (K99Weblogic) for the rc0.d
    directory. Check the file names. Sblahblah means start, Kblahblah means
    kill. Do a man on "init" and read the README in rc3.d.
    Jesse

  • JSF 2.0 and Weblogic 10.3.6

    Hi,
    I am planning to use JSF 2.0 on Weblogic Server 10.3.6.
    What implementation of JSF 2.0 is used by weblogic servers ( Mojarra ?)
    Is a Reference Implementation like Mojarra, compatible to be used with other component libraries ?
    Thanks

    Why don't you ask Weblogic questions in the Weblogic forums? https://forums.oracle.com/forums/category.jspa?categoryID=193
    If you startup the server with a simple webapp deployed to it you should be able to see in the server log which implementation of JSF is there. A simple text search for "Mojarra" should already tell you if it is used or not. A simple google query for "weblogic 10.3 mojarra" seems to indicate it is in fact Mojarra for both JSF 1.2 and 2.0.

  • How to connect weblogic 8.1 to IBM MQ Series from remote machines?

    Hi,
              I am trying to connect WebLogic 8.1 to IBM MQ Series 6.0 both are running in a seperate machines.Can we do using JNDI services? Can anyone help me to fix this issue?

    I'm cutting/pasting my notes on the topic, including MQ specific notes. Start with the Integrating Remote JMS Providers FAQ (link below). You can also search this newsgroup for answers.
              Tom
              JMS Integration of Foreign Vendors with BEA WebLogic Server
              The following notes are derived mostly from "http://dev2dev.bea.com/technologies/jms/index.jsp".
              For additional questions, a good forum for WebLogic questions in general is "newsgroups.bea.com". These can be mined for information by using Google's newsgroup search function.
              JMS Integration Overview
              - For integration with "non-Java" and/or "non-JMS" platforms, see "Non-Java Integration Options" below.
              - For a foreign JMS vendor to participate in a WL transaction it must support XA. Specifically, it must support the javax.jms.XA* interfaces.
              - In WL versions 6.0 and up it is possible to make synchronous calls to foreign JMS vendors participate in a WL transaction as long as the foreign vendor supports XA.
              - WL 6.0 and 6.1 MDBs can be driven by foreign vendors non-transactionally. They can be driven transactionally by a select few foreign vendors (MQ is not part of the select few)
              - WL 7.0 and later, MDBs can be driven by foreign vendors transactionally and non-transationally.
              - WL 6.1 and later WL provides a messaging bridge feature. Messaging bridges forward messages between any two JMS destinations, including foreign destinations, and can transfer messages transactionally or non-transactionally.
              - WL 8.1 JMS provides additional features that simplify transactional and JNDI integration of foreign vendors. See http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features and http://e-docs.bea.com/wls/docs81/faq/interop.html
              Integration with 8.1 Details
              To start, first read the "Integrating Remote JMS Providers FAQ" (released in Dec 2004) at:
              http://e-docs.bea.com/wls/docs81/faq/interop.html
              A good overview of 8.1 JMS interop capability is the presentation "Integrating Foreign JMS Providers with BEA WebLogic Server" here:
              http://www.bea.com/content/files/eworld/presentations/Wed_03_05_03/Application_Servers/1097-Foreign_JMS_Providers_WLS.pdf
              This document refers to helpful new 8.1 features, which simplify integration. These include:
              http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#accessing_foreign_providers
              http://edocs.bea.com/wls/docs81/jms/j2ee_components.html#1033768
              And are also summarized here (under interoperability):
              http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
              Also read the MDB documentation, which extensively covers integrating foreign vendors:
              http://edocs.bea.com/wls/docs81/ejb/message_beans.html
              The 8.1 features are likely sufficient for most 8.1 integration needs, but you may want to refer to the "Using Foreign JMS Providers With WLS" white-paper mentioned below, which is 7.0 specific but contains specific examples of configuring non-WebLogic JMS vendors. See also notes on "MQ" below.
              Integration with 6.1 and 7.0 Details
              Read the "Using Foreign JMS Providers With WLS" white-paper:
              http://dev2dev.bea.com/products/wlserver/whitepapers/jmsproviders.jsp
              Note that this white-paper does not take into account 8.1 features.
              For 7.0 read the extensive 8.1 MDB documentation, which largely also applies to 7.0:
              http://edocs.bea.com/wls/docs81/ejb/message_beans.html
              Non-Java Integration Options
              - WL JMS has a JNI based C client which is available for Windows and some UNIX platforms. This C client supports 7.0 and up, and will be officially packaged with WLS in 9.0 (virtually unchanged). The C API is currently only supported through the jms newsgroup. See "JMS C API", here:
              http://dev2dev.bea.com/technologies/jms/index.jsp
              - WL supports direct Windows COM access through its "JCOM" feature. This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
              http://e-docs.bea.com/wls/docs61/jcom.html
              http://e-docs.bea.com/wls/docs70/jcom/
              http://e-docs.bea.com/wls/docs81/jcom/
              - Similar to JCOM, but more advanced and supported on more platforms, WL supports access via the standard IIOP protocol. You can use the BEA Tuxedo C client for this purpose (no license fee). This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
              http://e-docs.bea.com/wls/docs81/rmi_iiop/
              http://e-docs.bea.com/wls/docs70/rmi_iiop/
              http://e-docs.bea.com/wls/docs61/rmi_iiop/
              Unlike most other approaches, the IIOP client approach also allows the client to begin and commit user (JTA) transactions (not configured).
              - If you already have a BEA Tuxedo license, one option is communicate through BEA Tuxedo (which has various APIs on Windows) and configure a WebLogic Server to respond to these requests via the WTC bridge. Search for "WTC" in the BEA docs. Unlike most other approaches, the Tuxedo API approach also allows the client to begin and commit user (JTA) transactions.
              - Another approach is to interop via web-service standards. Or even to simply to invoke a servlet on the WL server using a basic HTTP call from the client. These operation in turn can invoke the JMS API. There is a white-paper on "Interoperability Study of BEA WebLogic Workshop 8.1 and Microsoft .NET 1.1 Web Services", that demonstrates web-services here:
              http://ftpna2.bea.com/pub/downloads/WebLogic-DotNet-Interop.pdf
              - Yet another approach is to use a third party product that is designed to wrap any JMS vendor. There are even open source versions. In no particular order, here are some examples: Open3 WinJMS, CodeMesh, Active JMS, SpiritSoft
              - Finally, there are .NET/C/C++ integration libraries that are not specific to JMS, some examples are JNBridge, Jace, and CodeMesh.
              Notes on MQ Remote Capable XA Clients
              Until recently, IBM MQ JMS clients could not work transactionally unless they were running on the same host as their MQ server. This is a limitation unique to MQ that was relaxed with the introduction of IBM's new "WebSphere MQ Extended Transactional Client". See:
              http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf
              The product is new, and for some reason, configuration of this client seems to be tricky, even when WebLogic is not involved at all. Oddly, the main sticking point seems to be simply making sure that class paths refer to the required IBM jars:
              - Required on WLS where MQ objects are bound into JNDI:
              com.ibm.mq.jar, com.ibm.mqjms.jar
              - Required only if MQ objects are bound into JNDI on a different server:
              com.ibm.mq.jar
              If there are problems when using this client, first get it to work using a pure IBM client without any BEA classes involved. Once that is working, search the WL JMS newsgroup for answers and/or contact BEA customer support.
              Notes on Oracle AQ Integration
              If problems are encountered integrating Oracle's built-in queuing (Oracle AQ) JMS client, there is publicly available wrapper code that can aid integrating AQ directly into MDBs, JMS, or the messaging bridge. The solution is titled "Startup class to bind AQ/Referenceable objects to WLS JNDI", is not supported by BEA, and is posted to:
              http://dev2dev.bea.com/codelibrary/code/startupclass.jsp (older version)
              http://xa-compliant-oracleaq.projects.dev2dev.bea.com (newer version)
              Caveats:
              It may be that the solution doesn't directly support concurrent consumers. Perhaps Oracle requires that concurrent consumers each have a unique JMS connection? As a work-around, parallel message processing can be achieved indirectly by forwarding AQ messages into a WL JMS destination - which do support concurrent processing.
              Up-to-date versions of Oracle may be required. For more information, google search the weblogic.developer.interest.jms newsgroup for "Oracle" and "AQ".
              MDB Thread Pool Notes
              WL7.0SP? and WL8.1 and later support the "dispatch-policy" field to specify which thread pool an MDB uses to run its instances. In most cases this field should be configured to help address potential performance issues and/or dead-locks:
              http://edocs.bea.com/wls/docs81/ejb/DDreference-ejb-jar.html#dispatch-policy
              (Note that "dispatch-policy" is ignored for non-transactional foreign vendors; in this case, the MDB "onMessage" callback runs in the foreign vendor's thread.)
              MDB Concurrency Notes
              Queue MDBs driven by foreign providers can run multiple instances concurrently. Topic MDBs driven by foreign providers are limited to one instance (not sure, but transactional foreign driven topic MDBs may not have this limitation). The size of the thread pool that the MDB runs in and the "max-beans-in-free-pool" descriptor limit how many instances run concurrently.
              Design Guide-Lines and Performance Tuning Notes
              The "WebLogic JMS Performance Guide" white-paper contains detailed design, performance, and tuning information for Clustering, Messaging Bridge, JMS, and MDBs.
              http://dev2dev.bea.com/products/wlserver/whitepapers/WL_JMS_Perform_GD.jsp

Maybe you are looking for

  • Barcode printing in simple abap report

    Hai, I want to print Barcode for 'RESERVATION' in my simple abap report.Can you please give step by step procedure to achieve this? Thank you. Note :I saw many threads in sdn,it is NOT clear for me. With Regards, Jaheer.

  • HT4437 mirroring the computer on apple tv

    Is there a way to mirror what is on my MacBook Pro onto the tv using Apple TV?

  • Crossgrade 5.0.4 to 5.1.2

    I'm currently on a Dual G5 running FCP 5.0.4 (Final Cut Studio); what are the main benefits / concerns to crossgrading to the Universal version..? Thx, Ross. ~~~~~~~~~~~~ Dual G5 2GHz; 23" ACD; 3.5GB   Mac OS X (10.4.8)   Focusrite Saffire; LaCie 250

  • Dreamweaver CS5 quits unexpectedly after installing Yosemite but other programs work

    After installing OS X Yosemite 10.10.1 on my Macbook Pro, Dreamweaver CS5 will load part way and then crash. Other programs seem to load just fine and I don't know what to do. Model Name: MacBook Pro   Model Identifier: MacBookPro5,4   Processor Name

  • InDesign CS4 crashing?

    Recently had to erase hard drive and re-intall all software. MAC laptop OS 10.6.8. Installed CS4 and everything seems to be fine except for InDesign. Will open but then crashes. I downloaded the latest upgrade but problem still exists. Illustrator, P