Deploy using remote server

hi,
i need to inform about the following:
i installed creator 2005Q1 and i want to use a remore server for deployment so is it enough to install sun application server enterprise edition 2005Q1 on the server without the IDE and do i need to do some configurations on that server ???
Best Regards,

Hi,
Please go through the tutorial titled "Deploying to a Sun Java System Application Server" which is available at:http://developers.sun.com/prodtech/javatools/jscreator/learning/tutorials/2/appserverdeploy.html
Also, you could go through the Remote Deployment in the Sun Java Studio Creator 2 IDE. This is available at:http://developers.sun.com/prodtech/javatools/jscreator/reference/fi/2/remote-deploy.html
Hope this helps.
RK

Similar Messages

  • Interesting! JDeveloper deploy to remote server uses HTTP POST

    The documentation clearly mentions that the bpelc ant task only deploys to local server using a file copy. I was wondering how JDeveloper is able to deploy to remote servers. Turns out is just does a HTTP POST of multipart/form-data to upload the BPEL suitcase jar file. Given below is the trace of the POST. Of course, it is all proprietary for now and is not documented. Maybe Oracle can wrap this as a custom ant task?
    --Nizam
    POST /integration/services/deploy/deployProcess.jsp HTTP/1.1
    Host: bpel.server.com:9700
    Connection: Keep-Alive, TE
    TE: trailers, deflate, gzip, compress
    User-Agent: RPT-HTTPClient/0.3-3
    BPELDomain: default
    BPELPassword: bpel
    Accept-Language: en
    Accept-Encoding: gzip, x-gzip, compress, x-compress
    Content-type: multipart/form-data;boundary=*****
    Content-length: 10690
    Content-Disposition: form-data; name="upload";BPELDomain="default"; filename="E:\work\MyBPELWS\HelloWorld\output\bpel_HelloWorld_1.0.jar"
    PK..
    ........3................META-INF/....PK..
    ........3...#............META-INF/MANIFEST.MFManifest-Version: 1.0
    Process-GUID: MD5{9d2c0a4b850da042548cc6bdf1c04d68}
    Created-By: 1.4.2_06 (Sun Microsystems Inc.)
    Process-Id: HelloWorld
    Timestamp: 1124360790893
    Process-Class: BPEL
    Implementation-Package: bpel.p0
    Revision-Tag: 1.0
    PK..
    ........3................BPEL-INF/PK..
    ........3.\.Z............bpel.xml<?xml version="1.0" encoding="UTF-8"?>
    <BPELSuitcase guid="MD5{9d2c0a4b850da042548cc6bdf1c04d68}" timestamp="1124360790893" revision="1.0">
    <BPELProcess process-impl="bpel.p0.BPEL_BIN" src="HelloWorld.bpel" id="HelloWorld">
    <partnerLinkBindings>
    <partnerLinkBinding name="client">
    <property name="wsdlLocation">HelloWorld.wsdl</property>
    </partnerLinkBinding>
    </partnerLinkBindings>
    </BPELProcess>
    </BPELSuitcase>
    PK..
    ........3[...5...5.......build.xml<?xml version="1.0" ?>
    <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Run cxant on this file to build, package and deploy the
    HelloWorld BPEL process
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    <project name="HelloWorld" default="main" basedir=".">
    <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Name of the domain the generated BPEL suitcase will be deployed to
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    <property name="deploy" value="default" />
    <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    What version number should be used to tag the generated BPEL archive?
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    <property name="rev" value="1.0" />
    <target name="main">
    <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    the bpelc task compiles and package BPEL processes into versioned BPEL
    archives (bpel_...jar). See the "Programming BPEL" guide for more
    information on the options of this task.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    <bpelc input="${basedir}/bpel.xml" rev="${rev}" deploy="${deploy}" />
    </target>
    </project>PK..
    ........3,.JaZ...Z.......graphics.xml<?xml version = '1.0' encoding = 'UTF-8'?>
    <graphics>
    <partnerlink_locations>
    <partnerlink name="client" x="15" y="215" side="left"/>
    </partnerlink_locations>
    <diagram popupeditor="false" centerzoom="true" validateonload="true" confirmbeforedelete="true" SELECTED_PARTNERLINK_COLOR="0,0,153" SWIMLANE_BACKGROUND="255,255,225" SWIMLANE_DIVIDER_BACKGROUND="236,233,216" GRAPH_BACKGROUND="255,255,255" SELECTED_BORDER_BACKGROUND="204,255,204" CONNECTED_PARTNERLINK_COLOR="204,204,255" CONNECTABLE_PARTNERLINK_COLOR="0,0,255" UNCONNECTED_PARTNERLINK_COLOR="192,192,192"/>
    </graphics>
    PK..
    ........3O ..............HelloService.wsdl<definitions
    targetNamespace="http://tempuri.org/"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
    xmlns:s0="http://tempuri.org/"
    xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    >
    <import namespace="http://tempuri.org/" location="http://localhost/HelloEnglish/Service1.asmx?WSDL"/>
    <plnk:partnerLinkType name="Service1Soap_PL">
    <plnk:role name="Service1Soap_Role">
    <plnk:portType name="s0:Service1Soap"/>
    </plnk:role>
    </plnk:partnerLinkType>
    </definitions>
    PK..
    ........3.....
    ......HelloWorld.bpel<!--
    // Oracle JDeveloper BPEL Designer
    // Created: Fri Aug 05 00:05:52 IST 2005
    // Author: nizam
    // Purpose: Synchronous BPEL Process
    -->
    <process name="HelloWorld" targetNamespace="http://xmlns.oracle.com/HelloWorld" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20" xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap" xmlns:bpelx="http://schemas.oracle.com/bpel/extension" xmlns:client="http://xmlns.oracle.com/HelloWorld" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc"><!-- ================================================================= --><!-- PARTNERLINKS --><!-- List of services participating in this BPEL process --><!-- ================================================================= -->
    <partnerLinks><!--
    The 'client' role represents the requester of this service. It is
    used for callback. The location and correlation information associated
    with the client role are automatically set using WS-Addressing.
    -->
    <partnerLink name="client" partnerLinkType="client:HelloWorld" myRole="HelloWorldProvider"/>
    </partnerLinks><!-- ================================================================= --><!-- VARIABLES --><!-- List of messages and XML documents used within this BPEL process --><!-- ================================================================= -->
    <variables><!-- Reference to the message passed as input during initiation -->
    <variable name="inputVariable" messageType="client:HelloWorldRequestMessage"/><!--
    Reference to the message that will be returned to the requester
    -->
    <variable name="outputVariable" messageType="client:HelloWorldResponseMessage"/>
    </variables><!-- ================================================================= --><!-- ORCHESTRATION LOGIC --><!-- Set of activities coordinating the flow of messages across the --><!-- services integrated within this business process --><!-- ================================================================= -->
    <sequence name="main"><!-- Receive input from requestor.
    Note: This maps to operation defined in HelloWorld.wsdl
    -->
    <receive name="receiveInput" partnerLink="client" portType="client:HelloWorld" operation="process" variable="inputVariable" createInstance="yes"/><!-- Generate reply to synchronous request -->
    <assign name="Assign_1">
    <copy>
    <from expression="concat("v1.1: Hello ", bpws:getVariableData('inputVariable','payload','/client:HelloWorldProcessRequest/client:input'))"/>
    <to variable="outputVariable" part="payload" query="/client:HelloWorldProcessResponse/client:result"/>
    </copy>
    </assign>
    <reply name="replyOutput" partnerLink="client" portType="client:HelloWorld" operation="process" variable="outputVariable"/>
    </sequence>
    </process>PK..
    ........3.....
    ......HelloWorld.wsdl<?xml version="1.0" encoding="UTF-8"?>
    <definitions name="HelloWorld"
    targetNamespace="http://xmlns.oracle.com/HelloWorld"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:client="http://xmlns.oracle.com/HelloWorld"
    xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
    .<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    .TYPE DEFINITION - List of services participating in this BPEL process
    .The default output of the BPEL designer uses strings as input and
    .output to the BPEL Process. But you can define or import any XML
    .Schema type and us them as part of the message types.
    .~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    .<types>
    ..<schema attributeFormDefault="qualified"
    ...elementFormDefault="qualified"
    ...targetNamespace="http://xmlns.oracle.com/HelloWorld"
    ...xmlns="http://www.w3.org/2001/XMLSchema">
    ...<element name="HelloWorldProcessRequest">
    ....<complexType>
    .....<sequence>
    ......<element name="input" type="string"/>
    .....</sequence>
    ....</complexType>
    ...</element>
    ...<element name="HelloWorldProcessResponse">
    ....<complexType>
    .....<sequence>
    ......<element name="result" type="string"/>
    .....</sequence>
    ....</complexType>
    ...</element>
    ..</schema>
    .</types>
    .<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    .MESSAGE TYPE DEFINITION - Definition of the message types used as
    .part of the port type defintions
    .~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    .<message name="HelloWorldRequestMessage">
    ..<part name="payload" element="client:HelloWorldProcessRequest"/>
    .</message>
    .<message name="HelloWorldResponseMessage">
    ..<part name="payload" element="client:HelloWorldProcessResponse"/>
    .</message>
    .<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    .PORT TYPE DEFINITION - A port type groups a set of operations into
    .a logical service unit.
    .~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    .<!-- portType implemented by the HelloWorld BPEL process -->
    .<portType name="HelloWorld">
    ..<operation name="process">
    ...<input message="client:HelloWorldRequestMessage" />
    ...<output message="client:HelloWorldResponseMessage"/>
    ..</operation>
    .</portType>
    .<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    .PARTNER LINK TYPE DEFINITION
    .~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    .<plnk:partnerLinkType name="HelloWorld">
    ..<plnk:role name="HelloWorldProvider">
    ...<plnk:portType name="client:HelloWorld"/>
    ..</plnk:role>
    .</plnk:partnerLinkType>
    </definitions>
    PK..
    ........3..............................META-INF/....PK..
    ........3...#......................+...META-INF/MANIFEST.MFPK..
    ........3..........................T...BPEL-INF/PK..
    ........3.\.Z......................{...bpel.xmlPK..
    ........3[...5...5.................i...build.xmlPK..
    ........3,.JaZ...Z.....................graphics.xmlPK..
    ........3O ........................I...HelloService.wsdlPK..
    ........3.....
    ....................HelloWorld.bpelPK..
    ........3.....
    ....................HelloWorld.wsdlPK...............&....
    *****

    If anyone is interested, I've created a custom ant taks to leverage this HTTP post for deploying the BPEL suitcase jar to remote servers. We didn't want to use FTP, as we'd have to change permissions on the files.
    To do this, I've leveraged the oracle.tip.pc.infra.deploy.DeployRemote class. You just have to pass it the path the the jar, server url (http://host:port/deploy/deployProcess.jsp), domain, and password.
    This seems to work fine for us.
    -Mike

  • Application not working after deployment in remote server

    I have a standard web application working in my localhost. But when I deploy the same in a remote server it gives the following exception. This happens for all the jsp:useBean. why is the container not able to fund the Beans. The Tomcat is installed properly and I use it's manager tool to deploy the WAR.
    I checked the WEB-INF/lib directory and it has all the required JARs.
    Error:
    org.apache.jasper.JasperException: Exception in JSP: /test/CurWeatherBean.jsp:22
    19:         <a href="index.jsp">[ index ]</a>
    20:        
    21:         <h2>CurrentWeatherMapBean.ATOMICS</h2>
    22:         <jsp:useBean id="cwmDAO" class="com.news.pub.weather.CurWeatherBean$ATOMICS" scope="request"/>       
    23:         <ul>
    24:             <li>
    25:                 <h3>List<CurWeatherBean> get()</h3>
    Stacktrace:
         org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:506)
         org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:395)
         org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
         org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
    root cause
    java.lang.NullPointerException
         com.news.pubt.forc.oc.Container.getReference(Container.java:68)
         com.news.pubt.forc.cfg.PropertyBag.getBag(PropertyBag.java:80)
         com.news.pubt.forc.cfg.PropertyBag.getProperty(PropertyBag.java:60)
         com.news.pubt.atomicsbeans.impl.ATOMICSBean.<init>(ATOMICSBean.java:61)
         com.news.pubt.atomicsbeans.ATOMICSAwareBean.<init>(ATOMICSAwareBean.java:175)
         com.news.pubt.weather.CurWeatherBean$ATOMICS.<init>(CurWeatherBean.java:131)
         org.apache.jsp.test.CurWeatherBean_jsp._jspService(CurWeatherBean_jsp.java:65)
         org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
         org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334)
         org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
         org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:802)Please help me.
    Edited by: danbrown on Feb 8, 2008 8:32 AM

    Your error stack refers to a class with the package sequence "com.news.pubt.weather....." but your jsp file refers to a class "com.news.pub.weather...
    Is there an error in your jsp page? If so, did you change the package name, and do you still have old class files on the classpath on your local machine with the old name?
    Anyway, the top of the error stack refers to line number 68 in the Container class. So that is where you should see a problem regarding the NullPointerExcpetion. You could post that line of code.

  • Images do not show when deployed on remote server

    We are using jdeveloper 11.1.2.1, adf and integrated weblogic and remote server has weblogic where we deploy the application for testing.
    We have a login.html page. when deployed and running the image in login.html does not show in FF or IE 8. It shows on IE9. when deployed on the remote server.
    When deployed on the integrated server only fire fox shows the image. None of the other web browsers show the image in login,html
    Here is my login.html
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
    <html>
    <head>
    <!--meta http-equiv="Content-Type" content="text/html;CHARSET=iso-8859-1" /-->
    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8"/>
    <title>Application Login</title>
    </head>
    <body>
    <div class="header">
    <div class="head_logo"><img src="images/imageLogo.JPG" alt="DASIS Logo" height="73" width="862"/></div>
    </div>
    <div class="navigation"></div>
    <div class="content">
    <div class="contentTitle">
    Welcome to ISATS online.
    <hr/>
    </div>
    <div class="contentArea">
    <p class="Arial">To login, enter your user ID and password, then click the Login button.
    </p>
    <form method="POST" action="j_security_check">
    <TABLE CELLPADDING="5"
    SUMMARY="This table contains a web form
    with fields for ID and password entry." >
    <TBODY>
    <TR>
    <TD ALIGN="right" VALIGN="top">
    <span class="Arial">User ID:</span>
    </TD>
    <TD VALIGN="top" ALIGN="left">
    <input type="text" value="" alt="Enter User ID" name="j_username"></input>
    </TD>
    </TR>
    <TR>
    <TD ALIGN="right" VALIGN="top">
    <span class="Arial">Password:</span>
    </TD>
    <TD VALIGN="top" ALIGN="left">
    <input type="password" name="j_password" value="" alt="Password"></input>
    </TD>
    </TR>
    <TR>
    <TD ALIGN="right" VALIGN="top" width="85">
    </TD>
    <TD VALIGN="top" ALIGN="left">
    <input type="submit" name="submit" value="Submit"></input>
    </TD>
    </TR>
    </TBODY>
    </TABLE>
    </form>
    <span class="Arial">
    Please contact Help Desk for assistance with the User ID and Password.
    <br>
    The Help Desk number is XXX) XXX-2300.
    </span>
    </div>
    </div>
    </body>
    </html>
    Any help is appreciated
    Edited by: user597294 on Jan 11, 2012 3:58 PM
    Edited by: user597294 on Jan 11, 2012 4:01 PM

    The problem does not seem to be with TopLink or JPA, so you may want to post this question to a different forum, such as the JDeveloper/ADF forum at:
    JDeveloper and ADF
    If the image itself is being sent but not loaded, you might check that it is a display issue with the browser being used.
    Best Regards,
    Chris

  • Adapter deployment on remote server

    I have read in one of the oracle document that Application adapters and Legacy Adapter should be deployed in the same OC4J container as that of BPEL process manager. In other words your BPEL process and adapter should be on the same server then only it can be integrated. Does this apply for Technology adapters also ?

    Yes. In order to deploy to a non-SCE server, you will need to take your generated EAR or WAR file from the SCE workspace and use Application Server Control to deploy to an external OCMS instance.
    Chapter 7 of the OCMS Admin Guide describes how to deploy with Application Server Control.
    Adam

  • FMS 3.5 - How to use remoting Server Side

    I am very interested in using Remoting in order to connect to a Drupal AMFPHP service module.  On the client side this is easily done and I have had limited success on the Server side, but a good guide on how to do this properly and be able to get the data being returned would be great.
    Thanks,
    Chris
    ChrisMcIntoshDesigns.com

    I don't know if Drupal's AMFPHP implementation is any different than a straight install of AMFPHP, but this article should help to get you started:
    http://www.sephiroth.it/tutorials/flashPHP/flashcomm_AMFPHP/index.php

  • Unable to create a clustered VM using Remote Server Administration Tools - Failover Cluster Manager

    Hi
    I am using two Hyper-V Server 2012 R2 and a single WS2012 Datacenter Edition with GUI Interface for management purpose.
    I have installed Failover Clustering feature on these two Hyper-V servers and remote server administration tools for Failover Clustering on WS2012 DC Edition with GUI.
    I have created cluster using powershell cmdlets on Hyper-V server because I was unable to create a cluster using RSAT-Failover Clustering (May be some privileges issues).
    The problem is " I am still not able to create a Hyper-VM using Failover Cluster Manager on WS2012 DC Edition server". It gives me an error "Invalid operation"
    Any Help regarding this issue will be very appreciated.
    Thanks in Advance.....
    Abhinav | MCTS-Server Virtualization

    Thanks Tim for your response but atleast I should be able to create and configure VMs for high availability. 
    I think this is not the issue which I am facing. It gives me an error "invalid class". There is something missing.
    Please check and let me know if it can be solved. Any help will be really appreciated.
    Thanks in advance.
    Abhinav | MCTS-Server Virtualization

  • Error while deploying to remote server

    Hi,
    I'm trying to deploy an application from Java Studio Creator2 (running in my home office) to a Java System Applicatio Server PE 8.2 (running in our company). The server is behind a NAT router an has a private IP address on the company LAN (10.0.0.0 network). The ports 4848, 8080 and 8181 are open and directed to the server and I can connect using a web browser.
    I can also register the server in JSC2 as a remote deployment server and that little green arrow shows up imediately (I can see/change settings, ...). If I start to deploy an application to this server it fails. JSC2 and the server start talking to each other but after a few minutes I get a timeout error. This is the output in the JSC console:
    Building jar: /export/home/tim/Documents/source/Creator/Projects/Test/dist/Test.war
    Deleting directory /export/home/tim/Documents/source/Creator/Projects/Test/dist/tmp
    dist:
    run-deploy:
    Distributing /export/home/tim/Documents/source/Creator/Projects/Test/dist/Test.war to [ni000g02:4848_server]
    Start registering the project's server resources
    Finished registering server resources
    Deployment error: Deployment timed out after 240 seconds.. See the server log file for details.
    Exception=Deployment error: Deployment timed out after 240 seconds.. See the server log file for details.
    Deployment error: Deployment timed out after 240 seconds.. See the server log file for details.
    The Application is on the server but it's disabled and theres no automatic test (starting the browser, calling the page). This only works once. After I removed the crippled app from the server, I can't redeploy it.
    Maybe the problem is the server being behind a NAT router?
    Any help is appreciated!
    Tim Richter

    Hi,
    I did a fresh install (plain vanilla) and tried to deploy again. Here's the complete log:
    [#|2006-05-01T10:41:52.958+0200|INFO|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|
    /usr/java/bin/java
    -client
    -Xmx512m
    -XX:NewRatio=2
    -Dcom.sun.aas.defaultLogFile=/opt/SUNWappserver/domains/domain1/logs/server.log
    -Djava.endorsed.dirs=/opt/SUNWappserver/lib/endorsed
    -Djava.security.policy=/opt/SUNWappserver/domains/domain1/config/server.policy
    -Djava.security.auth.login.config=/opt/SUNWappserver/domains/domain1/config/login.conf
    -Dsun.rmi.dgc.server.gcInterval=3600000
    -Dsun.rmi.dgc.client.gcInterval=3600000
    -Djavax.net.ssl.keyStore=/opt/SUNWappserver/domains/domain1/config/keystore.jks
    -Djavax.net.ssl.trustStore=/opt/SUNWappserver/domains/domain1/config/cacerts.jks
    -Djava.ext.dirs=/usr/java/jre/lib/ext:/opt/SUNWappserver/domains/domain1/lib/ext:/opt/SUNWappserver/derby/lib
    -Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
    -Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
    -Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
    -Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
    -Dcom.sun.enterprise.taglisteners=jsf-impl.jar
    -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
    -Dcom.sun.aas.configName=server-config
    -Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
    -Ddomain.name=domain1
    -Djmx.invoke.getters=true
    -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
    -Dcom.sun.aas.promptForIdentity=true
    -Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
    -Dcom.sun.aas.instanceRoot=/opt/SUNWappserver/domains/domain1
    -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
    -Dcom.sun.aas.domainName=domain1
    -Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
    -Dproduct.name=Sun-Java-System/Application-Server
    -Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
    -Dcom.sun.aas.configRoot=/opt/SUNWappserver/config
    -Djava.library.path=/usr/java/jre/lib/i386/client:/usr/jdk/instances/jdk1.5.0/jre/lib/i386/client:/usr/jdk/instances/jdk1.5.0/jre/lib/i386:/usr/jdk/instances/jdk1.5.0/jre/../lib/i386:/opt/SUNWappserver/lib:/usr/lib/lwp:/opt/SUNWappserver/lib:/usr/lib/lwp:/usr/jdk/instances/jdk1.5.0/jre/lib/i386/client:/usr/jdk/instances/jdk1.5.0/jre/lib/i386:/usr/jdk/instances/jdk1.5.0/jre/../lib/i386:/opt/SUNWappserver/lib:/opt/SUNWappserver/lib:/opt/SUNWappserver/lib::/usr/lib
    -Dcom.sun.aas.instanceName=server
    -Dcom.sun.aas.processLauncher=SE
    -cp
    /usr/java/lib/tools.jar:/opt/SUNWappserver/lib/appserv-rt.jar:/opt/SUNWappserver/lib/j2ee.jar:/opt/SUNWappserver/lib/activation.jar:/opt/SUNWappserver/lib/mail.jar:/opt/SUNWappserver/lib/appserv-cmp.jar:/opt/SUNWappserver/lib/admin-cli.jar:/opt/SUNWappserver/lib/appserv-admin.jar:/opt/SUNWappserver/lib/appserv-jstl.jar:/opt/SUNWappserver/lib/commons-launcher.jar:/opt/SUNWappserver/lib/commons-logging.jar:/opt/SUNWappserver/lib/j2ee-svc.jar:/opt/SUNWappserver/lib/jaxr-api.jar:/opt/SUNWappserver/lib/jaxr-impl.jar:/opt/SUNWappserver/lib/jaxrpc-api.jar:/opt/SUNWappserver/lib/jaxrpc-impl.jar:/opt/SUNWappserver/lib/dom.jar:/opt/SUNWappserver/lib/relaxngDatatype.jar:/opt/SUNWappserver/lib/jax-qname.jar:/opt/SUNWappserver/lib/saaj-api.jar:/opt/SUNWappserver/lib/saaj-impl.jar:/opt/SUNWappserver/lib/xsdlib.jar:/opt/SUNWappserver/lib/jmxremote.jar:/opt/SUNWappserver/lib/jmxremote_optional.jar:/opt/SUNWappserver/lib/jsf-api.jar:/opt/SUNWappserver/lib/jsf-impl.jar:/opt/SUNWappserver/lib/rmissl.jar:/opt/SUNWappserver/lib/xalan.jar:/opt/SUNWappserver/lib/xercesImpl.jar:/opt/SUNWappserver/lib/appserv-assemblytool_zh_CN.jar:/opt/SUNWappserver/lib/appserv-cmp_zh_CN.jar:/opt/SUNWappserver/lib/appserv-rt_zh_CN.jar:/opt/SUNWappserver/lib/commons-launcher_zh_CN.jar:/opt/SUNWappserver/lib/deployhelp_zh_CN.jar:/opt/SUNWappserver/lib/j2ee_zh_CN.jar:/opt/SUNWappserver/lib/appserv-assemblytool_ja.jar:/opt/SUNWappserver/lib/appserv-cmp_ja.jar:/opt/SUNWappserver/lib/appserv-rt_ja.jar:/opt/SUNWappserver/lib/j2ee_ja.jar:/opt/SUNWappserver/lib/commons-launcher_ja.jar:/opt/SUNWappserver/lib/deployhelp_ja.jar:/opt/SUNWappserver/lib/j2ee_ko.jar:/opt/SUNWappserver/lib/appserv-assemblytool_ko.jar:/opt/SUNWappserver/lib/appserv-cmp_ko.jar:/opt/SUNWappserver/lib/appserv-rt_ko.jar:/opt/SUNWappserver/lib/commons-launcher_ko.jar:/opt/SUNWappserver/lib/deployhelp_ko.jar:/opt/SUNWappserver/lib/appserv-assemblytool_fr.jar:/opt/SUNWappserver/lib/appserv-cmp_fr.jar:/opt/SUNWappserver/lib/appserv-rt_fr.jar:/opt/SUNWappserver/lib/commons-launcher_fr.jar:/opt/SUNWappserver/lib/deployhelp_fr.jar:/opt/SUNWappserver/lib/j2ee_fr.jar:/opt/SUNWappserver/lib/appserv-assemblytool_es.jar:/opt/SUNWappserver/lib/appserv-cmp_es.jar:/opt/SUNWappserver/lib/appserv-rt_es.jar:/opt/SUNWappserver/lib/commons-launcher_es.jar:/opt/SUNWappserver/lib/deployhelp_es.jar:/opt/SUNWappserver/lib/j2ee_es.jar:/opt/SUNWappserver/lib/appserv-assemblytool_zh.jar:/opt/SUNWappserver/lib/appserv-cmp_zh.jar:/opt/SUNWappserver/lib/appserv-rt_zh.jar:/opt/SUNWappserver/lib/commons-launcher_zh.jar:/opt/SUNWappserver/lib/j2ee_zh.jar:/opt/SUNWappserver/lib/deployhelp_zh.jar:/opt/SUNWappserver/lib/appserv-upgrade.jar:/opt/SUNWappserver/lib/appserv-ext.jar:/opt/SUNWappserver/lib/install/applications/jmsra/imqjmsra.jar:/opt/SUNWappserver/imq/lib/jaxm-api.jar:/opt/SUNWappserver/imq/lib/fscontext.jar:/opt/SUNWappserver/lib/ant/lib/ant.jar
    com.sun.enterprise.server.PEMain
    start
    display|#]
    [#|2006-05-01T10:41:56.585+0200|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [/opt/SUNWappserver/imq/bin].|#]
    [#|2006-05-01T10:41:56.588+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]
    [#|2006-05-01T10:41:57.161+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0046:The Platform MBeanServer is available. It will be used to register Application Server MBeans. Platform MBeans will also be available for browsing while using standard JMX Console.|#]
    [#|2006-05-01T10:41:57.166+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
    [#|2006-05-01T10:41:57.289+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
    [#|2006-05-01T10:41:57.800+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server server|#]
    [#|2006-05-01T10:41:57.805+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server __asadmin|#]
    [#|2006-05-01T10:41:58.418+0200|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3700"|#]
    [#|2006-05-01T10:41:58.721+0200|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3820"|#]
    [#|2006-05-01T10:41:58.724+0200|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3920"|#]
    [#|2006-05-01T10:41:59.436+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]
    [#|2006-05-01T10:42:03.014+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1079: Initialization of AMX MBeans successful|#]
    [#|2006-05-01T10:42:03.154+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file /opt/SUNWappserver/lib/install/applications/MEjbApp.ear for autodeployment.|#]
    [#|2006-05-01T10:42:03.671+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
    [#|2006-05-01T10:42:03.674+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
    [#|2006-05-01T10:42:03.702+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [MEjbApp]|#]
    [#|2006-05-01T10:42:03.809+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 554 msec, Total EJB Compiler Module Time: 31 msec, Portion spent EJB Compiling: 5%
    Breakdown of EJBC Module Time: Total Time for EJBC: 31 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 24 msec (77%),
    |#]
    [#|2006-05-01T10:42:03.880+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = MEjbApp|#]
    [#|2006-05-01T10:42:03.993+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added MEjbApp]|#]
    [#|2006-05-01T10:42:04.066+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
    [#|2006-05-01T10:42:04.084+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy MEjbApp]|#]
    [#|2006-05-01T10:42:04.213+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: MEJBBean; containerId: 75135249527799808|#]
    [#|2006-05-01T10:42:04.314+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
    [#|2006-05-01T10:42:04.316+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
    [#|2006-05-01T10:42:04.317+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : /opt/SUNWappserver/lib/install/applications/MEjbApp.ear.|#]
    [#|2006-05-01T10:42:04.317+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file /opt/SUNWappserver/lib/install/applications/__ejb_container_timer_app.ear for autodeployment.|#]
    [#|2006-05-01T10:42:04.498+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
    [#|2006-05-01T10:42:06.770+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
    [#|2006-05-01T10:42:06.770+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [__ejb_container_timer_app]|#]
    [#|2006-05-01T10:42:06.815+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 2488 msec, Total EJB Compiler Module Time: 2272 msec, Portion spent EJB Compiling: 91%
    Breakdown of EJBC Module Time: Total Time for EJBC: 2272 msec, CMP Generation: 649 msec (28%), Java Compilation: 1567 msec (68%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
    |#]
    [#|2006-05-01T10:42:06.857+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = __ejb_container_timer_app|#]
    [#|2006-05-01T10:42:06.908+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added __ejb_container_timer_app]|#]
    [#|2006-05-01T10:42:07.028+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
    [#|2006-05-01T10:42:07.039+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy __ejb_container_timer_app]|#]
    [#|2006-05-01T10:42:07.133+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: TimerBean; containerId: 75135249728798720|#]
    [#|2006-05-01T10:42:07.392+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
    [#|2006-05-01T10:42:07.392+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
    [#|2006-05-01T10:42:07.393+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
    [#|2006-05-01T10:42:07.393+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : /opt/SUNWappserver/lib/install/applications/__ejb_container_timer_app.ear.|#]
    [#|2006-05-01T10:42:07.398+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Sun-Java-System/Application-Server.|#]
    [#|2006-05-01T10:42:07.455+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at []|#]
    [#|2006-05-01T10:42:07.521+0200|WARNING|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
    [#|2006-05-01T10:42:07.611+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [web1]|#]
    [#|2006-05-01T10:42:07.623+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [asadmin]|#]
    [#|2006-05-01T10:42:07.625+0200|WARNING|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
    [#|2006-05-01T10:42:07.636+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [__asadmin] at [com_sun_web_ui]|#]
    [#|2006-05-01T10:42:07.711+0200|INFO|sun-appserver-pe8.2|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server|#]
    [#|2006-05-01T10:42:09.084+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]
    [#|2006-05-01T10:42:09.085+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
    [#|2006-05-01T10:42:09.097+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
    [#|2006-05-01T10:42:09.156+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Blocking Mode|#]
    [#|2006-05-01T10:42:09.157+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
    [#|2006-05-01T10:42:09.160+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
    [#|2006-05-01T10:42:09.189+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]
    [#|2006-05-01T10:42:09.189+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
    [#|2006-05-01T10:42:09.195+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
    [#|2006-05-01T10:42:09.332+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://ni000g02.kidogo.net:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors|#]
    [#|2006-05-01T10:42:09.333+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1506: Status of Standard JMX Connector: Active = [true]|#]
    [#|2006-05-01T10:42:09.363+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
    [#|2006-05-01T10:50:57.639+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5109: EJBC - START of EJBC for [Test]|#]
    [#|2006-05-01T10:50:57.640+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=11;|Processing beans ...|#]
    [#|2006-05-01T10:50:57.640+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5110: EJBC - END of EJBC for [Test]|#]
    [#|2006-05-01T10:50:57.681+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=11;|Total Deployment Time: 229 msec, Total EJB Compiler Module Time: 2 msec, Portion spent EJB Compiling: 0%
    Breakdown of EJBC Module Time: Total Time for EJBC: 2 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
    |#]
    [#|2006-05-01T10:50:57.723+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=11;|deployed with moduleid = Test|#]
    [#|2006-05-01T10:50:58.419+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=12;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added Test]|#]
    [#|2006-05-01T10:50:58.451+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=12;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
    [#|2006-05-01T10:50:58.674+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=13;|ADM1041:Sent the event to instance:[ModuleDeployEvent -- deploy web/Test]|#]
    [#|2006-05-01T10:50:58.687+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=13;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
    Tim

  • Jpeg image loaded with Loader- loadBytes() does not display when app is deployed on remote server

    I am loading a JPEG  image from the server, using the Loader->loadBytes() and that works when the app is deployed under my local Tomcat server.  When I deploy it on other servers the image is not displayed,  instead of the image I see II*
    On the server side I have java, Spring, BlazeDs and I use RemoteObject on the client.
    The code that loads the image looks like below:
    private function imageLoadResultHandler(event:ResultEvent):void {
        var result:ArrayCollection = event.result as ArrayCollection
        var bytes : ByteArray = result.getItemAt(0) as ByteArray;
        _loader = new Loader();
        _loader.contentLoaderInfo.addEventListener(Event.COMPLETE, loaderCompleteHandler);
        _loader.contentLoaderInfo.addEventListener(IOErrorEvent.IO_ERROR, loaderFaultHandler);
        _loader.loadBytes(bytes);
    private function loaderCompleteHandler(event:Event):void {
        var loaderInfo:LoaderInfo = event.currentTarget as LoaderInfo;
        var img:Image = new Image();
        img.source = loaderInfo.content;
        myPanel.addChild(img);
    <mx:RemoteObject id="ro" destination="imageLoadService">
         <mx:method name="loadImage" result="imageLoadResultHandler(event)" fault="faultHandler(event)" />
    </mx:RemoteObject>
    Any help with this problem is much appreciated.
    Thank you,
    Lumi Velicanu

    Hi Dmitri,
    Thank you for the prompt reply, your question about the jpeg content was a helpful pointer.
    I solved the problem, it had nothing to do with flex, it was all on the java side. The image was obtained from converting a TIFF to a JPEG, the conversion was failing and the flex loader was receiveing a tiff and it did not know how to display it.
    The java problem was kind of interesting, I'll post it here as an FYI in case anybody cares :
    On my server the first writer returned by ImageIO was an instance of JPEGImageWriter and on the other servers was CLibJPEGImageWriter. And it happens that  only JPEGImageWrite can write the type of TIFF that we are having.
    The fix was to iterate through all the writers and pick the instace of JPEGImageWrite, instead of the first one found.
    Lumi

  • Deploy in remote server

    Hi,
    I have jdev in one system and the weblogic server is in other system.
    When I am trying to deploy the developed application from jdev to that remote weblogic server, i am facing the below error.
    #### Deployment incomplete. ####
    [01:54:45 PM] No SOA configured servers found for deploying the archive file:/app_rev1.0.jar
    (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
    Please help me in deploying this application remotely.
    Thanks,
    dbp

    What is your Jdeveloper and SOA Suite version?
    Please note that the Jdeveloper version and the SOA Suite version should be the same.

  • Running the mappings which were deployed using remote runtime.

    Hi EveryBody,
    I am using OWB 10GR2. My environment is like this.
    I have two oracle databases A and B. I have installed OWB Repository in both databases. Now i have created a mapping map1 in Repository A and deployed it to Respository B(remote run time). I was able to run this mapping from repository A.
    But i wanted to run the mapping map1 from repository B. when i connected to repository B and checked it in control center manager. I couldn't find out the mapping.
    Can anybody suggest how to achieve this.
    MY task should be like this.
    1) create mapping map1 in rep A.
    2) deploy this mapping map1 to rep B.
    3) connect to rep B.
    4) Run the mappping map1.
    thanks,
    vasu

    test

  • JSP deployment using SunAppliction server 9.0

    I am deploying a jsp page using j2ee sdk SunApp Server deploy tool. After deploying the applictaion when i run the jsp page from internet explorer is :
    org.apache.jasper.JasperException: Unable to compile class for JSP
    No Java compiler was found to compile the generated source for the JSP.
    This can usually be solved by copying manually $JAVA_HOME/lib/tools.jar from the JDK
    to the common/lib directory of the Tomcat server, followed by a Tomcat restart.
    If using an alternate Java compiler, please check its installation and access path.
    Please! help me urgent to resolve this problem since i am stuck amidst in my project.

    No its again showing unable to compile the JSP page no JAVA compiler.
    My JAVA_HOME environment variable was initially set to jdk of Sun App server i had set it again as you mentioned to jdk installed in Program Files directory but it didn't work.

  • Remote Server Administration Tools Win7 to Svr20212R2

    Can be done, and works.  Functionality is reduced, however.  See—http://community.spiceworks.com/topic/439904-windows-7-remote-server-administration-toolkit-rsat

    I was wondering, is it possible to use Remote Server Administration Tools to access a server running Windows Server 2012 R2 on Windows 7 Pro? Last I heard it was NOT possible. If not, is there anyway to do it another way other than RD? I would like to administer my server from my computer rather than using the KVM or RD. Thanks! 
    This topic first appeared in the Spiceworks Community

  • How do I activate Office 2013 that I have deployed using ODT and App-V onto a Remote Desktop Server?

    I am setting up a demo Server 2012 R2 environment (1 DC server, 2 RDSH servers, 1 App-V server).
    I have created an Office 2013 volume license App-V package using the latest Office Deployment Toolkit. I have deployed the App-V package to an RDS server and it all works fine. However, I am unable to activate Office 2013 using the MSDN Office 2013 retail
    key because it tells me the product key is invalid for this version of Office. I've looked at the alternative of using the App-V Sequencer to create the Office 2013 package, but from what I've read this is not a Microsoft supported method.
    Is there any way that I can activate Office 2013 (volume license on RDS) using the method I've outlined above, or is there any way of using the Office2013 download from MSDN such that it can be packaged by the ODT (or App-V Sequencer) for successful deployment
    using App-V and activation using the retail Office 2013 product key on MSDN?

    True, VL channel media can't be activated with MSDN Retail pkeys (that's what I was trying to get you to understand, I figured you would be attempting that, as so many people do :(
    I've not attempted your scenario myself.
    It sounds like you aren't following the supported scenarios as (poorly) described by MS;
    The way I read their guide, for an RDS scenario, you must use a VL key [either MAK or KMS] (since a subscription product+key can't be used on RDS):
    i.e.: <Product ID="ProPlusVolume">
    http://support.microsoft.com/kb/2772509
    http://support.microsoft.com/kb/2915745
    http://technet.microsoft.com/library/dn481351.aspxhttp://blogs.technet.com/b/office_resource_kit/archive/2013/12/02/announcing-app-v-5-0-sp2-support-for-office-2013-volume-licensing-editions.aspx
    So, that all means that for RDS, you can't use anything other than VL "product" (in
    the form of an ODT-generated output) with a VL pkey. So, for your RDS demo setup, you need to use real product and real pkeys.
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Error occurred in deployment step 'Uninstall app for SharePoint': The remote server returned an error: (502) Bad Gateway.

    Installed SP 2013 Foundation in my Hyper-V machine
    Created and done all the steps mentioned here http://blogs.msdn.com/b/shariq/archive/2013/05/07/how-to-set-up-high-trust-apps-for-sharepoint-2013-amp-troubleshooting-tips.aspx && http://msdn.microsoft.com/en-us/library/office/fp179901%28v=office.15%29.aspx
    for self signed certificate
    copied those two certificates in my local machine(base machine) D drive
    (D:\Cert)
    Both VM and base machine are in same domain
    Installed VS 2013 in my base machine and create a Provided hosted app with the copied certificates, (For creation i followed the above mentioned URL)
    Just created and hit F5 to run in my base machine, but getting this error
    Error occurred in deployment step 'Uninstall app for SharePoint': The remote server returned an error: (502) Bad Gateway.
    Please help me to resolve this issue, trying to figure out from last 2 days
    Thanks in Advance
    Arun

    Hi Harminder,
    This happens because an app has already been deployed and you are deploying it again using the same version.
    Resolution:
    Open the AppManifest.xml file and change the version.
    Vivek Jagga - MCTS SharePoint
    SharePointExcellence

Maybe you are looking for