Error migrating clientgen from weblogic 8.1 sp5 to 10 - clientgen

I am currently trying to port an ant script from weblogic 8.1 to 10. When I run the new ant script for 10 I get the following output:
[clientgen]
[clientgen] *********** jax-rpc clientgen attribute settings ***************
[clientgen]
[clientgen] wsdlURI: file:/D:/project/app/wsdl/wserv.wsdl
[clientgen] serviceName : null
[clientgen] packageName : com.dr.proc.ws
[clientgen] destDir : D:\temp\out
[clientgen] handlerChainFile : null
[clientgen] generatePolicyMethods : false
[clientgen] autoDetectWrapped : true
[clientgen] jaxRPCWrappedArrayStyle : true
[clientgen] generateAsyncMethods : true
[clientgen]
[clientgen] *********** jax-rpc clientgen attribute settings end ***************
[clientgen] Package name is com.dr.proc.ws
[clientgen] DestDir is D:\temp\out
[clientgen] class name is EGTWS_Stub
[clientgen] service class name is EGT
[clientgen] Porttype name is EGTWS
[clientgen] service impl name is EGT_Impl
BUILD FAILED
D:\project\app\build.xml:4: The following error occurred while executing this
line:
D:\project\app\build2.xml:105: weblogic.wsee.tools.WsBuildException: java.io.IOException
The ant script component looks like this:
<clientgen wsdl="${WSDL_FILE}" packageName="${WSCLIENT_PACKAGE}" destDir="${TEMP_DIR}/out/">
<classpath refid="clientgen.class.path" />
<classpath refid="webservice.class.path" />
</clientgen>
Also when I look at the javawsdl_mapping file it is empty. I was wondering if anyone has seen this before or has any tips.
Thanks
Mitchell
Edited by mitchellsullivan at 12/12/2007 8:16 PM

I found the answer to this. I put ant into debug mode and check out the stack trace, it was having trouble finding a "type library" using AntClassLoader. I needed to include the weblogic-container-binding.jar in the classpath and errors went away.
Edited by mitchellsullivan at 12/12/2007 8:16 PM

