Debugging deployment in iPlanet Application Server6.5

Can any one help me out the proper and efficient way of debugging the deployment process in iPlanet application server 6.5 .Where i can look out for the
debug outputs while deploying

You can use the -verbose (iasdeploy deployapp -verbose fortune.ear) option while deploying your application. This will give you some additional information on the debugging process.
Hope that helps
Vasanth

Similar Messages

  • Whether Iplanet Application server6.0/6.5 supports EJB2.0

    I doubt that whether Iplanet Application Server supports
    EJB2.0 Features.
    Please reply ASAP.

    no it does not support ejb 2.0 ..
    ejb 2.0 is expected to be supported in the next major version release ..

  • Migration guide from Iplanet application server

    Hi ,
    i would like to migrate application to oracle 9ias application server.Curently we are using iplanet application server6.5.
    From where do i get some useful documents.
    In oracle 9ias faqs , its written that its available on http://ias.us.oracle.com.But the site is not opening up.
    If some one has already tried migration please suggest to us as how to do.
    Thanks in advance
    smita

    Please refer to the following url:
    http://www.sun.com/migration/sunonetools.html
    This should give u a head start on what needs to be done and how,. WIth respect to webserver , i guess you can use it or leave it depending on the architecture you require to deploy your solution.
    Hope this helps !

  • Steps to deploy an ejb application and running an ejb client in weblogic server6.1

    steps to deploy an ejb application and steps to run an ejb client in weblogic server6.1
    if the client is an simple java application and if the client is a servlet

    Hi.
    Check out the beanManaged example that ships with WLS and read the accompanying docs. This
    is a simple EJB with a servlet that invokes it.
    Michael
    shekhar sachdev wrote:
    steps to deploy an ejb application and steps to run an ejb client in weblogic server6.1
    if the client is an simple java application and if the client is a servlet--
    Michael Young
    Developer Relations Engineer
    BEA Support

  • Deploying war file on iplanet application server 6.5

    Hi ,
    We are trying to deploy WebObjects application on Iplanet Application server server 6.5.
    Steps we tried for deployment :
    1) War file generated by WebObjects.
    2) Started IPlanet Application server.
    3) Opened the War file in the deployment tool.
    4) Verified that the WAR file to be deployed using the verify option in the deployment tool(Verified successfully)
    5) We tried to save the archive, then it throws an error saying "
    "Invalid entry compressed size (expected 52 bytes but got 51 bytes)".
    We ignored this message and proceeded further by clicking on OK.
    6) Deployed the WAR file using the deploy option
    7) In the deploy message box, it diplays that the application was deployed successfully.
    Then we tried to access the application by trying the following url : " http://localhost/NASApp/<CONTEXT NAME>/WebObjects/<APPLICATION NAME>"
    (eg : http://localhost/NASApp/SampleApplication/WebObjects/SampleApplication.woa>)
    We are getting the error saying that " GXError". We are not sure whether the the above mentioned url is the correct way to access the application !
    What we think the problem in deployment is
    i) because of error while saving the WAR file (Invalid entry compressed size (expected 52 bytes but got 51 bytes)
    ii) URL not appropriate
    Other observations :
    We tried to deploy to deploy sample application on Iplanet Application server. All these sample applications are deployed properly without the above mentioned error message. All these application are accessed by typing following url : " http:localhost/NASApp/<CONTEXT NAME>/<APPLICATION NAME>". IN all the sample application, url contains "NASApp" . We are not sure what this stand for and maps to. What we assumed is that it maps to the the iplanet app document root i.e "installedroot/ias6/ias/App"
    The exception throw while saving the WAR file is " com.iplanet.ias.tools.buzz.util.ArchiveHandlerException"
    Has any body who has tried this can help us?
    Thanks,
    Raju and Venkatesh

    Hi,
    First of all the application you are trying is from a WebObjects application server. I don't know how they package the modules and what is the format/file structure. I just went to their site, though they say that the WebObjects applications can be deploy on any J2EE Application server but still how they package and how they write the xml descriptors is not known.
    Looking at your exception it seem that first it is something to do the war/jar archive file compression thing (as the deployment tool is not able to read the complete file) then comes the deployment descriptors.
    I tried to get a few sample application from their site but I couldn't fine any, it will be great help if you can provide a WebObjects sample app to me (mail it to [email protected]).
    Regarding the NASApp string in URL, it has nothing to do with document root of iAS and also installedroot/ias6/ias/APPS dir is not the document root of iPlanet app server, this is the place where it save/explodes all the archives (ear).
    See iPlanet App server don't have any HTTP daemon to listen to the HTTP requests, so it needs a web server with a plugin (web connector) to forward the HTTP requests meant for iAS, and this NASApp string in the URL is the key to that.
    All the URLs are first send to the iAS plugin (as configured in web server's obj.conf file) and plugin look for this NASApp string (configurable), if it is there in the URL then it converts the HTTP request and send it to iAS over a proprietary protocol (KCP), otherwise it gives the request as it is to web server to process it.
    The NASApp string is a iAS registry parameter which you can change any time. And generally the context root part of the URL is the war file name (by default). So the typical URL for any web application (MyWeb.war) will be:
    http://<host>:<port>/NASApp/MyWeb/<Servlet_name>.
    I don't know why that extension "*.woa" is there. So if you send me a sample war file, I will be able to try it out.
    Please feel free to ask further questions.
    Sanjeev,
    Developer Support, Sun ONE Application Server-India.

  • Flex error while deploying a VC application

    Hi Experts,
    Though I have rarely worked on VC developments, I have to troubleshoot an issue wherein we are getting following error while deploying a VC Application.
    Error: Error in compiling flex application. Consult log file for details.
    I have got a log file and it has written out 100s of lines of log, however, following is the important part from the log file:
    #00145E9635CE0060000016940015E0C60004A07BE7C55172#1302353936732#/System/Server/VCServer
    #sap.com/VisualComposerServerEar04
    #com.sap.portal.vc.server#ganeshb#35216##n/a##b1528d4062a811e0aedc00145e9635ce
    #SAPEngine_Application_Thread[impl:3]_12##0#0#Debug#1#/System/Server/VCServer#Plain###
    Server Error:Failed to import model - attribute is missing in imported file bytes are <?xml version="1.0" encoding="UTF-8"?>
    Any help on how to resolve this?
    Thanks in advance,
    Ameya
    Edited by: Ameya Pimpalgaonkar on Nov 16, 2011 7:31 AM

    Hi Ameya,
         If its VC 7.0 then you must be using Flash Compiler.Try changing the compiler to Flash at this path
    Tools->Options->Compiler->Change 'Runtime filed to Flash'.I hope this should solve your problem.
    Naga

  • Error while deploying the Composite Application ERROR: (SOAPBC_START_1)

    Hi,
    I have a EJB web service created and deployed in GlassFish. I have created a BPEL which will recieve from the web service and then insert into a SQL table. To track the messages I have also created to File WSDLs to save the WS message and the DB message.
    While deploying the Composite application I am recieving this error. "Component: sun-http-binding
    ERROR: (SOAPBC_START_1) HTTPBC-E00205: Start failed. java.lang.Exception: LifecycleException: PWC3985: Protocol handler initialization failed: java.net.BindException: Already bound: 8080
    Can anyone tell me what this is error is all about ??
    Regards,
    Jai

    This is the Glassfish Server log
    Nov 8, 2008 4:01:16 PM com.sun.enterprise.admin.servermgmt.launch.ASLauncher buildCommand
    INFO:
    C:/Program Files/Java/jdk1.6.0_06\bin\java
    -Dcom.sun.aas.instanceRoot=C:/Program Files/glassfish-v2ur2/domains/domain1
    -Dcom.sun.aas.ClassPathPrefix=
    -Dcom.sun.aas.ClassPathSuffix=
    -Dcom.sun.aas.ServerClassPath=
    -Dcom.sun.aas.classloader.appserverChainJars.ee=
    -Dcom.sun.aas.classloader.appserverChainJars=admin-cli.jar,admin-cli-ee.jar,j2ee-svc.jar
    -Dcom.sun.aas.classloader.excludesList=admin-cli.jar,appserv-upgrade.jar,sun-appserv-ant.jar
    -Dcom.sun.aas.classloader.optionalOverrideableChain.ee=
    -Dcom.sun.aas.classloader.optionalOverrideableChain=webservices-rt.jar,webservices-tools.jar
    -Dcom.sun.aas.classloader.serverClassPath.ee=/lib/hadbjdbc4.jar,C:/Program Files/glassfish-v2ur2/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,/lib/dbstate.jar,/lib/hadbm.jar,/lib/hadbmgt.jar,C:/Program Files/glassfish-v2ur2/lib/SUNWmfwk/lib/mfwk_instrum_tk.jar
    -Dcom.sun.aas.classloader.serverClassPath=C:/Program Files/glassfish-v2ur2/lib/install/applications/jmsra/imqjmsra.jar,C:/Program Files/glassfish-v2ur2/imq/lib/jaxm-api.jar,C:/Program Files/glassfish-v2ur2/imq/lib/fscontext.jar,C:/Program Files/glassfish-v2ur2/imq/lib/imqbroker.jar,C:/Program Files/glassfish-v2ur2/imq/lib/imqjmx.jar,C:/Program Files/glassfish-v2ur2/lib/ant/lib/ant.jar,C:/Program Files/glassfish-v2ur2/lib/SUNWjdmk/5.1/lib/jdmkrt.jar
    -Dcom.sun.aas.classloader.sharedChainJars.ee=appserv-se.jar,appserv-ee.jar,jesmf-plugin.jar,/lib/dbstate.jar,/lib/hadbjdbc4.jar,jgroups-all.jar,C:/Program Files/glassfish-v2ur2/lib/SUNWmfwk/lib/mfwk_instrum_tk.jar
    -Dcom.sun.aas.classloader.sharedChainJars=javaee.jar,C:/Program Files/Java/jdk1.6.0_06/lib/tools.jar,install/applications/jmsra/imqjmsra.jar,com-sun-commons-launcher.jar,com-sun-commons-logging.jar,C:/Program Files/glassfish-v2ur2/imq/lib/jaxm-api.jar,C:/Program Files/glassfish-v2ur2/imq/lib/fscontext.jar,C:/Program Files/glassfish-v2ur2/imq/lib/imqbroker.jar,C:/Program Files/glassfish-v2ur2/imq/lib/imqjmx.jar,C:/Program Files/glassfish-v2ur2/imq/lib/imqxm.jar,webservices-rt.jar,webservices-tools.jar,mail.jar,appserv-jstl.jar,jmxremote_optional.jar,C:/Program Files/glassfish-v2ur2/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,activation.jar,appserv-rt.jar,appserv-admin.jar,appserv-cmp.jar,C:/Program Files/glassfish-v2ur2/updatecenter/lib/updatecenter.jar,C:/Program Files/glassfish-v2ur2/jbi/lib/jbi.jar,C:/Program Files/glassfish-v2ur2/imq/lib/imqjmx.jar,C:/Program Files/glassfish-v2ur2/lib/ant/lib/ant.jar,dbschema.jar
    -Dcom.sun.aas.configName=server-config
    -Dcom.sun.aas.configRoot=C:/Program Files/glassfish-v2ur2/config
    -Dcom.sun.aas.defaultLogFile=C:/Program Files/glassfish-v2ur2/domains/domain1/logs/server.log
    -Dcom.sun.aas.domainName=domain1
    -Dcom.sun.aas.installRoot=C:/Program Files/glassfish-v2ur2
    -Dcom.sun.aas.instanceName=server
    -Dcom.sun.aas.processLauncher=SE
    -Dcom.sun.aas.promptForIdentity=true
    -Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
    -Dcom.sun.enterprise.overrideablejavaxpackages=javax.help,javax.portlet
    -Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
    -Dcom.sun.enterprise.taglisteners=jsf-impl.jar
    -Dcom.sun.updatecenter.home=C:/Program Files/glassfish-v2ur2/updatecenter
    -Ddomain.name=domain1
    -Dhttp.nonProxyHosts=localhost|127.0.0.1|jnambiar2
    -Dhttp.proxyHost=web-proxy.atl.hp.com
    -Dhttp.proxyPort=8088
    -Dhttps.proxyHost=web-proxy.atl.hp.com
    -Dhttps.proxyPort=8088
    -Djava.endorsed.dirs=C:/Program Files/glassfish-v2ur2/lib/endorsed
    -Djava.ext.dirs=C:/Program Files/Java/jdk1.6.0_06/lib/ext;C:/Program Files/Java/jdk1.6.0_06/jre/lib/ext;C:/Program Files/glassfish-v2ur2/domains/domain1/lib/ext;C:/Program Files/glassfish-v2ur2/javadb/lib
    -Djava.library.path=C:\Program Files\glassfish-v2ur2\lib;C:\Program Files\glassfish-v2ur2\lib;C:\Program Files\glassfish-v2ur2\bin;C:\Program Files\glassfish-v2ur2\lib
    -Djava.security.auth.login.config=C:/Program Files/glassfish-v2ur2/domains/domain1/config/login.conf
    -Djava.security.policy=C:/Program Files/glassfish-v2ur2/domains/domain1/config/server.policy
    -Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
    -Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
    -Djavax.net.ssl.keyStore=C:/Program Files/glassfish-v2ur2/domains/domain1/config/keystore.jks
    -Djavax.net.ssl.trustStore=C:/Program Files/glassfish-v2ur2/domains/domain1/config/cacerts.jks
    -Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
    -Djmx.invoke.getters=true
    -Dsun.rmi.dgc.client.gcInterval=3600000
    -Dsun.rmi.dgc.server.gcInterval=3600000
    -client
    -XX:+UnlockDiagnosticVMOptions
    -XX:MaxPermSize=192m
    -Xmx512m
    -XX:NewRatio=2
    -XX:+LogVMOutput
    -XX:LogFile=C:/Program Files/glassfish-v2ur2/domains/domain1/logs/jvm.log
    -cp
    C:/Program Files/glassfish-v2ur2/lib/jhall.jar;C:\Program Files\glassfish-v2ur2\lib\appserv-launch.jar
    com.sun.enterprise.server.PELaunch
    start
    Starting Sun Java System Application Server 9.1_02 (build b04-fcs) ...
    MBeanServer started: com.sun.enterprise.interceptor.DynamicInterceptor
    CORE5098: AS Socket Service Initialization has been completed.
    CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.6.0_06] from [Sun Microsystems Inc.]
    SEC1002: Security Manager is OFF.
    C:/Program Files/glassfish-v2ur2/domains/domain1/config/.__com_sun_appserv_pid
    ADM0001:SunoneInterceptor is now enabled
    SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.
    WEB0114: SSO is disabled in virtual server [server]
    WEB0114: SSO is disabled in virtual server [__asadmin]
    ADM1079: Initialization of AMX MBeans started
    ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://jnambiar2.asiapacific.hpqcorp.net:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors
    ADM1506: Status of Standard JMX Connector: Active = [true]
    JBIFW0010: JBI framework ready to accept requests.
    WEB0302: Starting Sun-Java-System/Application-Server.
    WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8080
    WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8181
    WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 4848
    SMGT0007: Self Management Rules service is enabled
    Application server startup complete.
    Registered Status Provider MBean for sun-jdbc-binding.
    Registered Status Provider MBean for sun-sql-engine.
    JBISE6013: JavaEEServiceEngine : Java EE Service Engine started successfully.
    JBIFW1146: Engine sun-javaee-engine has been started.
    Registered runtime configuration MBean for sun-jdbc-binding.
    Registered runtime configuration MBean for sun-sql-engine.
    HTTPBC-R00100: sun-http-binding starting
    FILBC-LCY0006: Component sun-file-binding started (outbound).
    FILBC-LCY0005: Component sun-file-binding started (inbound).
    Started outbound.
    SQLSE started.
    JBIFW1146: Engine sun-sql-engine has been started.
    Started outbound receiver.
    Receiver started.
    Receiver started.
    FILBC-LCY0003: Component sun-file-binding started with the following configuration:
    specification-version: 1.0
    build-number: 080408_1
    Threads: 10
    JBIFW1146: Binding sun-file-binding has been started.
    Started inbound receiver.
    JDBC Binding component started.
    JBIFW1146: Binding sun-jdbc-binding has been started.
    PWC3982: Cannot register MBean for the Protocol
    grizzlyHttpProtocol.selectorRegisterProtocol
    WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 9080
    XSLTSE-5001:Initialized XSLT service engine successfully!
    XSLTSE-5002:Started XSLT service engine successfully!
    JBIFW1146: Engine sun-xslt-engine has been started.
    HTTPBC-E00153: Failed to read the descriptor file for identity information; descriptor file is 'C:\Program Files\glassfish-v2ur2\domains\domain1\jbi\components\sun-http-binding\install_root/META-INF/jbi.xml'
    java.net.MalformedURLException: unknown protocol: c
    at java.net.URL.<init>(URL.java:574)
    at java.net.URL.<init>(URL.java:464)
    at java.net.URL.<init>(URL.java:413)
    at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:650)
    at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:186)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:771)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
    at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107)
    at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:225)
    at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283)
    at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:180)
    at com.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle.identity(HttpSoapBindingLifeCycle.java:1103)
    at com.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle.logComponentInfo(HttpSoapBindingLifeCycle.java:1075)
    at com.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle.start(HttpSoapBindingLifeCycle.java:476)
    at com.sun.jbi.framework.ComponentFramework.startComponent(ComponentFramework.java:1846)
    at com.sun.jbi.framework.ComponentFramework.startComponent(ComponentFramework.java:1792)
    at com.sun.jbi.framework.ComponentOperation.process(ComponentOperation.java:233)
    at com.sun.jbi.framework.Operation.run(Operation.java:104)
    at java.lang.Thread.run(Thread.java:619)
    HTTPBC-R00101: sun-http-binding started with the following configuration:
    specification-version: unknown
    build-number: unknown
    OutboundThreads (max outbound threads): 10
    HttpDefaultPort: 9080
    HttpsDefaultPort: 9181
    AMConfigDir:
    ProxyType: DIRECT
    ProxyHost:
    ProxyPort: 0
    NonProxyHosts: localhost|127.0.0.1
    ProxyUserName:
    UseJVMProxySettings: false
    ApplicationVariables: {  }
    ApplicationConfigurations: {  }
    JBIFW1146: Binding sun-http-binding has been started.
    EJBSCLookup:: sc.getEjbContainerAvailabilityEnabledFromConfig() ==> false
    JTS5014: Recoverable JTS instance, serverId = [3700]
    About to load the system app: MEjbApp
    POARemoteRefFactory checking if SFSBVersionPolicy need to be added
    EJBSCLookup:: sc.getEjbContainerAvailabilityEnabledFromConfig() ==> false
    POARemoteRefFactory addSFSBVersionPolicy? false
    POARemoteRefFactory checking if SFSBVersionPolicy need to be added
    EJBSCLookup:: sc.getEjbContainerAvailabilityEnabledFromConfig() ==> false
    POARemoteRefFactory addSFSBVersionPolicy? false
    LDR5010: All ejb(s) of [MEjbApp] loaded successfully!
    About to load the system app: __ejb_container_timer_app
    EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]
    LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!
    BPJBI-5001:BPEL service engine initialized
    BPJBI-5002:Starting BPEL service engine
    BPELSEInOutThread.Started_BPEL_service_engine_in-out_thread
    BPELSEInOutThread.Started_BPEL_service_engine_in-out_thread
    BPELSEInOutThread.Started_BPEL_service_engine_in-out_thread
    BPELSEInOutThread.Started_BPEL_service_engine_in-out_thread
    BPELSEInOutThread.Started_BPEL_service_engine_in-out_thread
    BPELSEInOutThread.Started_BPEL_service_engine_in-out_thread
    I18N:
    BPJBI-5003: BPEL service engine started with following configurations:
    Persistence Enabled : false
    Monitor Enabled : false
    Persistence Database NonXA JNDI ResourceName : jdbc/bpelseNonXA
    Persistence Database XA JNDI Resource Name : jdbc/bpelseXA
    Engine Expiry Interval (failover setting) : 60 seconds
    Debug Enabled : false
    Debug Port : 3,343
    Thread Count 10
    Engine Installed on Application Server Cluster : false
    BPELSEInOutThread.Started_BPEL_service_engine_in-out_thread
    BPELSEInOutThread.Started_BPEL_service_engine_in-out_thread
    BPELSEInOutThread.Started_BPEL_service_engine_in-out_thread
    BPELSEInOutThread.Started_BPEL_service_engine_in-out_thread
    JBIFW1146: Engine sun-bpel-engine has been started.
    JBIMA0452: Successfully processed 0 Service Assemblies during startup.
    JBIFW0012: JBI framework startup complete.
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.XWS_ClientProvider.property.signature.key.alias"
    javax.management.InstanceNotFoundException: No object matches the specified name "domain.applications.lifecycle-module.JBIFramework.property.com.sun.jbi.home"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.XWS_ServerProvider.property.encryption.key.alias"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ClientProvider.property.security.config"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ClientProvider.property.encryption.key.alias"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ServerProvider.property.security.config"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.applications.lifecycle-module.JBIFramework.property.com.sun.jbi.home"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ClientProvider.property.dynamic.username.password"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ServerProvider.property.signature.key.alias"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.XWS_ClientProvider.property.dynamic.username.password"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.XWS_ClientProvider.property.encryption.key.alias"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ClientProvider.property.signature.key.alias"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.ServerProvider.property.encryption.key.alias"
    javax.management.InstanceNotFoundException: No object matches the specified name "server.security-service.message-security-config.SOAP.provider-config.XWS_ServerProvider.property.signature.key.alias"
    wsgen successful
    DPL5306:EJB Web Service Endpoint [HPAdaptorWS] listening at address [http://jnambiar2.asiapacific.hpqcorp.net:8080/HPAdaptorWSDLService/HPAdaptorWS]
    deployed with moduleid = HPAdaptorWSEJB
    Container com.sun.enterprise.webservice.JAXWSContainer@1fae7b1 doesn't support class com.sun.xml.ws.api.server.Module
    LDR5010: All ejb(s) of [HPAdaptorWSEJB] loaded successfully!
    The log message is null.
    javax.ejb.EJBException
    at com.sun.ejb.containers.BaseContainer.processSystemException(BaseContainer.java:3869)
    at com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:3769)
    at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:3571)
    at com.sun.ejb.containers.WebServiceInvocationHandler.invoke(WebServiceInvocationHandler.java:200)
    at $Proxy62.hpAdaptorWSDLOperation(Unknown Source)
    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:597)
    at com.sun.enterprise.webservice.InvokerImpl.invoke(InvokerImpl.java:81)
    at com.sun.enterprise.webservice.EjbInvokerImpl.invoke(EjbInvokerImpl.java:82)
    at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:146)
    at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:257)
    at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
    at com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
    at com.sun.enterprise.webservice.MonitoringPipe.process(MonitoringPipe.java:147)
    at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
    at com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
    at com.sun.enterprise.webservice.CommonServerSecurityPipe.processRequest(CommonServerSecurityPipe.java:218)
    at com.sun.enterprise.webservice.CommonServerSecurityPipe.process(CommonServerSecurityPipe.java:129)
    at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
    at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
    at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
    at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
    at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
    at com.sun.enterprise.webservice.Ejb3MessageDispatcher.handlePost(Ejb3MessageDispatcher.java:113)
    at com.sun.enterprise.webservice.Ejb3MessageDispatcher.invoke(Ejb3MessageDispatcher.java:87)
    at com.sun.enterprise.webservice.EjbWebServiceServlet.dispatchToEjbEndpoint(EjbWebServiceServlet.java:226)
    at com.sun.enterprise.webservice.EjbWebServiceServlet.service(EjbWebServiceServlet.java:155)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    at com.sun.enterprise.web.AdHocContextValve.invoke(AdHocContextValve.java:114)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:87)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
    at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:272)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
    at com.sun.enterprise.web.portunif.PortUnificationPipeline$PUTask.doTask(PortUnificationPipeline.java:380)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
    at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
    Caused by: java.lang.UnsupportedOperationException: Message Recieved Successfully
    at hp.adaptor.gateway.HPAdaptorWS.hpAdaptorWSDLOperation(HPAdaptorWS.java:22)
    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:597)
    at com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1067)
    at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:176)
    at com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.java:2895)
    at com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:3986)
    at com.sun.ejb.containers.WebServiceInvocationHandler.invoke(WebServiceInvocationHandler.java:189)
    ... 63 more
    EJB5018: An exception was thrown during an ejb invocation on [HPAdaptorWS]
    javax.ejb.EJBException
    at com.sun.ejb.containers.BaseContainer.processSystemException(BaseContainer.java:3869)
    at com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:3769)
    at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:3571)
    at com.sun.ejb.containers.WebServiceInvocationHandler.invoke(WebServiceInvocationHandler.java:200)
    at $Proxy62.hpAdaptorWSDLOperation(Unknown Source)
    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:597)
    at com.sun.enterprise.webservice.InvokerImpl.invoke(InvokerImpl.java:81)
    at com.sun.enterprise.webservice.EjbInvokerImpl.invoke(EjbInvokerImpl.java:82)
    at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:146)
    at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:257)
    at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
    at com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
    at com.sun.enterprise.webservice.MonitoringPipe.process(MonitoringPipe.java:147)
    at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
    at com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
    at com.sun.enterprise.webservice.CommonServerSecurityPipe.processRequest(CommonServerSecurityPipe.java:218)
    at com.sun.enterprise.webservice.CommonServerSecurityPipe.process(CommonServerSecurityPipe.java:129)
    at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
    at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
    at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
    at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
    at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
    at com.sun.enterprise.webservice.Ejb3MessageDispatcher.handlePost(Ejb3MessageDispatcher.java:113)
    at com.sun.enterprise.webservice.Ejb3MessageDispatcher.invoke(Ejb3MessageDispatcher.java:87)
    at com.sun.enterprise.webservice.EjbWebServiceServlet.dispatchToEjbEndpoint(EjbWebServiceServlet.java:226)
    at com.sun.enterprise.webservice.EjbWebServiceServlet.service(EjbWebServiceServlet.java:155)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    at com.sun.enterprise.web.AdHocContextValve.invoke(AdHocContextValve.java:114)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:87)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
    at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:272)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
    at com.sun.enterprise.web.portunif.PortUnificationPipeline$PUTask.doTask(PortUnificationPipeline.java:380)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
    at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
    Caused by: java.lang.UnsupportedOperationException: Message Recieved Successfully
    at hp.adaptor.gateway.HPAdaptorWS.hpAdaptorWSDLOperation(HPAdaptorWS.java:22)
    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:597)
    at com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1067)
    at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:176)
    at com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.java:2895)
    at com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:3986)
    at com.sun.ejb.containers.WebServiceInvocationHandler.invoke(WebServiceInvocationHandler.java:189)
    ... 63 more
    Deploying service assembly HPAdapatorInboundCAwithFault to target server.
    Cannot find CatalogManager.properties
    Retrieving document at 'C:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HPAdapatorInboundCAwithFault\HPAdapatorInboundCAwithFault-sun-file-binding\sun-file-binding\HPAdaptorInboundBPEL\DBMessageFile.wsdl'.
    Retrieving document at 'C:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HPAdapatorInboundCAwithFault\HPAdapatorInboundCAwithFault-sun-file-binding\sun-file-binding\HPAdaptorInboundBPEL\MsgInbound_DB.wsdl'.
    Retrieving document at 'C:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HPAdapatorInboundCAwithFault\HPAdapatorInboundCAwithFault-sun-file-binding\sun-file-binding\HPAdaptorInboundBPEL\Partners\HPAdaptorWSDLService\HPAdaptorWS.wsdl'.
    Retrieving document at 'C:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HPAdapatorInboundCA

  • Context lookup problem in iplanet application server 6.0 sp3?

    Hi all,
    I am writing codes in the following enviornment, iplanet application server 6.0 sp3 with iplanet web server 4.1 sp7 in Window 2000.
    When I tried to login to the system, error occured when i try to lookup context for my session bean.
    The error message is as follows:
    login_process.jsp: Home / Remote Error:String index out of range: -7
    [10/Apr/2002 18:09:10:5] error: Exception: SERVLET-execution_failed: Error in ex
    ecuting servlet JSPRunnerSticky: java.util.EmptyStackException
    Exception Stack Trace:
    java.util.EmptyStackException
    at java.util.Stack.peek(Stack.java:86)
    at java.util.Stack.pop(Stack.java:68)
    at com.netscape.server.deployment.AppComponentDescriptorUtil.popCurrentAppComponent(Unknown Source)
    at com.netscape.server.servlet.servletrunner.AppInfo.popWebAppDescriptor(Unknown Source)
    at com.netscape.server.servlet.servletrunner.ServletInfo.service(Unknown Source)
    at com.netscape.server.servlet.servletrunner.ServletRunner.execute(Unknown Source)
    at com.kivasoft.applogic.AppLogic.execute(Unknown Source)
    at com.kivasoft.applogic.AppLogic.execute(Unknown Source)
    at com.kivasoft.thread.ThreadBasic.run(Native Method)
    at java.lang.Thread.run(Thread.java:479)
    could anyone suggest a method to solve the problem?
    Thx very much!

    There is a major security breach in authenticating
    iPlanet Web Server 6.0 SP3 and SP4 using Sun ONE
    Directory Server. Using a valid user id, any
    password except null string would allow user access
    the restricted resources. iPlanet Web Server 6.0 SP5
    and 4.1 SP12 worked fine with similar configuration.Did you get an answer for this?
    We are having the exact same problems with our iPlanet Web server 6.0 SP3.
    thank you.

  • IPlanet Application Server 6.0 Service Pack 3 Test Drive

    Hi,
    We are trying to port an existing web-app (runs on WebLogic and JBoss)
    to the iPlanet Application Server platform.
    We can deploy our app, but cannot access it once it is deployed.
    Is the iPlanet Application Server 6.0 Service Pack 3 Test Drive "cripple
    ware" or is it a fully functioning trial which allows you deploy new
    apps to it?
    Thank You,
    Eric Kahler

    Hello,
    If the issue is looking up the bean and you are looking up the bean as you
    would with JBoss or BEA:
    String beanName = "Bean";
    ctx = InitialContext();
    ctx.lookup( beanName );
    then you might have the problem there. Atleast this is what we have found
    with beans needing to be convered. Change the lookup to be ctx.lookup
    ("ejb/" + beanName ); and you might be better. I haven't tried it on JBoss
    or Bean but ctx.lookup( "java:comp/env/ejb/" + beanName) might work on all
    the different app servers
    TTYL, Jeff
    "Eric Kahler" <[email protected]> wrote in message
    news:[email protected]..
    Hi,
    We are trying to port an existing web-app (runs on WebLogic and JBoss)
    to the iPlanet Application Server platform.
    We can deploy our app, but cannot access it once it is deployed.
    Is the iPlanet Application Server 6.0 Service Pack 3 Test Drive "cripple
    ware" or is it a fully functioning trial which allows you deploy new
    apps to it?
    Thank You,
    Eric Kahler

  • Understand​ing TestStand Debug Deployment License

    After reading the License Agreement and the TestStand Help section on licenses I still would like an explanation as to exactly what the license does and does not allow. My understanding is with a TestStand Debug/Deployment license I can install TestStand on a machine, let's call it the development machine, and also install TestStand on another machine, my production machine. The development machine is where I would develop applications to deploy onto my production machine. The production machine is where I would actually test my products. The production machine can also be used as a platform to debug my deployed applications. If this is true then can I develop any additional tests on the production machine, e.g. I found a problem in the sequence so I need to add a new sequence to correct the error? Or I found a problem with a LabVIEW VI and I need to create a new VI to correct it. Can I develop VI's and sequences on the production machine or do I need to develop on the development machine transfer the files over to the production machine and hope it works (this type of process could prove to be very time consuming and tedious)?

    Thanks for the info. Now what about LabVIEW. Here are some options I'm considering:
    1. Run a LabVIEW Runtime Engine on the production machine and a FDS of LabVIEW on the development machine. In turn run a TestStand Deployment license on the production machine. This seems the most cost effective method. The problem I'm having is some VI's are developed in LabVIEW 6i, 7.0, and 7.1 and the LabVIEW 7.0 RT Engine does not work with TestStand 3.1. It seems only the LabVIEW 7.1 RT Engine will work with TestStand 3.1. But I don't have a LabVIEW 7.1 development license (not sure how the 7.1 VI's came to be, before my time). I've also thought of using standalone LabVIEW applications but the only license I have for Application Builder is from LabVIEW 6i PDS from the Developer's Suite. If TestStand 3.1 is suppose to work with any LabVIEW RT engine then I'm doing something wrong.
    2. Run a LabVIEW Development/Deployment license with a TestStand Development/Deployment license. This is the most expensive method but the easiest to implement.
    3. Run a LabVIEW FDS and a TestStand Deployment license on the production machine.
    A finally question, does NI make available a TestStand Run-time Engine that is available as a free download, similar to the LabVIEW Run-Time Engine?

  • 0x800705AA error code while deploying win store application. Insufficient resources.

    Hi,
    I'm getting the error while deploying win store application in debug mode. I checked the space - it is not the issue. Is is possible to check/clean the disk space associated with the user account? Is this a problem? If yes, how to clean it?
    Thanks
    Vlad

    Did you ever get an answer on this?  I have the same problem, and have had 3 different level 1 and level 2 Microsoft Techs work on this, with no fix.  Always the same answer - refresh Windows.  It's amazing how these techs can't zero in
    on a root cause for anything.

  • Weblogic.Deployer using -deploy for existing application

    I'm running on weblogic 8.1 SP3
    when I use -deploy for an existing application the documentation says it will do a redeploy.
    documentation for the targets option says that it will use existing targets for an application that is currently deployed.
    BUT it doesn't work. Is this a known issue ?
    I use the following options:
    -name fortune
    -source /data/bea81/applications/stg/fortune.ear
    -verbose -debug -deploy -stage

    Check to see if the problem is with the Deployer tool or myApp.war:
    1) Does myApp.war deploy using the console?
    2) Check myApp.war has all the classes it needs?
    If your app does deploy from the console then we can focus in on the Deploy tool. If not it may help give us a clue as to what is going on e.g. your war file missing classes.
    Hoos

  • BIBeans deployment    and Iplanet

    Can BIBeans be deployed on Iplanet Web server 6?
    Is there some examples in Otn?
    Thanks, Paolo Forin

    BI Beans has not tested been tested on iPlanet servers, however, as BI Beans applications are fully J2EE compliant there is no reason why applications developed using BI Beans should not work correctly within an iPlanet environment.
    Alas, we have no specific documentation covering deployment to iPlanet servers.
    Hope this helps
    Business Intelligence Beans Product Management Team
    Oracle Corporation

  • Deploying an ADF application as part of an EAR

    I have an ADF application that should be deployed as part of an EAR. The components of this EAR are assembled in Ant and part of an EAR deployment profile. When I right click on the adfc-config.xml file and choose run, I want JDeveloper to deploy the entire application, not just the webapp. How do I do this? I don't see any clear directions for this. It appears I would have to click on the Application menu and select Deploy which doesn't cause the browser to open when the deployment is complete.

    When you right click and choose run a virtual EAR in exploded form is created for you in the system.xx.xx.xx.\o.j2ee\drs\<application> directory. This is equivalent to what you would do when clicking on the application menu and selecting deploy. This is done for you to make debugging and testing an app easier from within JDeveloper. If you look in the online help for"Integrated Weblogic Server" you can find more details on this feature.

  • Deploy BC4J/JSP applications on OC4J

    I am trying to deploy JDeveloper3.2 BC4J/JSP applications on OC4J. However, I have no lucky at all. My OC4J will hang when I tried to run my JSP applications.
    Does this only happen to me? Any suggestion will be appreciated.
    null

    I've followed the instructions in the "How TO Deploy a BC4J Application to an Oracle9iAS J2EE Container in Local Mode" again. The OC4J still hung. I turn on the -Djbo.debugoutput switch this time. I used the following line to startup the OC4J.
    java -Djbo.debugoutput=console -cp C:\oc4j\j2ee\home\orion.jar;
    C:\oc4j\j2ee\home\lib\classes12.jar;
    C:\JDev3.2_BC4Jlib\xmlparserv2.jar;
    C:\JDev3.2_BC4Jlib\jdev-rt.zip;
    C:\JDev3.2_BC4Jlib\jbojdbcpatch.zip;
    C:\JDev3.2_BC4Jlib\connectionmanager.zip;
    C:\JDev3.2_BC4Jlib\jbohtml.zip;
    C:\JDev3.2_BC4Jlib\jboimdomains.zip;
    C:\JDev3.2_BC4Jlib\ordim817.zip;
    C:\JDev3.2_BC4Jlib\ordvir817.zip;
    C:\JDev3.2_BC4Jlib\ordhttp.zip;
    C:\JDev3.2_BC4Jlib\jbomt.zip;
    C:\JDev3.2_BC4Jlib\jbodomorcl.zip;
    C:\JDev3.2_BC4Jlib\jboremote.zip;
    C:\JDev3.2_BC4Jlib\jndi.jar;
    C:\JDev3.2_BC4Jlib\jbodatum12.zip;
    C:\JDev3.2_BC4Jlib\;
    C:\JDev3.2_BC4Jlib\bc4j_scott.jar
    com.evermind.server.ApplicationServer
    I got the following message from my console:
    (The OC4J hung at [132]..)
    Loading from CLASSPATH bc4j_scott_bc4j_scott_Bc4j_scottModule.properties
    Diagnostics: Routing diagnostics to standard output (use -Djbo.debugoutput=silent to remove)
    Successfully loaded properties file using: getResourceAsStream("/oracle/jbo/common/Diagnostic.prop
    erties");
    [00] Diagnostic Properties: Timing:false Functions:false Linecount:true Threshold:6
    [01] CommonMessageBundle (language base) being initialized
    [02] Stringmanager using default locale: 'null'
    [03] Creating a new pool instance
    [04] BC4JDeployPlatform: LOCAL
    [05] Propertymanager: searching for file and system based properties
    [06] {{ begin Loading BC4J properties
    [07] -----------------------------------------------------------
    [08] BC4J Property jbo.default.language='en' -->(MetaObjectManager) from System Default
    [09] BC4J Property jbo.default.country='US' -->(MetaObjectManager) from System Default
    [10] BC4J Property DeployPlatform='LOCAL' -->(SessionImpl) from Client Environment
    [11] Skipping empty Property ConnectionMode from System Default
    [12] Skipping empty Property HostName from System Default
    [13] Skipping empty Property ConnectionPort from System Default
    [14] Skipping empty Property ApplicationPath from System Default
    [15] Skipping empty Property java.naming.security.principal from System Default
    [16] Skipping empty Property java.naming.security.credentials from System Default
    [17] BC4J Property jbo.use.pers.coll='false' -->(SessionImpl) from System Default
    [18] BC4J Property jbo.pers.max.rows.per.node='70' -->(SessionImpl) from System Default
    [19] BC4J Property jbo.pers.max.active.nodes='10' -->(SessionImpl) from System Default
    [20] BC4J Property jbo.pcoll.mgr='oracle.jbo.pcoll.OraclePersistManager' -->(SessionImpl) from Sys
    tem Default
    [21] BC4J Property jbo.fetch.mode='AS.NEEDED' -->(MetaObjectManager) from System Default
    [22] Skipping empty Property JBODynamicObjectsPackage from System Default
    [23] BC4J Property MetaObjectContextFactory='oracle.jbo.server.xml.DefaultMomContextFactory' -->(M
    etaObjectManager) from /oracle/jbo/server/jboserver.properties resource
    [24] BC4J Property MetaObjectContext='oracle.jbo.server.xml.XMLContextImpl' -->(MetaObjectManager)
    from /oracle/jbo/server/jboserver.properties resource
    [25] BC4J Property java.naming.factory.initial='oracle.jbo.common.JboInitialContextFactory' -->(Se
    ssionImpl) from Client Environment
    [26] BC4J Property IsLazyLoadingTrue='true' -->(MetaObjectManager) from /oracle/jbo/server/jboserv
    er.properties resource
    [27] BC4J Property ActivateSharedDataHandle='false' -->(MetaObjectManager) from System Default
    [28] Skipping empty Property HandleName from System Default
    [29] Skipping empty Property Factory-Substitution-List from System Default
    [30] BC4J Property jbo.project='bc4j_scott' -->(MetaObjectManager) from Client Environment
    [31] BC4J Property jbo.max.cursors='50' -->(MetaObjectManager) from System Default
    [32] BC4J Property jbo.dofai lover='true' -->(MetaObjectManager) from System Default
    [33] BC4J Property jbo.doconnectionpooling='false' -->(MetaObjectManager) from System Default
    [34] BC4J Property jbo.recyclethreshold='10' -->(MetaObjectManager) from System Default
    [35] BC4J Property jbo.passivationstore='null' -->(MetaObjectManager) from System Default
    [36] BC4J Property RELEASE_MODE='Reserved' -->(MetaObjectManager) from System Default
    [37] BC4J Property jbo.maxpoolcookieage='-1' -->(MetaObjectManager) from System Default
    [38] Skipping empty Property PoolClassName from System Default
    [39] BC4J Property jbo.maxpoolsize='2147483647' -->(MetaObjectManager) from System Default
    [40] BC4J Property jbo.initpoolsize='0' -->(MetaObjectManager) from System Default
    [41] BC4J Property jbo.poolrequesttimeout='30000' -->(MetaObjectManager) from System Default
    [42] BC4J Property jbo.assoc.consistent='true' -->(MetaObjectManager) from System Default
    [43] BC4J Property jbo.SQLBuilder='Oracle' -->(MetaObjectManager) from /oracle/jbo/server/jboserve
    r.properties resource
    [44] BC4J Property jbo.ConnectionPoolManager='oracle.jbo.server.ConnectionPoolManagerImpl' -->(Met
    aObjectManager) from System Default
    [45] BC4J Property jbo.TypeMapEntries='Oracle' -->(MetaObjectManager) from /oracle/jbo/server/jbos
    erver.properties resource
    [46] BC4J Property jbo.jdbc.trace='false' -->(MetaObjectManager) from System Default
    [47] BC4J Property oracle.jbo.defineColumnLength='true' -->(MetaObjectManager) from System Default
    [48] Skipping empty Property jbo.tmpdir from System Default
    [49] Skipping empty Property jbo.server.internal_connection from System Default
    [50] Skipping empty Property SessionClass from System Default
    [51] Skipping empty Property TransactionFactory from System Default
    [52] BC4J Property jbo.debugoutput='console' -->(Diagnostic) from System Property
    [53] BC4J Property jbo.debug.prefix='DBG' -->(Diagnostic) from /oracle/jbo/common/Diagnostic.prope
    rties resource
    [54] BC4J Property jbo.logging.show.timing='false' -->(Diagnostic) from /oracle/jbo/common/Diagnos
    tic.properties resource
    [55] BC4J Property jbo.logging.show.function='false' -->(Diagnostic) from /oracle/jbo/common/Diagn
    ostic.properties resource
    [56] BC4J Property jbo.logging.show.level='false' -->(Diagnostic) from /oracle/jbo/common/Diagnost
    ic.properties resource
    [57] BC4J Property jbo.logging.show.linecount='true' -->(Diagnostic) from /oracle/jbo/common/Diagn
    ostic.properties resource
    [58] BC4J Property jbo.logging.trace.threshold='6' -->(Diagnostic) from /oracle/jbo/common/Diagnos
    tic.properties resource
    [59] BC4J Property jbo.jdbc.driver.verbose='false' -->(Diagnostic) from System Default
    [60] BC4J Property jbo.ejb.txntimeout='60' -->(SessionImpl) from System Default
    [61] BC4J Property jbo.ejb.txntype='global' -->(MetaObjectManager) from System Default
    [62] Skipping empty Property oracle.jbo.schema from System Default
    [63] Copying unknown Client property (CSSURL='/webapp/cabo/images/cabo_styles.css') to session
    [64] Copying unknown Client property (DBconnection='jdbc:oracle:thin:@Oracle_Prod1:1521:p816') to
    session
    [65] Copying unknown Client property (password='tiger') to session
    [66] Copying unknown Client property (JDBCName='rick') to session
    [67] Copying unknown Client property (ConfigName='bc4j_scott.Bc4j_scottModule.Bc4j_scottModuleLoca
    l') to session
    [68] Copying unknown Client property (ImageBase='/webapp/jsimages') to session
    [69] Copying unknown Client property (user='rick') to session
    [70] Copying unknown Client property (Password='tiger') to session
    [71] Copying unknown Client property (ApplicationName='bc4j_scott.Bc4j_scottModule') to session
    [72] WARNING: Unused property: LC='Calling Function' found in /oracle/jbo/common/Diagnostic.proper
    ties resource
    [73] }} finished loading BC4J properties
    [74] -----------------------------------------------------------
    Diagnostics: Routing diagnostics to standard output (use -Djb o.debugoutput=silent to remove)
    [75] Diagnostic Properties: Timing:false Functions:false Linecount:true Threshold:6
    [76] JavaVMVersion: 1.3.0_02
    [77] JavaVMVendor: Sun Microsystems Inc.
    [78] JavaVMName: Java HotSpot(TM) Client VM
    [79] OperatingSystemName: Windows 2000
    [80] OperatingSystemVersion: 5.0
    [81] OperatingSystemUsername: RWANG
    [82] Connected to Oracle JBO Server - Version: 3.2.9.76.3
    [83] {{+++ id=10000 type: 'BC4J_CREATE_ROOTAM' Create Root Application Module 'bc4j_scott.Bc4j_sco
    ttModule'
    [84] {{+++ id=10001 type: 'METAOBJECT_LOAD' Loading meta-object: bc4j_scott.Bc4j_scottModule
    [85] {{+++ id=10002 type: 'METAOBJECT_LOAD' Loading meta-object: bc4j_scott.bc4j_scott
    [86] Loading from /bc4j_scott/bc4j_scott.xml file
    [87] Loading from indvidual XML files
    [88] Loading the Containees for the Package 'bc4j_scott.bc4j_scott'.
    [89] }}+++ End Event10003 null
    [90] Loading from /bc4j_scott/Bc4j_scottModule.xml file
    [91] }}+++ End Event10002 null
    [92] {{+++ id=10003 type: 'METAOBJECT_LOAD' Loading meta-object: bc4j_scott.DeptView
    [93] Loading from /bc4j_scott/DeptView.xml file
    [94] ViewObjectImpl's default fetch mode = 0
    [95] {{+++ id=10004 type: 'METAOBJECT_LOAD' Loading meta-object: bc4j_scott.Dept
    [96] Loading from /bc4j_scott/Dept.xml file
    [97] Loading Typemap entries from oracle.jbo.server.OracleTypeMapEntries
    [98] CSMessageBundle (language base) being initialized
    [99] }}+++ End Event10005 null
    [100] OracleSQLBuilder reached getInterface
    [101] Oracle SQL Builder Version 3.2.0.0.0
    [102] }}+++ End Event10004 null
    [103] {{+++ id=10005 type: 'BC4J_CREATE_VIEWOBJECT' Create ViewObject 'DeptView'
    [104] }}+++ End Event10006 null
    [105] {{+++ id=10006 type: 'METAOBJECT_LOAD' Loading meta-object: bc4j_scott.EmpView
    [106] Loading from /bc4j_scott/EmpView.xml file
    [107] {{+++ id=10007 type: 'METAOBJECT_LOAD' Loading meta-object: bc4j_scott.Emp
    [108] Loading from /bc4j_scott/Emp.xml file
    [109] }}+++ End Event10008 null
    [110] }}+++ End Event10007 null
    [111] {{+++ id=10008 type: 'BC4J_CREATE_VIEWOBJECT' Create ViewObject 'EmpView'
    [112] }}+++ End Event10009 null
    [113] {{+++ id=10009 type: 'METAOBJECT_LOAD' Loading meta-object: bc4j_scott.FkDeptnoLink
    [114] Loading from /bc4j_scott/FkDeptnoLink.xml file
    [115] }}+++ End Event10010 null
    [116] {{+++ id=10010 type: 'METAOBJECT_LOAD' Loading meta-object: bc4j_scott.FkDeptnoAssoc
    [117] Loading from /bc4j_scott/FkDeptnoAssoc.xml file
    [118] }}+++ End Event10011 null
    [119] Created root application module: 'bc4j_scott.Bc4j_scottModule'
    [120] Locale is: 'en_US'
    [121] }}+++ End Event10001 null
    [122] AM pool is establishing an application module connection
    [123] Using DatabaseTransactionFactory implementation oracle.jbo.server.DatabaseTransactionFactory
    [124] DBTransactionImpl Max Cursors is 50
    [125] Oracle SQLBuilder: Registered driver: oracle.jdbc.driver.OracleDriver
    [126] {{+++ id=10011 type: 'JDBC_CONNECT' null
    [127] Trying connection/2: url='jdbc:oracle:thin:@Oracle_Prod1:1521:p816' info='{user=rick, passwo
    rd=tiger}' ...
    [128] }}+++ End Event10012 null
    [129] Successfully logged in
    [130] JDBCDriverVersion: 8.1.7.1.0
    [131] DatabaseProductName: Oracle
    [132] DatabaseProductVersion: Oracle8i Enterprise Edition Release 8.1.6.0.0 - Production With the
    Partitioning option JServer Release 8.1.6.0.0 - Production <---It's hanging here for a very very long time......
    Any idea?
    null

Maybe you are looking for