Similar Messages

  • Migrating applciation from weblogic to oracle 9i application server(OC4J)??????

    Hi,
    I am migrating my ejb application from weblogic to oracle 9i application server.What changes are needed to be made in code and what configuration changes are required.
    In my application i use a couple of session beans wherin a session bean calls the method of the other session bean which acceses the database.I am using a jdbc thin driver for the database connection. is it possible for a session bean to call a method of another session bean which access the database??This concept works well in weblogic where the current application is running.
    The problem is that while migrating the application to the orion server, it gives an OrionCMTException ...
    memory leak..etc.
    Could any one clarify.
    Thanks in advance!!!

    Hi Avi and Harrison,
    Cease Fire avi!!!!.First of all let me clear the issue of posting the same problem twice.Well, when i mentioned the problem the first time , i found the title session bean deployment was not right and few people would look into it as it was a common problem so i thought it would be appropriate if i mentioned the title correctly , so i posted the query again with the change in title.
    Now coming to the answer for ur questions.
    The platform used is MS Windows NT.
    The (OC4J) version is 1.0.2.2.1.
    I am not using JDeveloper.
    The database is oracle 8i and i am using the thin driver.
    The beans to be deployed are stateless session beans.
    The client involved is a web client i.e a jsp application.
    The first session bean is as follows.
    import java.sql.Connection;
    import java.sql.Statement;
    import java.sql.ResultSet;
    import java.sql.SQLException;
    import java.util.Vector;
    import java.sql.Timestamp;
    import java.rmi.RemoteException;
    import java.util.Date;
    import javax.ejb.*;
    import javax.naming.*;
    import initcontext;
    import PrintMessage;
    import JB_B2B_ERROR_PARSER;
    * @stereotype SessionBean
    * @homeInterface DB_UTILITYHome
    * @remoteInterface DB_UTILITYRemote
    public class DB_UTILITY implements SessionBean
         private SessionContext context;
    private ResultSet rs = null;
    private Statement stmt = null;
    private Connection con = null;
    private PrintMessage print = null;
    public DB_UTILITY()
    rs = null;
    stmt = null;
    con = null;
    print = new PrintMessage();
         public Connection getConnection()throws RemoteException
              InitialContext initctx = null;
              Connection con = null;
              try
                   initctx = initcontext.getContext();
                   javax.sql.DataSource ds =
    (javax.sql.DataSource)initctx.lookup("java:comp/env/jdbc/ePool");
                   con = ds.getConnection();
    //(javax.sql.DataSource)initctx.lookup("java:comp/env/jdbc/ePool");
    catch(NamingException namingexception)
    print.printUserMessage("DB_UTILITY", (new
    Date()).toString(), "", namingexception);
    throw new
    EpoolException(JB_B2B_ERROR_PARSER.getErrorMessage("AppError",
    "Epool-10001", "DB_UTILITY.getConnection"));
    catch(SQLException sqlexception)
    print.printUserMessage("DB_UTILITY", (new
    Date()).toString(), "", sqlexception);
    throw new
    epoolException(JB_B2B_ERROR_PARSER.getErrorMessage("DBError",
    JB_B2B_ERROR_PARSER.getSQLCode(sqlexception),
    "DB_UTILITY.getConnection"));
    catch(Exception exception)
    print.printUserMessage("DB_UTILITY", (new
    Date()).toString(), "", exception);
    throw new
    epoolException(JB_B2B_ERROR_PARSER.getErrorMessage("EpoolError",
    "Epool10005", "DB_UTILITY.getConnection"));
              return con;
         public String getDate()throws RemoteException
              String Date=null;
              try
                   con=getConnection();
                   stmt=con.createStatement();
                   rs=stmt.executeQuery("SELECT
    TO_CHAR(SYSDATE,'YYYY-MM-DD HH:MI:SS') FROM DUAL");
                   while(rs.next())
                        Date=rs.getString(1);
                   stmt.close();
                   con.close();
    catch(SQLException sqlexception)
         print.printUserMessage("DB_UTILITY", (new
    Date()).toString(), "", sqlexception);
    throw new
    EpoolException(JB_B2B_ERROR_PARSER.getErrorMessage("DBError",
    JB_B2B_ERROR_PARSER.getSQLCode(sqlexception), "DB_UTILITY.getDate"));
    catch(Exception exception)
         print.printUserMessage("DB_UTILITY", (new
    Date()).toString(), "", exception);
    throw new
    EpoolException(JB_B2B_ERROR_PARSER.getErrorMessage("epoolError",
    "Epool10005", "DB_UTILITY.getDate"));
    finally
    try
    if(con != null && !con.isClosed())
    con.close();
    catch(Exception exception2)
    stmt = null;
    con = null;
              return Date;
         public void setSessionContext(SessionContext context)
              this.context = context;
         public void ejbActivate()
         public void ejbPassivate()
         public void ejbCreate()
         public void ejbRemove()
    Also the xml files are as follows.
    web.xml
    <?xml version="1.0"?>
    <!DOCTYPE web-app PUBLIC "-//Sun Microsystems,
    Inc.//DTD Web Application 2.2//EN"
    "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
    <web-app>
    <!-- A friendly name for this web application, this name can be used in visual development environments, for instance -->
    <display-name>AddressBook Web Application</display-name>
    <!-- A human-readable description of this web application -->
    <description>Web module that contains an HTML welcome page, and 4 JSP's.</description>
    <!-- The file(s) to show when no file is specified, i.e. only the directory is specified. -->
    <welcome-file-list>
    <welcome-file>B2B_COUNTRY_CODE.jsp</welcome-file>
    </welcome-file-list>
    <ejb-ref>
    <ejb-ref-name>SB_B2B_COUNTRY_CODEHome</ejb-ref-name>
    <ejb-ref-type>Session</ejb-ref-type>
    <home>SB_B2B_COUNTRY_CODEHome</home
    <remote>SB_B2B_COUNTRY_CODERemote</remote>
    </ejb-ref></web-app>
    Application.xml
    <?xml version="1.0"?>
    <!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.2//EN" "http://java.sun.com/j2ee/dtds/application_1_2.dtd">
    <application>
    <display-name>Country Code</display-name>
    <module>
    <ejb>epool_CountryCode-ejb.jar</ejb>
    </module>
    <module>
    <web>
    <web-uri>epool_CountryCode-web.war</web-uri>
    <context-root>/epool_CountryCode-web</context-root>
    </web>
    </module>
    </application>
    ejb-jar.xml:
    <?xml version="1.0"?>
    <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd">
    <ejb-jar>
    <description>epool_CountryCode</description>
    <enterprise-beans>
    <session>
    <display-name>CountryCode Session
    Bean</display-name>
    <ejb-name>SB_B2B_COUNTRY_CODERemote</ejb-name>
    <home>SB_B2B_COUNTRY_CODEHome</home>
    <remote>SB_B2B_COUNTRY_CODERemote</remote>
    <ejb-class>SB_B2B_COUNTRY_CODE</ejb-class>
    <session-type>Stateless</session-type>
    <ejb-ref>
    <description>EJB Epool DButility</description>
         <ejb-ref-name>DB_UTILITYRemote</ejb-ref-name>
                   <ejb-ref-type>Session</ejb-ref-type>
                   <home>DB_UTILITYHome</home>
                   <remote>DB_UTILITYRemote</remote>
              </ejb-ref>
              <ejb-ref>
              <description>EJB Entity Bean</description>
    <ejb-ref-name>EB_B2B_COUNTRY_CODERemote</ejb-ref-name>
                   <ejb-ref-type>Entity</ejb-ref-type>
                   <home>EB_B2B_COUNTRY_CODEHome</home>
              <remote>EB_B2B_COUNTRY_CODERemote</remote>
              </ejb-ref>
    </session>
    <session>
    <display-name>DbUtility Session Bean</display-name>
    <ejb-name>DB_UTILITYRemote</ejb-name>
    <home>DB_UTILITYHome</home>
    <remote>DB_UTILITYRemote</remote>
    <ejb-class>DB_UTILITY</ejb-class>
    <session-type>Stateless</session-type>
    </session>
    <entity>
    <ejb-name>EB_B2B_COUNTRY_CODERemote</ejb-name>
         <home>EB_B2B_COUNTRY_CODEHome</home>
         <remote>EB_B2B_COUNTRY_CODERemote</remote>
         <ejb-class>EB_B2B_COUNTRY_CODE</ejb-class>
         <persistence-type>Container</persistence-type>
         <prim-key-class>EB_B2B_COUNTRY_CODEPK</prim-key-class>
         <reentrant>False</reentrant>
         <cmp-field>
         <field-name>country_code_desc</field-name>
         </cmp-field>
         <cmp-field>
         <field-name>phone_format_flag</field-name>
         </cmp-field>
         <cmp-field>
         <field-name>country_code</field-name>
         </cmp-field>
         <cmp-field>
         <field-name>active_date</field-name>
         </cmp-field>
         <cmp-field>
         <field-name>date_created</field-name>
         </cmp-field>
         <cmp-field>
         <field-name>active_flag</field-name>
         </cmp-field>
         <cmp-field>
         <field-name>country_phone_code</field-name>
         </cmp-field>
         <cmp-field>
         <field-name>country_tax_percent</field-name>
         </cmp-field>
         <cmp-field>
         <field-name>sort_order</field-name>
         </cmp-field>
         <cmp-field>
         <field-name>date_modified</field-name>
         </cmp-field>
         <cmp-field>
         <field-name>user_created</field-name>
         </cmp-field>
         <cmp-field>
         <field-name>user_modified</field-name>
         </cmp-field>
         <resource-ref>
         <description></description>
         <res-ref-name>jdbc/ePool</res-ref-name>
         <res-type>javax.sql.DataSource</res-type>
         <res-auth>Container</res-auth>
         </resource-ref>
    </entity>
    </enterprise-beans>
    <assembly-descriptor>
         <container-transaction>
              <method>
                   <ejb-name>EB_B2B_COUNTRY_CODERemote</ejb-name>
                   <method-name>*</method-name>
              </method>
              <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <security-role>
    <description>Users</description>
    <role-name>users</role-name>
    </security-role>
    </assembly-descriptor>
    </ejb-jar>
    The session bean which uses the above session bean is as follows.
    import javax.ejb.SessionContext;
    import javax.ejb.SessionBean;
    import java.sql.*;
    import javax.naming.Context;
    import java.sql.Timestamp;
    import java.util.Vector;
    import initcontext;
    import DB_UTILITYHome;
    import DB_UTILITYRemote;
    import EB_B2B_COUNTRY_CODEHome;
    import EB_B2B_COUNTRY_CODERemote;
    import EB_B2B_COUNTRY_CODEPK;
    * @stereotype SessionBean
    * @homeInterface SB_B2B_COUNTRY_CODEHome
    * @remoteInterface SB_B2B_COUNTRY_CODERemote
    public class SB_B2B_COUNTRY_CODE implements SessionBean
         private SessionContext context;
         * Sets the context of the bean
         * @param context The Bean's Context
         public Vector selectCountryCode(String query,String
    countquery, String pagenos) throws Exception
              Context ctx = initcontext.getContext();
              Connection con=null;
              Vector records=new Vector();
              int pageno=Integer.parseInt(pagenos);
              int min=(pageno-1)*10;
              int max=pageno*10;
              int counter=0;
              boolean recordsfound=false;     
              try
                   DB_UTILITYHome home =
    (DB_UTILITYHome)ctx.lookup("java:comp/env/DB_UTILITYRemote");
                   DB_UTILITYRemote remote =
    (DB_UTILITYRemote)home.create();
                   con=remote.getConnection();
                   Statement stmt = con.createStatement();
                   ResultSet rscount =
    stmt.executeQuery(countquery);
                   while(rscount.next())
                        int temp=rscount.getInt(1);
                        int pagecount=temp;
                        pagecount=pagecount/10;
                        if((temp%10)>0)
                        pagecount=pagecount+1;               
                        records.addElement(""+pagecount);
                   ResultSet rs = stmt.executeQuery(query);
                   while(rs.next())
                        counter++;
                        if(counter>min && counter<=max)
                             String row[]=new String[8];     
                             recordsfound=true;
                             row[0]=rs.getString(1);
                             row[1]=rs.getString(2);
                             row[2]=rs.getString(3);
                             row[3]=rs.getString(4);
                             row[4]=rs.getString(5);
                             row[5]=rs.getString(6);
                             row[6]=rs.getString(7);
                             row[7]=rs.getString(8);          
                             records.addElement(row);
              con.close();               
              catch(Exception e)
                   System.out.println("Error in selecting Country
    Code "+e);
                   throw new Exception("Error in selecting Country
    Code "+e);
              return(records);     
         public void insertCountryCode(String country_code, String
    country_code_desc, String country_phone_code, String
    phone_format_flag,String active_flag, String sort_order,String
    country_tax_percent)throws Exception
              Context ctx = initcontext.getContext();
              Double Sort_Order=null;
              Double cntry_tax_prct=null;
              if(sort_order!=null && sort_order.length()>0)          
              Sort_Order=new Double(sort_order);          
              if(country_tax_percent!=null &&
    country_tax_percent.length()>0)          
              cntry_tax_prct=new Double(country_tax_percent);
              String user_created=null;
              Timestamp date_created=null;
              Timestamp active_date=null;
              String user_modified=null;
              Timestamp date_modified=null;          
              try
                   DB_UTILITYHome dbhome =
    (DB_UTILITYHome)ctx.lookup("java:comp/env/DB_UTILITYRemote");
                   DB_UTILITYRemote dbremote =
    (DB_UTILITYRemote)dbhome.create();
                   user_created=dbremote.getUser();
    date_created=Timestamp.valueOf(dbremote.getDate());
                   active_date=date_created;
                   EB_B2B_COUNTRY_CODEHome home =
    (EB_B2B_COUNTRY_CODEHome)ctx.lookup("java:comp/env/EB_B2B_COUNTRY_CODER
    emote");
                   EB_B2B_COUNTRY_CODERemote remote =
    (EB_B2B_COUNTRY_CODERemote)home.create(country_code, country_code_desc,
    country_phone_code,active_flag, phone_format_flag,user_created,
    date_created, active_date, Sort_Order, user_modified,
    date_modified,cntry_tax_prct);                              
              catch(Exception e)
                   System.out.println("Error in Creating COUNTRY
    Code "+e);
                   throw new Exception("Error in Creating COUNTRY
    Code "+e);
         public void setSessionContext(SessionContext context)
              this.context = context;
         public void ejbActivate()
         public void ejbPassivate()
         public void ejbCreate()
         public void ejbRemove()
    The jsp client which acces the beans is as follows.
    <BODY >
    <%@ page language="java" %>
    <%@ page import="java.sql.*" %>
    <%@ page import="initcontext" %>
    <%@ page import = "java.util.*" %>
    <%@ page import="DB_UTILITYHome"%>
    <%@ page import="DB_UTILITYRemote"%>
    <%@ page import="javax.naming.*"%>
    <%Connection con=null; %>
    <script src="search_getvalues.js">
    </script>
    <form name=frm1>
    <%! int intCount,intI,intRowCount,intJ;
    String strtname=new String();
    String strhidden=new String("txthdn");
         Statement st;
         ResultSet rs;
         ResultSetMetaData rmeta;
    ....%>
    <%
    try
         Context ctx = initcontext.getContext();
         DB_UTILITYHome dbhome =
    (DB_UTILITYHome)ctx.lookup("java:comp/env/DB_UTILITYRemote");
         DB_UTILITYRemote dbremote = (DB_UTILITYRemote)dbhome.create();
         con=dbremote.getConnection();
         st=con.createStatement();
         rs=st.executeQuery(strsqlquery);
         rmeta=rs.getMetaData();
    intCount=rmeta.getColumnCount();
    ....... %>
    </form>
    </BODY>
    </HTML>
    The resulting exception generated is as follows:
    D:\oc4j\j2ee\home>java -jar orion.jar
    Auto-unpacking
    D:\oc4j\j2ee\home\applications\epool_CountryCode\build\epool_CountryCod
    e.ear... done.
    Auto-unpacking
    D:\oc4j\j2ee\home\applications\epool_CountryCode\build\epool_CountryCod
    e\epool_CountryCode-web.war... done.
    Auto-deploying epool_CountryCode (New server version detected)...
    Auto-deploying epool_CountryCode-ejb.jar (No previous deployment
    found)... done.
    Error deploying
    file:/D:/oc4j/j2ee/home/demo/messagelogger/messagelogger-ejb.jar homes:
    No javax.jms.Destination found a
    t the specified destination-location (jms/theTopic) for
    MessageDrivenBean com.evermind.logger.MessageLogger
    Oracle9iAS (1.0.2.2.1) Containers for J2EE initialized
    Auto-deploying epool countryCode example (New server version
    detected)...
    ************************1
    ************************2
    COUNT QUERY :SELECT COUNT(COUNTRY_CODE) FROM BAP_COUNTRY_CODE
    QUERY :SELECT
    COUNTRY_CODE,COUNTRY_CODE_DESC,COUNTRY_PHONE_CODE,PHONE_FORMAT_FLAG,COU
    NTRY_TAX_PERCENT ,SORT_ORDER,ACTIVE
    FLAG,ACTIVEDATE FROM BAP_COUNTRY_CODE order by COUNTRY_CODE
    Error in selecting Country Code java.rmi.RemoteException: Error
    (de-)serializing object: com.evermind.sql.OrionCMTConnec
    tion; nested exception is:
    java.io.NotSerializableException:
    com.evermind.sql.OrionCMTConnection
    JB:Error in selecting country cd java.lang.Exception: Error in
    selecting Country Code java.rmi.RemoteException: Error (d
    e-)serializing object: com.evermind.sql.OrionCMTConnection; nested
    exception is:
    java.io.NotSerializableException:
    com.evermind.sql.OrionCMTConnection
    Error in Selecting Records
    OrionCMTConnection not closed, check your code!
    LogicalDriverManagerXAConnection not closed, check your code!
    (Use -Djdbc.connection.debug=true to find out where the leaked
    connection was created)
    Auto-unpacking
    D:\oc4j\j2ee\home\applications\epool_CountryCode\build\epool_CountryCod
    e.ear... Error unpacking: IO Error:
    The system cannot find the path specified
    Error updating application epool_CountryCode: Unable to find/read
    assembly info for D:\oc4j\j2ee\home\applications\epool_C
    ountryCode\build\epool_CountryCode (META-INF/application.xml)
    But if the DBUTILITY session bean is changed to a simple bean and accessed the code works fine and i am able to retrieve the data.Is the problem there because u one session bean cannot access a database connection method from another one or could it be because of the driver???
    I hope i am clear.Please revert back in case any more references are needed.
    Thanks in advance!!!!!!

  • Accessing External Url using Http Utility | Error when using from Weblogic on Solaris

    We are using Http Utility (http://jakarta.apache.org/commons/httpclient/) from
    Apache for accessing external URL. A XML string is sent as POST parameter to the
    URL and the response is also an XML string. The URL is accessed over HTTPS protocol.
    I am setting the following parameters in the java class:
    Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
    // set the property
    System.setProperty("java.protocol.handler.pkgs","com.sun.net.ssl.internal.www.protocol");
    The java class written to access the external URL using Http Utility works perfectly
    fine when it is run from either the command line (of Windows or Solaris using
    main() ) or from weblogic on windows. The same java class throws an exception
    when run from Solaris instance of Weblogic
    2003-09-30 11:02:12,411 FATAL [com.bp.beyondbp.presentation.userregistration.action.LloydsValidator]
    EXCEPTION: com.bp.beyondbp.presentation.userregistration.exception.LlyodsValidationFailedException,
    MESSAGE: Write Channel Closed, possible SSL handshaking or trust failure;
    CAUSE: (java.io.IOException: Write Channel Closed, possible SSL handshaking or
    trust failure)
    at com.bp.beyondbp.presentation.userregistration.action.LloydsValidator.postXMLtoLloyd(LloydsValidator.java:243)
    at com.bp.beyondbp.presentation.userregistration.action.LloydsValidator.validateLlyodsForNewUser(LloydsValidator.java:95)
    at com.bp.beyondbp.presentation.userregistration.action.PreferencesActionForm.validate(PreferencesActionForm.java:326)
    at org.apache.struts.action.RequestProcessor.processValidate(RequestProcessor.java:942)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:255)
    at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
    at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    java.io.IOException: Write Channel Closed, possible SSL handshaking or trust failure
    at com.certicom.tls.record.WriteHandler.write(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown
    Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown
    Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown
    Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown
    Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown
    Source)
    at com.certicom.tls.record.ReadHandler.interpretContent(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown
    Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown
    Source)
    at com.certicom.tls.record.WriteHandler.write(Unknown Source)
    at org.apache.commons.httpclient.HttpConnection$WrappedOutputStream.write(HttpConnection.java:1344)
    at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:67)
    at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:125)
    at org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:779)
    at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2179)
    at org.apache.commons.httpclient.HttpMethodBase.processRequest(HttpMethodBase.java:2534)
    I tried to debug the problem by looking at system properties on windows and solaris,
    the difference that I found was
    On Windows
    [exec] tModelInstanceInfo_description : com.sun.net.ssl.internal.www.protocol
    On Solaris
    [exec] tModelInstanceInfo_description : weblogic.utils|weblogic.tils|weblogic.net|weblogic.management
    After this I changed the startWLS.sh on Solaris and set
    -Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol in java options.
    On looking the system properties again, the output was
    [exec] tModelInstanceInfo_description : com.sun.net.ssl.internal.www.protocol|weblogic.utils|weblogic.utils|weblogic.net|weblogic.management
    But still the error is same. Can somebody help me out here as to what is going
    wrong? Please find the java class attached for reference, please have a look at
    postXMLtoLloyd() method in the class file..
    [LloydsValidator.java]

    We are using Http Utility (http://jakarta.apache.org/commons/httpclient/) from
    Apache for accessing external URL. A XML string is sent as POST parameter to the
    URL and the response is also an XML string. The URL is accessed over HTTPS protocol.
    I am setting the following parameters in the java class:
    Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
    // set the property
    System.setProperty("java.protocol.handler.pkgs","com.sun.net.ssl.internal.www.protocol");
    The java class written to access the external URL using Http Utility works perfectly
    fine when it is run from either the command line (of Windows or Solaris using
    main() ) or from weblogic on windows. The same java class throws an exception
    when run from Solaris instance of Weblogic
    2003-09-30 11:02:12,411 FATAL [com.bp.beyondbp.presentation.userregistration.action.LloydsValidator]
    EXCEPTION: com.bp.beyondbp.presentation.userregistration.exception.LlyodsValidationFailedException,
    MESSAGE: Write Channel Closed, possible SSL handshaking or trust failure;
    CAUSE: (java.io.IOException: Write Channel Closed, possible SSL handshaking or
    trust failure)
    at com.bp.beyondbp.presentation.userregistration.action.LloydsValidator.postXMLtoLloyd(LloydsValidator.java:243)
    at com.bp.beyondbp.presentation.userregistration.action.LloydsValidator.validateLlyodsForNewUser(LloydsValidator.java:95)
    at com.bp.beyondbp.presentation.userregistration.action.PreferencesActionForm.validate(PreferencesActionForm.java:326)
    at org.apache.struts.action.RequestProcessor.processValidate(RequestProcessor.java:942)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:255)
    at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
    at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    java.io.IOException: Write Channel Closed, possible SSL handshaking or trust failure
    at com.certicom.tls.record.WriteHandler.write(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown
    Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown
    Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown
    Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown
    Source)
    at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown
    Source)
    at com.certicom.tls.record.ReadHandler.interpretContent(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown
    Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown
    Source)
    at com.certicom.tls.record.WriteHandler.write(Unknown Source)
    at org.apache.commons.httpclient.HttpConnection$WrappedOutputStream.write(HttpConnection.java:1344)
    at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:67)
    at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:125)
    at org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:779)
    at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2179)
    at org.apache.commons.httpclient.HttpMethodBase.processRequest(HttpMethodBase.java:2534)
    I tried to debug the problem by looking at system properties on windows and solaris,
    the difference that I found was
    On Windows
    [exec] tModelInstanceInfo_description : com.sun.net.ssl.internal.www.protocol
    On Solaris
    [exec] tModelInstanceInfo_description : weblogic.utils|weblogic.tils|weblogic.net|weblogic.management
    After this I changed the startWLS.sh on Solaris and set
    -Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol in java options.
    On looking the system properties again, the output was
    [exec] tModelInstanceInfo_description : com.sun.net.ssl.internal.www.protocol|weblogic.utils|weblogic.utils|weblogic.net|weblogic.management
    But still the error is same. Can somebody help me out here as to what is going
    wrong? Please find the java class attached for reference, please have a look at
    postXMLtoLloyd() method in the class file..
    [LloydsValidator.java]

  • Appc error when upgrade from weblogic sp5 to sp6

    Hi,
    I got an appc compilation error for an Entity Bean. It is exactly the same code. the generated xxxx__WebLogic_CMP_RDBMS.java compiles in weblogic8.1sp5. After upgrading to sp6, I got the following error for "cannot resolve symbol
    symbol : method setStringForClob (int,java.lang.String)
    location: interface oracle.jdbc.OraclePreparedStatement".
    I checked the generated java code. addition code is generated on sp6 which reference to oracle.jdbc.OraclePreparedStatement.setStringForClob().
    The databased used is oracle 9i. driver is oracle shipped ojdbc14.jar for 9i. If I change to 10g driver, it compiles of course. But we don't have plan to upgrade the driver.
    Would someone help me find what is wrong.
    Thanks alot
    JC

    any ideas about this problem?? i am getting the same error. is it a bug in the weblogic sp 6??
    Thanks,
    Raj

  • Migrating Application from weblogic 8.1 to weblogic 10.0 - Urgent

    Migration
    Edited by: user2647658 on Jan 5, 2009 8:49 PM

    Mukul,
    Thanks - I may appear as though I know what I'm doing, but I'm at a similar stage to you - I have to upgrade to 10.3 early next year and have so far only moved a single JVM for development use and checked my application works.
    What I learnt was that 8.1 - 10.* is a huge step, various JMS/JDBC configuration options you were used to in 8.1 have now been simplified - for example, the JDBC DataSource and Connection pool you had in 8.1 has now been replaced by a single entity.
    I'm pleased that the JDBC connection works - where does that SQL statement come from, as it looks like there's something not quite right about that.
    Now that you have that working, make a backup of the folder and try to deploy one of your applications. First off, try to do this through the WebLogic console and see what errors, if any you get. Do you have jar files on the system classpath at all in WLS8.1? If you do, you may want to stick them in the lib folder of the domain just to get it working - I don't think that's the recommended approach, but it will do as a test to see if it works.
    Upgrade Approach_
    As for the approach to upgrade, I have the same issue (although only 6 - 8 developers to worry about) Within WLS 10.* there is a scripting language called WLST, and my aim is to create a base domain for development and once that's ready all the developers will delete the existing 8.1 domain and run the wlst script to create the new one, deploy all the applications and all will work nicely. That's just what I'm aiming for and I'm a long way off at the moment.
    So, it will be an automated upgrade, but will be a brand new domain structure - 8.1 and 10 I think are so different, its difficult to make the change seamless - but WLST will help ( I hope )
    How I upgrade my production environment with clusters etc I have no idea at the moment
    let us know how you get on
    Pete

  • How to deal with security when migrating application from weblogic 5.1 to weblogic 6.1?

    Dear All,
    I have one statement int weblogic 5.1 weblogic.propertis as follow,
    weblogic.security.realmClass=com.tbcn.security.realm.TestRealm
    but after converting to weblogic 6.1 there are no corresponding statement in
    the file config.xml. And when i start the new application, error occured.
    what should I do?
    The error message is:
    <2001/8/27 am 11:33:42> <Notice> <Management> <Loading configuration file
    .\config\tbcn\config.xml
    <2001/8/27 am 11:33:49> <Emergency> <Server> <Unable to initialize the
    server: 'Fatal initializatio
    Throwable: java.lang.NullPointerException
    java.lang.NullPointerException
    at
    weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
    at
    weblogic.security.SecurityService.initialize(SecurityService.java:115)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
    at weblogic.Server.main(Server.java:35)
    '>
    The WebLogic Server did not start up properly.
    Exception raised: java.lang.NullPointerException
    java.lang.NullPointerException
    at
    weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
    at
    weblogic.security.SecurityService.initialize(SecurityService.java:115)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception

    Dear Satya,
    My weblogic propertis file as follow,
    # CORE PROPERTIES
    # You should set these before you start the WebLogic Server the first time.
    # If you need more instructions on individual properties in this
    # section, check the same section in the Optional Properties, where
    # we've left the long explanations. Or, better yet, go to our
    # website and read all about properties, at:
    # http://www.weblogic.com/docs51/admindocs/properties.html
    # CORE SYSTEM PROPERTIES
    # TCP/IP port number at which the WebLogic Server listens for connections
    weblogic.system.listenPort=7001
    # CORE SECURITY-RELATED PROPERTIES
    # Read important information about security at:
    # http://www.weblogic.com/docs51/admindocs/properties.html
    # REQUIRED: The system password MUST be set in order to start the
    # WebLogic Server. This password is case-sensitive, at least 8 characters.
    # The username for the privileged user is ALWAYS "system".
    # This username and password also includes httpd access (see
    # HTTPD properties below).
    weblogic.password.system=12345678
    # RECOMMEND Set to 'everyone' if HTTPD is enabled
    weblogic.allow.execute.weblogic.servlet=everyone
    # Set individual ACLs to restrict access to HTTP-related resources,
    # such as the Administration servlets.
    # To make your own servlets generally available, follow this
    # pattern (provide a weblogic.allow.execute) for your packages and
    # set ACLs as appropriate.
    # CORE SECURITY-RELATED PROPERTIES FOR SSL
    # Read important information about SSL at:
    # http://www.weblogic.com/docs51/classdocs/API_secure.html
    # Enable SSL
    # (default if property not defined is false)
    weblogic.security.ssl.enable=true
    # SSL listen port
    weblogic.system.SSLListenPort=7002
    # Servlets for SSL
    # Authentication servlet for creating tokens for applets
    weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationS
    ervlet
    # Limits number of unclaimed stored tokens
    weblogic.security.certificateCacheSize=3
    # Capture CA root of client servlet
    weblogic.httpd.register.AdminCaptureRootCA=admin.AdminCaptureRootCA
    # Certificates for SSL
    # Name of acceptable CA roots
    # For client authentication change value to a valid .pem file
    #weblogic.security.clientRootCA=SecureServerCA.pem
    # Server certificates for SSL
    weblogic.security.certificate.server=democert.pem
    weblogic.security.key.server=demokey.pem
    weblogic.security.certificate.authority=ca.pem
    # registration for certificate generator servlet
    weblogic.httpd.register.Certificate=utils.certificate
    weblogic.allow.execute.weblogic.servlet.Certificate=system
    # CORE HTTPD ADMINISTRATIVE PROPERTIES
    # True permits the HTTPD to run (default)
    # Uncomment this property to disable HTTPD
    #weblogic.httpd.enable=false
    # If authentication is required, add username/password for each user
    # who will be included in an ACL, as in this commented-out example:
    #weblogic.password.peter=#8gjsL4*
    # SYSTEM PROPERTIES
    # System properties in this section are set to system defaults
    # Performance pack. The shared library must be accessible from your
    # PATH (NT) or from your shared library path (UNIX; the name of the
    # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
    weblogic.system.nativeIO.enable=true
    # Outputs logging information to the console as well as to the log file
    weblogic.system.enableConsole=true
    # Sets the directory or URL for the WebLogic Admin help pages
    # The help pages are shipped in the "docs/adminhelp" directory, in the
    # default document root in public_html
    weblogic.system.helpPageURL=/weblogic/myserver/public_html/docs51/adminhelp/
    # If you prefer to access the most recent help pages, you can do so online
    # by commenting out the previous property and uncommenting this one:
    #weblogic.system.helpPageURL=http://www.weblogic.com/docs51/adminhelp/
    # Properties for tuning the server's performance
    # Number of WebLogic Server execute threads.
    weblogic.system.executeThreadCount=15
    # Other optional system properties
    # Limits size of weblogic.log (in K) and versions old log
    weblogic.system.maxLogFileSize=1024
    # Adjust minimum length of password
    weblogic.system.minPasswordLen=8
    # UNIX only: If running on port 80 on UNIX, enable the setUID program
    #weblogic.system.enableSetUID=false
    # UNIX only: Unprivileged user to setUID to after starting up
    # WebLogic Server on port 80
    #weblogic.system.nonPrivUser=nobody
    # CLUSTER-SPECIFIC PROPERTIES
    # Cluster-specific properties in this section are set to system defaults.
    # CLUSTER USERS: Note that ALL Cluster-specific properties should be set
    # in the per-cluster properties file ONLY.
    # Time-to-live (number of hops) for the cluster's multicast messages
    # (default 1, range 1-255).
    #weblogic.cluster.multicastTTL=1
    # Sets the load-balancing algorithm to be used between
    # replicated services if none is specified. If not specified,
    # round-robin is used.
    #weblogic.cluster.defaultLoadAlgorithm=round-robin
    # SERVER-SPECIFIC CLUSTER PROPERTIES
    # Cluster-related properties in this section are set to system defaults.
    # CLUSTER USERS: Note that these server-specific cluster-related properties
    # should be set in the per-server properties file ONLY.
    # Sets the weight of the individual server for the weight-based
    load-balancing.
    # Range is 0 - 100.
    # Larger numbers increase the amount of traffic routed to this server.
    #weblogic.system.weight=100
    # SYSTEM STARTUP FILES - Examples
    # CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
    # objects should be registered in the per-server properties file.
    # All other startup classes should be registered in the per-cluster
    # properties file.
    # For more info on writing and using startup file, see the
    # Developers Guide "Writing a WebLogic Client application," at
    # http://www.weblogic.com/docs51/classdocs/API_t3.html
    # Register a startup class by giving it a virtual name and
    # supplying its full pathname.
    #weblogic.system.startupClass.[virtual_name]=[full_pathname]
    # Add arguments for the startup class
    #weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
    # This example shows the entry for examples/t3client/StartupQuery.java
    #weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
    #weblogic.system.startupArgs.doquery=\
    # query=select * from emp,\
    # db=jdbc:weblogic:pool:demoPool
    # SYSTEM SHUTDOWN FILES - Examples
    # For more info on writing and using shutdown file, see the
    # Developers Guide "Writing a WebLogic Client application," at
    # http://www.weblogic.com/docs51/classdocs/API_t3.html
    # Register a shutdown class by giving it a virtual name and
    # supplying its full pathname.
    #weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
    # Add arguments for the shutdown class
    #weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
    # This example shows the entry for examples/t3client/ShutdownTest.java
    #weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
    #weblogic.system.shutdownArgs.ShutdownTest=\
    # outfile=c:/temp/shutdown.log
    # SECURITY-RELATED PROPERTIES FOR WORKSPACES
    # For backward compatibility, the following entries disable Access
    # Control on Workspaces
    weblogic.allow.read.weblogic.workspace=everyone
    weblogic.allow.write.weblogic.workspace=everyone
    # JOLT FOR WEBLOGIC PROPERTIES
    # These properties configure a BEA Jolt connection pool for use with
    # the simpapp and bankapp examples, and register a servlet for use with
    # with the simpapp example. The default server address provided here
    # points to a public TUXEDO server that is hosted by BEA for use with
    # this example.
    # Servlet registration for simpapp example:
    #weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServle
    t
    # Pool creation and cleanup
    # note this example is set up to work with the public
    # demo TUXEDO server available from BEA's website:
    #weblogic.system.startupClass.demojoltpoolStart=\
    # bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
    #weblogic.system.startupArgs.demojoltpoolStart=\
    # poolname=demojoltpool,\
    # appaddrlist=//beademo1.beasys.com:8000,\
    # failoverlist=//beademo1.beasys.com:8000,\
    # minpoolsize=1,\
    # maxpoolsize=3
    #weblogic.system.shutdownClass.demojoltpoolStop=\
    # bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
    #weblogic.system.shutdownArgs.demojoltpoolStop=\
    # poolname=demojoltpool
    # WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
    # The registrations enable a BEA IIOP connection pool and
    # register servlets for use with the simpapp and university examples.
    # Configure for your environment and uncomment to use.
    # Uncommenting these properties requires WebLogic Enterprise Connectivity
    # and an operating WebLogic Enterprise Server.
    # Servlet registration for simpapp servlet example
    #weblogic.httpd.register.SimpappServlet=\
    # examples.wlec.servlets.simpapp.SimpappServlet
    #weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
    # Servlet registration for simpapp EJB example
    # (You'll need to add the wlec_ejb_simpapp.jar to the
    # weblogic.ejb.deploy property in this file.)
    #weblogic.httpd.register.ejbSimpappServlet=\
    # examples.wlec.ejb.simpapp.ejbSimpappServlet
    #weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
    # Pool creation and cleanup for the simpapp example
    #weblogic.CORBA.connectionPool.simplepool=\
    # appaddrlist=//wlehost:2468,\
    # failoverlist=//wlehost:2468,\
    # minpoolsize=2,\
    # maxpoolsize=3,\
    # username=wleuser,\
    # userrole=developer,\
    # domainname=simpapp
    # Servlet registration for university Servlet example:
    #weblogic.httpd.register.UniversityServlet=\
    # examples.wlec.servlets.university.UniversityServlet
    #weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
    # Pool creation and cleanup for the University example:
    #weblogic.CORBA.connectionPool.Univpool=\
    # appaddrlist=//wlehost:2498,\
    # failoverlist=//wlehost:2498,\
    # minpoolsize=2,\
    # maxpoolsize=3,\
    # username=wleuser,\
    # userrole=developer,\
    # apppassword=wlepassword,\
    # domainname=university
    # WEBLOGIC FILE PROPERTIES
    # Maps a volume name to a path, for client file read/write
    #weblogic.io.fileSystem.[volumeName]=[fullPathName]
    # WEBLOGIC JMS DEMO PROPERTIES
    # CLUSTER USERS: Note that ALL JMS deployment should be done in the
    # per-cluster properties file ONLY.
    # You set up a JDBC connection pool if you want persistent messages
    # (including durable subscriptions). To use JMS and EJBs in the same
    # transaction, both must use the same JDBC connection pool. Uncomment
    # the following property to use the default JDBC connection pool
    # 'demo', which is defined in the Demo connection pool section of this file.
    #weblogic.jms.connectionPool=demoPool
    # The JMS Webshare example demonstrates how the ClientID for a
    # durable subscriber is configured in the connection factory:
    #weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
    #weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
    #weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
    #weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
    # The JMS trader example shows how to use JMS with an EJB. In addition
    # to uncommenting the following properties, you must also set up and
    # deploy the EJB example examples.ejb.basic.statelessSession.Trader in
    # ejb_basic_statelessSession.jar to try out this JMS example:
    #weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
    #weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
    #weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
    #weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
    # Registers the underlying servlet
    #weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
    # These properties are used with the ServerReceive JMS example,
    # which demonstrates how to establish a JMS message consumer
    # in a startup class:
    #weblogic.system.startupClass.serverReceive=\
    # examples.jms.startup.ServerReceive
    #weblogic.system.startupArgs.serverReceive=\
    # connectionFactory=javax.jms.TopicConnectionFactory,\
    # topic=javax.jms.exampleTopic
    # These properties are used with the PoolReceive JMS example,
    # which demonstrates how to establish a pool of JMS message consumers
    # in a startup class:
    #weblogic.system.startupClass.poolReceive=\
    # examples.jms.startup.PoolReceive
    #weblogic.system.startupArgs.poolReceive=\
    # connectionFactory=javax.jms.TopicConnectionFactory,\
    # topic=javax.jms.exampleTopic
    #weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone
    # WEBLOGIC RMI DEMO PROPERTIES
    # CLUSTER USERS: Note that pinned RMI objects should be registered
    # in the per-server properties file ONLY. All other RMI startup
    # classes should be registered in the per-cluster properties file.
    # Remote classes registered at startup after the pattern:
    #weblogic.system.startupClass.[virtualName]=[fullPackageName]
    # These examples can be compiled to see RMI in action. Uncomment to use:
    #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
    #weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
    #weblogic.system.startupClass.stock=examples.rmi.stock.StockServer
    # WEBLOGIC EJB DEMO PROPERTIES
    # CLUSTER USERS: Note that ALL EJB deployment should be done in the
    # per-cluster properties file ONLY.
    # See WebLogic Demo Connection Pool below for a connection pool
    # to use with these examples.
    # Deploys EJBeans. Uncomment the appropriate lines below and
    # modify DBMS-related info and paths to match your particular installation:
    # TBCN EJB PROPERTIES
    weblogic.ejb.deploy=\
    C:/weblogic/myserver/AccountSB.jar, \
    C:/weblogic/myserver/AddressEntryDet.jar, \
    C:/weblogic/myserver/AddressEntry.jar, \
    C:/weblogic/myserver/Affiliate.jar, \
    C:/weblogic/myserver/ContactPerson.jar, \
    C:/weblogic/myserver/ContactSB.jar, \
    C:/weblogic/myserver/Factory.jar, \
    C:/weblogic/myserver/FactorySups.jar, \
    c:/weblogic/myserver/LoginUsers.jar, \
    c:/weblogic/myserver/Member.jar, \
    c:/weblogic/myserver/MemberQuotaUsage.jar,\
    c:/weblogic/myserver/MemberToCategory.jar,\
    c:/weblogic/myserver/Organization.jar, \
    c:/weblogic/myserver/Person.jar, \
    c:/weblogic/myserver/QuotaType.jar,\
    c:/weblogic/myserver/Registration.jar, \
    c:/weblogic/myserver/TempAccounts.jar, \
    c:/weblogic/myserver/TempDomain.jar, \
    c:/weblogic/myserver/UserAccount.jar, \
    c:/weblogic/myserver/UserRole.jar, \
    c:/weblogic/myserver/BuyerProducts.jar, \
    c:/weblogic/myserver/Catalog.jar, \
    c:/weblogic/myserver/Categories.jar, \
    c:/weblogic/myserver/CategoryToCategory.jar, \
    c:/weblogic/myserver/CountryToCategory.jar, \
    c:/weblogic/myserver/InvitedMember.jar, \
    c:/weblogic/myserver/ProductOrigin.jar, \
    c:/weblogic/myserver/ProductOtherFee.jar,\
    c:/weblogic/myserver/ProductSups.jar, \
    c:/weblogic/myserver/Products.jar,\
    c:/weblogic/myserver/ProductToCategory.jar, \
    c:/weblogic/myserver/SecondaryQcEntry.jar, \
    c:/weblogic/myserver/CodeClass.jar,\
    c:/weblogic/myserver/ConfirmationSB.jar, \
    c:/weblogic/myserver/PurchasedPackage.jar,\
    c:/weblogic/myserver/RejectReasonCode.jar, \
    c:/weblogic/myserver/ServiceOrder.jar,\
    c:/weblogic/myserver/ServiceOrderLog.jar,\
    c:/weblogic/myserver/ServiceOrderState.jar,\
    c:/weblogic/myserver/ServiceOrderType.jar,\
    c:/weblogic/myserver/ServicePackageDetails.jar, \
    c:/weblogic/myserver/ServicePackage.jar, \
    c:/weblogic/myserver/ServicePayment.jar, \
    c:/weblogic/myserver/ServiceReqSB.jar, \
    c:/weblogic/myserver/TAM.jar, \
    c:/weblogic/myserver/SubscriptionEB.jar, \
    c:/weblogic/myserver/PostingCategoryEB.jar, \
    c:/weblogic/myserver/PostingBrowsedEB.jar, \
    c:/weblogic/myserver/PostingInfoEB.jar, \
    c:/weblogic/myserver/TransactionLogEB.jar, \
    c:/weblogic/myserver/PostingSB.jar
    #weblogic.ejb.deploy=\
    # d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
    # d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
    # d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
    # d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
    # d:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
    # d:/weblogic/myserver/ejb_extensions_readMostly.jar, \
    # d:/weblogic/myserver/ejb_subclass.jar, \
    # d:/weblogic/myserver/jolt_ejb_bankapp.jar
    # Servlet used by the EJB basic beanManaged example
    # Uncomment to use:
    weblogic.httpd.register.beanManaged=\
    examples.ejb.basic.beanManaged.Servlet
    # Add a list of users (set the password with
    weblogic.password.[username]=XXX)
    # to set an ACL for this servlet:
    #weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
    #weblogic.password.user1=user1Password
    #weblogic.password.user2=user2Password
    # WEBLOGIC XML DEMO PROPERTIES
    # These properties are required to run the XML examples.
    # Uncomment to use.
    # CLUSTER USERS: Note that ALL servlets should be set up
    # in the per-cluster properties file ONLY.
    #weblogic.httpd.register.StockServlet=examples.xml.http.StockServlet
    # BizTalk example properties
    #weblogic.jms.queue.tradeIncoming=biztalk.jms.tradeIncoming
    #weblogic.jms.queue.tradeError=biztalk.jms.tradeError
    #weblogic.httpd.register.BizTalkServer=examples.xml.biztalk.BizHttpProtocolA
    dapter
    #weblogic.httpd.initArgs.BizTalkServer=bizQueue=biztalk.jms.tradeIncoming
    # WEBLOGIC ZAC DEMO PROPERTIES
    # These registrations enable the ZAC Publish Wizard.
    weblogic.zac.enable=true
    # Set the publish root for a WebLogic Server. Edit and
    # uncomment to use.
    #weblogic.zac.publishRoot=d:/weblogic/zac
    # Set an ACL for each package you publish. The [name] is
    # the "Package name" you assign in the ZAC Publish Wizard.
    # Publish a package, edit this property, and uncomment to use.
    #weblogic.allow.read.weblogic.zac.[name]=[user list]
    #weblogic.allow.write.weblogic.zac.[name]=system
    # HTTPD ADMINISTRATIVE PROPERTIES
    # Enables logging of HTTPD info in common log format and
    # sets the log file name (default is "access.log" in "myserver")
    weblogic.httpd.enableLogFile=true
    weblogic.httpd.logFileName=access.log
    # Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
    weblogic.httpd.enableEvents=false
    # Enables HTTP sessions
    weblogic.httpd.session.enable=true
    # Sets an optional cookie name. The default name is "WebLogicSession".
    # Prior to version 4.0, the default was "TengahSession". To make
    # this backward compatible with cookies generated from previous
    # installations, you should set this property to "TengahSession".
    # Uncomment this line and set this to any string of your choice,
    # or comment out this property to use the default.
    #weblogic.httpd.session.cookie.name=WebLogicSession
    # MIME types
    weblogic.httpd.mimeType.text/html=html,htm
    weblogic.httpd.mimeType.image/gif=gif
    weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
    weblogic.httpd.mimeType.application/pdf=pdf
    weblogic.httpd.mimeType.application/zip=zip
    weblogic.httpd.mimeType.application/x-java-vm=class
    weblogic.httpd.mimeType.application/x-java-archive=jar
    weblogic.httpd.mimeType.application/x-java-serialized-object=ser
    weblogic.httpd.mimeType.application/octet-stream=exe
    weblogic.httpd.mimeType.text/vnd.wap.wml=wml
    weblogic.httpd.mimeType.text/vnd.wap.wmlscript=wmls
    weblogic.httpd.mimeType.application/vnd.wap.wmlc=wmlc
    weblogic.httpd.mimeType.application/vnd.wap.wmlscriptc=wmlsc
    weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
    # In seconds, the keep-alive for HTTP and HTTPS requests
    weblogic.httpd.http.keepAliveSecs=60
    weblogic.httpd.https.keepAliveSecs=120
    # WEBLOGIC JDBC DRIVER PROPERTIES
    # Enables JDBC driver logging and sets the file name for the log
    # The weblogic.jdbc.logFile is placed in the per-server
    # directory (default is "myserver")
    weblogic.jdbc.enableLogFile=false
    weblogic.jdbc.logFileName=jdbc.log
    # WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
    # CLUSTER USERS: Note that ALL JDBC connection pools should be set up
    # in the per-cluster properties file ONLY.
    # For creating JDBC connection pools. This example shows a connection
    # pool called "oraclePool" that allows 3 T3Users "guest," "joe," and "jill"
    # to use 4 JDBC connections (with a potential for up to 10 connections,
    # incremented by two at a time, with a delay of 1 second between each
    # attempt to connect to the database), to an Oracle database server called
    # "DEMO." If more than 4 connections are opened, after 15 minutes, unused
    # connections are dropped from the pool until only 4 connections remain
    open.
    # Every 10 minutes, any unused connections in the pool are tested and
    # refreshed if they are not viable.
    #weblogic.jdbc.connectionPool.oraclePool=\
    # url=jdbc:weblogic:oracle,\
    # driver=weblogic.jdbc.oci.Driver,\
    # loginDelaySecs=1,\
    # initialCapacity=4,\
    # maxCapacity=10,\
    # capacityIncrement=2,\
    # allowShrinking=true,\
    # shrinkPeriodMins=15,\
    # refreshMinutes=10,\
    # testTable=dual,\
    # props=user=SCOTT;password=tiger;server=DEMO
    # Get more details on each argument for this property in the
    # Administrators Guide on setting properties at:
    # http://www.weblogic.com/docs51/admindocs/properties.html
    # Set up ACLs for this connection pool with the following:
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
    # guest,joe,jill
    #weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
    # joe,jill
    #weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\
    # joe,jill
    # This property is an ACL that specifies the users who can
    # create dynamic connection pools:
    #weblogic.jdbc.connectionPoolcreate.admin=joe,jill
    # Read more about setting up and using connection pools in the
    # developers guide for WebLogic JDBC at:
    # http://www.weblogic.com/docs51/classdocs/API_jdbct3.html#T5a
    # TBCN JDBC CONNECTION POOL MANAGEMENT
    weblogic.jdbc.connectionPool.oraclePool=\
    url=jdbc:oracle:thin:@202.109.102.151:1521:tbcn,\
    driver=oracle.jdbc.driver.OracleDriver,\
    loginDelaySecs=1,\
    initialCapacity=2,\
    maxCapacity=10,\
    capacityIncrement=2,\
    allowShrinking=true,\
    shrinkPeriodMins=15,\
    refreshMinutes=10,\
    testTable=dual,\
    props=user=tbcn;password=ca91768
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
    weblogic.jdbc.TXDataSource.oracleDataSource=oraclePool
    weblogic.jdbc.DataSource.oracleReadOnlyDataSource=oraclePool
    # WEBLOGIC DEMO CONNECTION POOL PROPERTIES
    # CLUSTER USERS: Note that ALL JDBC connection pools should be set up
    # in the per-cluster properties file ONLY.
    # This connection pool uses the sample Cloudscape database shipped
    # with WebLogic. Used by the EJBean, JHTML, JSP and JMS examples.
    # Uncomment to use:
    #weblogic.jdbc.connectionPool.demoPool=\
    # url=jdbc:cloudscape:demo,\
    # driver=COM.cloudscape.core.JDBCDriver,\
    # initialCapacity=1,\
    # maxCapacity=2,\
    # capacityIncrement=1,\
    # props=user=none;password=none;server=none
    # Add a TXDataSource for the connection pool:
    #weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.demoPool=demoPool
    # Add an ACL for the connection pool:
    #weblogic.allow.reserve.weblogic.jdbc.connectionPool.demoPool=everyone
    # WEBLOGIC HTTP SERVLET PROPERTIES
    # CLUSTER USERS: Note that ALL servlets should be set up
    # in the per-cluster properties file ONLY.
    # WebLogic offers different types of servlets for various uses.
    # Classpath servlet registration
    # The ClasspathServlet is used to serve classes from
    # the system CLASSPATH. It is used by applets to load
    # classes they depend upon, and is registered against
    # the virtual name 'classes' here by default. This means
    # you should set your applet codebase to "/classes".
    # You can register multiple virtual names for this servlet.
    # Note that it can also be used to serve other
    # resources/files from the system CLASSPATH.
    # Don't confuse the ClasspathServlet with the ServletServlet. The
    # ClasspathServlet is used for serving classes for client-side Java only.
    # The ServletServlet is used to invoke unregistered servlets.
    # See the Administrators Guide "Setting up WebLogic as an HTTP server"
    # http://www.weblogic.com/docs51/admindocs/http.html#classfile for more
    info.
    weblogic.httpd.register.classes=weblogic.servlet.ClasspathServlet
    # We also set an open ACL for everyone to call the ClasspathServlet
    # so that applets work without requiring further changes.
    weblogic.allow.execute.weblogic.servlet.classes=everyone
    # File servlet registration
    # FileServlet searches below the documentRoot for the requested file
    # and serves it if found. If the requested file is a directory,
    # FileServlet will append the defaultFilename to the requested path
    # and serve that file if found.
    weblogic.httpd.register.file=weblogic.servlet.FileServlet
    weblogic.httpd.initArgs.file=defaultFilename=index.html
    weblogic.httpd.indexFiles=zh_TW/index.htm
    # ServerSideInclude servlet registration
    # SSIServlet searches below the documentRoot for the
    # requested .shtml file and serves it if found.
    weblogic.httpd.register.*.shtml=weblogic.servlet.ServerSideIncludeServlet
    # Example URL: http://localhost:7001/portside/welcome.shtml
    # for the file /weblogic/myserver/public_html/portside/welcome.shtml
    # PageCompileServlet (used by JHTML)
    # See the information below under WebLogic JHTML
    # JSPServlet (used by JSP)
    # See the information below under WebLogic JSP
    # ServletServlet registration
    # Allows unregistered servlets in the servlet classpath (see Servlet
    # reload properties below) to be r

  • Migrating Application from Weblogic 8 to WEblogic 10

    I am trying to migrate the application built for weblogic 8 add am getting errors:
    <5/12/2008 09:27:50 AM EST> <Error> <J2EE> <BEA-160197> <Unable to load descriptor /opt/weblogic/bea/user_projects/domains/sandpit/servers/AdminServer/tmp/.appmergegen_1228429662483_diy.ear/diy.war/WEB-INF/weblogic.xml of module diy.war. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:260)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:774)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:395)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:745)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:754)
    at weblogic.servlet.internal.WebAppDescriptor.getWeblogicWebAppBean(WebAppDescriptor.java:164)
    at weblogic.servlet.utils.WarUtils.getWlWebAppBean(WarUtils.java:104)
    at weblogic.application.compiler.WARModule.processLibraries(WARModule.java:330)
    at weblogic.application.compiler.WARModule.merge(WARModule.java:426)
    at weblogic.application.compiler.flow.MergeModuleFlow.compile(MergeModuleFlow.java:23)
    at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
    at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96)
    at weblogic.application.compiler.ReadOnlyEarMerger.merge(ReadOnlyEarMerger.java:49)
    at weblogic.application.compiler.flow.AppMergerFlow.mergeInput(AppMergerFlow.java:94)
    at weblogic.application.compiler.flow.AppMergerFlow.compile(AppMergerFlow.java:47)
    at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
    at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96)
    at weblogic.application.compiler.AppMerge.runBody(AppMerge.java:142)
    at weblogic.utils.compiler.Tool.run(Tool.java:158)
    at weblogic.utils.compiler.Tool.run(Tool.java:115)
    at weblogic.application.compiler.AppMerge.merge(AppMerge.java:154)
    at weblogic.deploy.api.internal.utils.AppMerger.merge(AppMerger.java:79)
    at weblogic.deploy.api.internal.utils.AppMerger.getMergedApp(AppMerger.java:60)
    at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createDeployableObject(WebLogicDeployableObjectFactoryImpl.java:184)
    at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createLazyDeployableObject(WebLogicDeployableObjectFactoryImpl.java:151)
    at weblogic.deploy.api.tools.SessionHelper.inspect(SessionHelper.java:646)
    at com.bea.console.actions.app.install.Flow.appSelected(Flow.java:459)
    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.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:870)
    at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:809)
    at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:478)
    at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:306)
    at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:336)
    at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:52)
    at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044)
    at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:64)
    After trying to find out about that i saw that there might be problems with
    1>weblogic.xml
    2>ejb-jar.xml
    3>application.xml
    Would you know how i could modify them to make it compatible with weblogic 10?

    It's likely that something in your weblogic.xml is invalid according to the schema. If you have a tool that can validate XML against a schema, then do that. It should point to the problem. Otherwise, if you show the entire contents of the file here, we might be able to see what the problem is.

  • Error while extracting from weblogic binary

    Hi,
    I am getting the following error when I try to run
    the downloaded weblogic binary server910_solaris32.bin
    onto my solaris 9 sparc64 machine -
    " End-of-central-directory signature not found.
    ** Error during init, error code = 2."
    Any ideas what could be wrong ?
    Thanks,
    harrynm

    Got same results though tried several times.
    Updated well  from DSO after Changing from transformation to  update rule.
    Think the transformation is some problem.
    Thanks a lot...
    dongsun, choi

  • Migrating Application from Weblogic to JBOSS

    Hi all,
    I have an requirement to migrate Application running in Weblogic 8.1 to JBOSS, However my biggest problem is i do not have my JSP files and have only JSP converted Class files which are currently decomplied JAVA files and used in place of JSP. While migating to JBOSS my JSP converted JAVA files are erroring out.
    Can any body please help me out. Thanks in advance for the help.

    can be any body help me out with this issue

  • Error migrating user from on-premises Exchange to Exchange online

    We have a hybrid configuration with our on-premises Exchange 2010 server and our Office 365 Exchange Online server (if this should be posted in the Exchange 2010 forum instead, let me know, but I figured we have one of each).  We have been doing remote
    moves, and all but two of them are finished. The two remaining are refusing to go, and I've done extensive searching but haven't been able to resolve the issues.
    The first mailbox returns this error message:
    Error: MissingExchangeGuidException: The user object for ‎nnn
    does not have a valid ExchangeGuid property and cannot be migrated.
    The second mailbox returns this error message:
    Error: MigrationTransientException: Couldn‎'t find a move request that corresponds to the specified identity
    <‎identity>.
    We've tried moving both mailboxes several times (deleting the migration batch after each error) with no luck.   The migration for both of these users are being done as separate batches with one user in each batch.  They are being created via the
    Exchange Admin Center from the Office 365 admin portal.  Any suggestions on what to do next?

    Hi Dave,
    I have gone thorough your query, its ok. Pplease follow this informative article that provides the steps Mailbox Migration to Exchange Online : https://technet.microsoft.com/en-us/library/jj863291%28v=exchg.150%29.aspx
    In addition if you want to move mailboxes automatically you may also have a look on
    Lepide Exchange Recovery Manager that could be a good alternative solution for you.
    It is complete disaster recovery, backup restoration, and Exchange to Exchange or Exchange to Office 365 migration tool and one stop solution.

  • Error migrating database from 4.0.1 to 4.1

    Hi,
    When i'm trying to apply sql script generated by migrationTool.jar i'm getting stuck at this error!
    ERROR 1062 (23000) at line 1: Duplicate entry '' for key 'PRIMARY'
    Can anyone help me with my update?
    Thank's

    If you are going to the trouble of migrating from 4.0.X, I'd go all the way to 5.2 and ditch VMS and Win2K if you can.
    If you have to use the same machine, the upgrade process "will allow you
    to import your V4.x configuration items into the newly installed V5.0 system. It
    will also allow you to migrate V4.x hosts to V5.0." (taken from the install guide).
    I believe the migration information is stored in the \Program Files\Ciscopx\csamc\migration\export folder.
    Tom

  • Migrating Application from weblogic 10 to weblogic12c

    Got the below error on th console.
    <Jan 4, 2014 3:11:01 PM IST> <Error> <HTTP> <BEA-101216> <Servlet: "Faces Servlet" failed to preload on startup in Web application: "/sdmcore".
    java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory
            at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:725)
            at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:239)
            at javax.faces.webapp.FacesServlet.init(FacesServlet.java:164)
            at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:337)
            at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:288)
            Truncated. see log file for complete stacktrace
    web.xml is
    <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
    version="2.5">
    <listener>
      <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>
    </listener>
    <filter>
      <filter-name>Seam Filter</filter-name>
      <filter-class>org.jboss.seam.servlet.SeamFilter</filter-class>
    </filter>
    <filter-mapping>
      <filter-name>Seam Filter</filter-name>
      <url-pattern>*.seam</url-pattern>
    </filter-mapping>
    <servlet>
      <servlet-name>Seam Resource Servlet</servlet-name>
      <servlet-class>org.jboss.seam.servlet.SeamResourceServlet</servlet-class>
    </servlet>
    <servlet-mapping>
      <servlet-name>Seam Resource Servlet</servlet-name>
      <url-pattern>/seam/resource/*</url-pattern>
    </servlet-mapping>
    <servlet>
      <servlet-name>Faces Servlet</servlet-name>
      <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
      <load-on-startup>1</load-on-startup>
    </servlet>
    <servlet-mapping>
      <servlet-name>Faces Servlet</servlet-name>
      <url-pattern>*.seam</url-pattern>
    </servlet-mapping>
    <servlet>
      <servlet-name>Document Store Servlet</servlet-name>
      <servlet-class>org.jboss.seam.document.DocumentStoreServlet</servlet-class>
    </servlet>
    <servlet-mapping>
      <servlet-name>Document Store Servlet</servlet-name>
      <url-pattern>*.pdf</url-pattern>
    </servlet-mapping>
    <context-param>
      <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
      <param-value>.xhtml</param-value>
    </context-param>
    <context-param>
      <param-name>facelets.DEVELOPMENT</param-name>
      <param-value>false</param-value>
    </context-param>
    <context-param>
      <param-name>facelets.REFRESH_PERIOD</param-name>
      <param-value>5</param-value>
    </context-param>
    <context-param>
      <param-name>facelets.SKIP_COMMENTS</param-name>
      <param-value>true</param-value>
    </context-param>
    <context-param>
      <param-name>facelets.LIBRARIES</param-name>
      <param-value>/WEB-INF/sdmcss.taglib.xml</param-value>
    </context-param>
    <session-config>
      <session-timeout>30</session-timeout>
    </session-config>
      <error-page>
      <error-code>403</error-code>
      <location>/login-error.html</location>
    </error-page>
    <security-constraint>
      <web-resource-collection>
       <web-resource-name>sdmcore</web-resource-name>
       <url-pattern>/sdmcore/*</url-pattern>
       <http-method>GET</http-method>
       <http-method>PUT</http-method>
       <http-method>POST</http-method>
       <http-method>DELETE</http-method>
      </web-resource-collection>
      <auth-constraint>
       <role-name>SDM</role-name>
      </auth-constraint>
    </security-constraint>
    <login-config>
      <auth-method>CLIENT-CERT</auth-method>
    </login-config>
      <security-role>
      <role-name>SDM</role-name>
    </security-role>
    </web-app>
    weblogic.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <wls:weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
    <wls:context-root>sdmcore</wls:context-root>
    <!-- <wls:container-descriptor>
      <wls:prefer-web-inf-classes>true</wls:prefer-web-inf-classes>
    </wls:container-descriptor> -->
    <wls:security-role-assignment>
       <wls:role-name>SDM</wls:role-name>
       <wls:principal-name>SDM</wls:principal-name>
    </wls:security-role-assignment>
    <wls:library-ref>
        <wls:library-name>jsf</wls:library-name>
        <wls:specification-version>1.2</wls:specification-version>
        <wls:implementation-version>1.2</wls:implementation-version>
        <wls:exact-match>false</wls:exact-match>
      </wls:library-ref>
    </wls:weblogic-web-app>
    IMP: Deployed the jsf1.2.war bundled with weblogic12.1.2 and have referred it here in the weblogic.xml
    Please help me to solve this problem.
    Thanks in Advance.

    Got the solution for this..
    Hope it helps someone searching for a solution.
    Edited the weblogic-application.xml and added the lines:
    Add in
    weblogic-application.xml :
    <prefer-application-packages>
    <package-name>javax.faces.*</package-name>
    <package-name>com.sun.faces.*</package-name>
    <package-name>com.bea.faces.*</package-name>
    </prefer-application-packages>
    <prefer-application-resources>
    <resource-name>javax.faces.*</resource-name>
    <resource-name>com.sun.faces.*</resource-name>
    <resource-name>com.bea.faces.*</resource-name>
    <resource-name>META-INF/services/javax.servlet.ServletContainerInitializer</resource-name>
    </prefer-application-resources>
    And added
    jsf-api-1.2_04-p02.jar inside the ear - APP-INF - lib folder.
    And now the application is working as expected.
    Message was edited by: 52d6a700-53d3-4ffc-9ecf-dd125927a735

  • Error migrating Security from Shared Services.

    Hi,
    I was using Hyperion Planning 9.3.1's in Import/ Export utility in D:\Hyperion\common\utilities\CSSImportExportUtility\cssimportexport\importexport\CSSExport.bat. I'm trying to export Security from Shared Services into xml format. I get the following error message:
    Malformed \uxxxx encoding
    Anyone with similar experiences? Hyperion's impexp.pdf makes the steps so complicated!!

    Answering my own question:
    Since I am in Windows, I was using backslashes in my paths when I updated file:
    importexport.properties
    The error went away after I changed the backslashes to forward slashes in all paths.

  • Migrating application from weblogic 8.1 to Sunone server

    I need to migrate enterprise application, currently deplyed in Weblogic 8.1, to Sunone server 7 or 8. Please provide some documentation help or if any tool is there to do that.
    Thanks

    There is a migration tool developed specifically for migration off WebLogic. Check out the following URL:
    http://java.sun.com/j2ee/tools/migration/index.html

  • Migrate source from weblogic 8.1.5 to weblogic 9.2

    Hi,
    I have to migrate an application running on weblogic 8.1.5 to weblogic 9.2
    I have read multiple documents on how to upgrade the domain with wizard and with the database.
    But i dont know how to convert the .jpf pageflows to .java pageflows.
    Can anybody point to what wizard/tool i have to use

    Open the workshot, create any workspace.
    then go to import->Other->Select workshop 8.1 application. This will upgrade your code and import you 8.1 app in to 9.2 app.
    Make sure that all page flow JSPs has been upgraded correctly. There should not be any and BEA taglib used for netui tags. They are all changed to Beehieves.
    If you still see that JSPs are using bea tag libs, then select the project, right click on it and select upgrade.
    I hope this helps.

Maybe you are looking for