Deploying EAR, how to access ?

I've already deployed and enabled ear files. How can I access it, if the ear file is called bapp.ear, which is correctly listed in Application Server as deployed app ?

If your app has a web component then you cann access the components through http://<hostname>:8080/<context-root>. If it is a pure EJB app, then you can have an app client access the EJBs. What is your exact scenario ?

Similar Messages

How to deploy EAR file in Tomcat?

Is we can deploy ear file in tomcat?
Normally we can deploy WAR file in tomcat webapps folder. When we run the tomat it will automatically extract the war file.
But samethink I have tried EAR file. But it is not working.
Is we can deploy EAR file or not?
If not plz give reason.

Hi
Normally we can deploy the war file thats routene stuff ofcourse ..........but when u deploy ear file it will give problmes as ear structure and war structure are differeant
The Tomcat Servlet/JSP Container
The Apache Tomcat 5.5 Servlet/JSP Container
     Apache Logo
Links
* Docs Home
Contents
* Contents
* Introduction
* Installation
* Deployment
* Source Code
* Processes
* Example App
Application Developer's Guide
Deployment
     Printer Friendly Version
print-friendly
version
Background
Before describing how to organize your source code directories, it is useful to examine the runtime organization of a web application. Prior to the Servlet API Specification, version 2.2, there was little consistency between server platforms. However, servers that conform to the 2.2 (or later) specification are required to accept a Web Application Archive in a standard format, which is discussed further below.
A web application is defined as a hierarchy of directories and files in a standard layout. Such a hierarchy can be accessed in its "unpacked" form, where each directory and file exists in the filesystem separately, or in a "packed" form known as a Web ARchive, or WAR file. The former format is more useful during development, while the latter is used when you distribute your application to be installed.
The top-level directory of your web application hierarchy is also the document root of your application. Here, you will place the HTML files and JSP pages that comprise your application's user interface. When the system administrator deploys your application into a particular server, he or she assigns a context path to your application (a later section of this manual describes deployment on Tomcat). Thus, if the system administrator assigns your application to the context path /catalog, then a request URI referring to /catalog/index.html will retrieve the index.html file from your document root.
Standard Directory Layout
To facilitate creation of a Web Application Archive file in the required format, it is convenient to arrange the "executable" files of your web application (that is, the files that Tomcat actually uses when executing your app) in the same organization as required by the WAR format itself. To do this, you will end up with the following contents in your application's "document root" directory:
* *.html, *.jsp, etc. - The HTML and JSP pages, along with other files that must be visible to the client browser (such as JavaScript, stylesheet files, and images) for your application. In larger applications you may choose to divide these files into a subdirectory hierarchy, but for smaller apps, it is generally much simpler to maintain only a single directory for these files.
* /WEB-INF/web.xml - The Web Application Deployment Descriptor for your application. This is an XML file describing the servlets and other components that make up your application, along with any initialization parameters and container-managed security constraints that you want the server to enforce for you. This file is discussed in more detail in the following subsection.
* /WEB-INF/classes/ - This directory contains any Java class files (and associated resources) required for your application, including both servlet and non-servlet classes, that are not combined into JAR files. If your classes are organized into Java packages, you must reflect this in the directory hierarchy under /WEB-INF/classes/. For example, a Java class named com.mycompany.mypackage.MyServlet would need to be stored in a file named /WEB-INF/classes/com/mycompany/mypackage/MyServlet.class.
* /WEB-INF/lib/ - This directory contains JAR files that contain Java class files (and associated resources) required for your application, such as third party class libraries or JDBC drivers.
When you install an application into Tomcat (or any other 2.2/2.3-compatible server), the classes in the WEB-INF/classes/ directory, as well as all classes in JAR files found in the WEB-INF/lib/ directory, are made visible to other classes within your particular web application. Thus, if you include all of the required library classes in one of these places (be sure to check licenses for redistribution rights for any third party libraries you utilize), you will simplify the installation of your web application -- no adjustment to the system class path (or installation of global library files in your server) will be necessary.
Much of this information was extracted from Chapter 9 of the Servlet API Specification, version 2.3, which you should consult for more details.
Shared Library Files
Like most servlet containers, Tomcat 5 also supports mechanisms to install library JAR files (or unpacked classes) once, and make them visible to all installed web applications (without having to be included inside the web application itself. The details of how Tomcat locates and shares such classes are described in the Class Loader HOW-TO documentation. For the purposes of our discussion, there are two locations that are commonly used within a Tomcat 5 installation for shared code:
* $CATALINA_HOME/common/lib - JAR files placed here are visible both to web applications and internal Tomcat code. This is a good place to put JDBC drivers that are required for both your application and internal Tomcat use (such as for a JDBCRealm).
* $CATALINA_BASE/shared/lib - JAR files placed here are visible to all web applications, but not to internal Tomcat code. This is the right place for shared libraries that are specific to your application.
Out of the box, a standard Tomcat 5 installation includes a variety of pre-installed shared library files, including:
* The Servlet 2.4 and JSP 2.0 APIs that are fundamental to writing servlets and JavaServer Pages.
* An XML Parser compliant with the JAXP (version 1.2) APIs, so your application can perform DOM-based or SAX-based processing of XML documents.
Web Application Deployment Descriptor
The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
As mentioned above, the /WEB-INF/web.xml file contains the Web Application Deployment Descriptor for your application. As the filename extension implies, this file is an XML document, and defines everything about your application that a server needs to know (except the context path, which is assigned by the system administrator when the application is deployed).
The complete syntax and semantics for the deployment descriptor is defined in Chapter 13 of the Servlet API Specification, version 2.3. Over time, it is expected that development tools will be provided that create and edit the deployment descriptor for you. In the meantime, to provide a starting point, a basic web.xml file is provided. This file includes comments that describe the purpose of each included element.
NOTE - The Servlet Specification includes a Document Type Descriptor (DTD) for the web application deployment descriptor, and Tomcat 5 enforces the rules defined here when processing your application's /WEB-INF/web.xml file. In particular, you must enter your descriptor elements (such as <filter>, <servlet>, and <servlet-mapping> in the order defined by the DTD (see Section 13.3).
Tomcat Context Descriptor
The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
A /META-INF/context.xml file can be used to define Tomcat specific configuration options, such as loggers, data sources, session manager configuration and more. This XML file must contain one Context element, which will be considered as if it was the child of the Host element corresponding to the Host to which the The Tomcat configuration documentation contains information on the Context element.
Deployment With Tomcat 5
In order to be executed, a web application must be deployed on a servlet container. This is true even during development. We will describe using Tomcat 5 to provide the execution environment. A web application can be deployed in Tomcat by one of the following approaches:
* Copy unpacked directory hierarchy into a subdirectory in directory $CATALINA_HOME/webapps/. Tomcat will assign a context path to your application based on the subdirectory name you choose. We will use this technique in the build.xml file that we construct, because it is the quickest and easiest approach during development. Be sure to restart Tomcat after installing or updating your application.
* Copy the web application archive file into directory $CATALINA_HOME/webapps/. When Tomcat is started, it will automatically expand the web application archive file into its unpacked form, and execute the application that way. This approach would typically be used to install an additional application, provided by a third party vendor or by your internal development staff, into an existing Tomcat installation. NOTE - If you use this approach, and wish to update your application later, you must both replace the web application archive file AND delete the expanded directory that Tomcat created, and then restart Tomcat, in order to reflect your changes.
* Use the Tomcat 5 "Manager" web application to deploy and undeploy web applications. Tomcat 5 includes a web application, deployed by default on context path /manager, that allows you to deploy and undeploy applications on a running Tomcat server without restarting it. See the administrator documentation (TODO: hyperlink) for more information on using the Manager web application.
* Use "Manager" Ant Tasks In Your Build Script. Tomcat 5 includes a set of custom task definitions for the Ant build tool that allow you to automate the execution of commands to the "Manager" web application. These tasks are used in the Tomcat deployer.
* Use the Tomcat Deployer. Tomcat 5 includes a packaged tool bundling the Ant tasks, and can be used to automatically precompile JSPs which are part of the web application before deployment to the server.
Deploying your app on other servlet containers will be specific to each container, but all containers compatible with the Servlet API Specification (version 2.2 or later) are required to accept a web application archive file. Note that other containers are NOT required to accept an unpacked directory structure (as Tomcat does), or to provide mechanisms for shared library files, but these features are commonly available.
Copyright © 1999-2006, Apache Software Foundation

How to access images files outside an ear file

I tried accessing images that are not part of the ear file which i deployed. And
which created on a fly during the execution of applicaiton. I get URL not found
error, can any one let me know if is there any way where in i could access the
files not part of deployed ear. I am uisnig Weblogic 6.1 Awaiting for a reply
ASAP.
Thanks
Anastasia

Generally, accessing files that are not within your
          war hierarchy is not allowed. Everything the webapp
          needs should be contained within the webapp.
          WebLogic does have an extension known as "virtual
          directories" which does allow you to access content
          outside the war. There is information on it at:
          http://e-docs.bea.com/wls/docs70/ConsoleHelp/war_webappext_virtualdirectorymapping_config.html
          mark
          > "Ajit Mukka" <[email protected]> wrote in message
          > news:[email protected]..
          >
          > Hi
          >
          > I tried accessing files that are part of my Default WebApp directory.
          > These files are not part of the ear file which i deployed. I create
          > few runtime files and make dynamic calls to access those files.
          > I get URL not found error, can any one let me know if is there any
          > way wherein i could access the files not part of deployed ear.
          > awaiting for a reply asap.
          >
          > Thanks
          > Ajit
          >

How to access ejb jar in ear package from other war web package?

How to access ejb in jar packed in ear package from other war web package?

Typically you would just look the EJB Home up in JNDI. If you're
looking for example code, the medrec example in WLS 8.1 or petstore has
plenty of webapps calling EJBs.
-- Rob
CottonXu wrote:
How to access ejb in jar packed in ear package from other war web package?

How to access deployed J2EE Web application ?

Hi,
I am new to J2EE Web Application. I have created a Web Module project and in that I have created a servlet. I did a build for WAR file. I have created an Enterprise Application Project and included this WAR file. I built the EAP and deployed it to J2EE engine. I am successful till here.
I am not sure how to access this deployed application and thus this servlet.
I tried to access the following way :
http://<hostname>:<portnumber>/<EAPName>/<ServletName>
However, I receive the error no such location.
In the web.xml file, in the servlet-mapping section, I have mentioned the servletname and urlpattern.
I have mentioned the urlpattern as MyServlet and not /MyServlet. Notice the 'backslash'.
Could this be an issue ?
Regards,
Subramanian V.

Hi
See this Thread
Re: servlet ----->url association ?
Re: Servlet not getting loaded when put in a jar file
Re: I just want to run a simple servlet. No EJBs, no Web DynPro...
/message/610344#610344 [original link is broken]
Kind Regards
Mukesh

Cannot access the applcation after deploying EAR

Hi,
I am having accessing the application afeter deploying EAR. This is what i have done:
Tasks Status
========================== ===========
Create a new OC4J instance Created
Then under this new instance
i deployed the EAR file.
Step1: selected the EAR file
and gave a name for the application
Step2:In the URL binding it already had a name
so i just added / infront of it
Step3:Clicked next
Step4:Took the default, i.e
Use JAZN XML User Manager
Then i clicked on Finish and on summary page i
clicked on Deploy.
It sucessfully deployed without any error message.
Then i changed the data source to point to the right server with the correct username, password, schema and port no.
After all this i started this new OC4J instance, which did start without any errors.
When i try to access the application @:
http://<hostname>:port/<URL Binding>/Logon/LogonForm.jsp
I get an HTTP505 error message saying:
"The page cannot be displayed"
Can someone please help, what am i missing here ?
Thanks in advance.
Dipak

Who is they?
What specific techniques?
What happens when yu try to connect? Error messages?

How to deploy EAR on CE server using Java Support Package Manager

Hello,
I am using CE server where I want to deploy EAR file by using JSPM. I run this program in Drive:\usr\sap\CE1\J00\j2ee\JSPM\go.bat
I have also put the EAR file into the inbox folder Drive:\usr\sap\CE1\SYS\EPS\in but still It does not show me any file to proceed further for deployment.
Does any one has idea?
Regards,
NK

Hi,
The Java Support Package Manager is not able to deploy a single .ear file.
If the *.EAR file is placed inside an SCA (Software Component Archive) then JSPM is able to deploy it.
You have to create a .SCA from an .EAR file
SAP note 1223957 contains an attachment (nwpacktool.zip) which can be used to create a .SCA file from the .EAR file.
Gerd

How to Deploy EAR from command line?

hello all, I would like to know if there is a good way to deploy EAR files from
the command line for weblogic server 6.1
the documentation says I can just copy the file over and use auto-deploy but then
it wont be administerable from the the admin console
thanks!
James

Hi James,
Autodeployment should work under the development mode.
Make sure you are not running into the production mode.
Another approach is to use WebLogic's JMX API to dynamically
deploy your EAR. This could be quite tedious though.
Lynch
"James" <[email protected]> ¼¶¼g©ó¶l¥ó
news:3c02eefa$[email protected]..
>
hello all, I would like to know if there is a good way to deploy EAR filesfrom
the command line for weblogic server 6.1
the documentation says I can just copy the file over and use auto-deploybut then
it wont be administerable from the the admin console
thanks!
James

How To Access a jar file present outside the war file through a jnlp

Aoa
I m new to this forum
I m having problem with my jnlp file
i want to know is there any way to access a jar file through jnlp.The problem is that my jnlp file is present in the war file
and i want to know how to acess a jar file through this jnlp.The scenerio is as below
I m using ear file on jboss.Its hirerchy is as
-PAN-war.war
-launch.jnlp
-PAN-app-client.jar
my jnlp file is as follows:
<?xml version="1.0" encoding="UTF-8"?>
<jnlp spec="1.0+" codebase="http://localhost:8080/" href="PAN/launch.jnlp">
<information>
<title>PanEmirates</title>
<vendor>M Fazal Ur Rehman</vendor>
<description>PanEmirates</description>
<description kind="short">PanEmirates</description>
<homepage href=""/>
</information>
<security>
<all-permissions/>
</security>
<resources>
<j2se version="1.5+"/>
<jar href="PAN-app-client.jar" download="eager"/>
<jar href="lib/javafxrt.jar" main="true" download="eager" />
<jar href="lib/Filters.jar" download="eager"/>
<jar href="lib/javafx-netbeans-fxuserlib.jar" download="eager"/>
<jar href="lib/swing-layout-1.0.3.jar" download="eager"/>
</resources>
<application-desc main-class="net.java.javafx.FXShell">
<argument>pan.Main</argument>
</application-desc>
</jnlp>
when i run launch.jnlp file it says unable to download resource http://localhost:8080/PAN/PAN-app-client.jar
how to access this jar file
Any help or comment would be highly appreciated
Regards
M Fazal Ur Rehman

Excellent question. I don't see any client-jar in your EAR file structure. So I am assuming you are writing a separate client application which will talk to the ejbs deployed as part of this EAR. You need to do the following:
Write another EAR file with the following structure:
ear:
META-INF/application.xml
util.jar
client.jar
client.jar should have a META-INF/MANIFEST.MF and that should contain Class-Path:util.jar and value for Main-Class attribute.
Now deploy this new ear to your application server and execute it using Application Client Container that comes with your app server.
If you don't want to write another EAR file, then bundle th client.jar in your original EAR file.
Points to note are:
you have to repackage util.jar again inside this ear file.
For portability reason, you should use Class-Path manifest entry in client.jar. Refer to http://java.sun.com/j2ee/verified/packaging.html and J2EE platform spec section #8.2.
Hope this helps,
Sahoo

Read the version of deployed EAR modules via JMX (WLS 10.0)

Hello
We are deploying some EAR components into a WLS 10.0. Now we want to monitor the version number of the deployed EARs via a JMX client. The version number is provided in the manifest of the EAR (Implementation-Version).
I read through some JMX related documents by BEA and searched the web, but I could not find any information on how to read the version.
Does anybody know how to do that or where to look in order to get the version numbers of the deployed components via JMX? Do I have to write my own MBean offering this version attribute?
Every hint is welcomed!
Thanks
Toni
Edited by: user10451156 on Oct 21, 2008 10:53 AM

Hi, Toni.
The input must be a externally provided version number, if you have no access to write manifest entries, or to the deployment process.
If this version number is already set in the ear file, you can use this process inside your custom mbean (an elaboration of Benoit's suggestion)
1 look up the application component from JMX
* http://edocs.bea.com/wls/docs100/wlsmbeanref/mbeans/AppDeploymentMBean.html
2 obtain the path of the ear file
3 open a JarURLConnection to this ear
* http://java.sun.com/javase/6/docs/api/java/net/JarURLConnection.html
4 read the implementation version, which was already provided.
* http://java.sun.com/javase/6/docs/api/java/util/jar/Attributes.Name.html#IMPLEMENTATION_VERSION
Sadly, this won't pop-up on the WLS console, you'd have to write or use a custom extension to do that.
* https://wls-console-extensions.projects.dev2dev.bea.com/
I hope this helps.
-Adrian

How to access .html in tomcat

I am very new to programming. I have created an html file (ThreeParamsForm.html) and placed it in development directoy. I am unsure of how to access that file. When i am typing http://localhost/ThreeParamsForm.html it is giving me HTTP Status 404 error. I have tried using servlets but they seem to be working fine. It is only htmls which i am unsure how to access. please help

I think it may be considered bad practice to include all your web applications in the root directory.
Instead, why don't you deploy each web application in it's own directory with a deployment descriptor.
Your directory structure should look like this:
[TOMCAT_HOME]
--|\webapps
----|\MyWebApp
------|index.html
------|\WEB-INF
--------|web.xmlYou'r web.xml file might read like this:
<?xml version="1.0" encoding="UTF-8"?>
<web-app>
<context path="/MyWebApp" />
</web-app>This so when you browse to your web site, you will go to http://localhost/MyWebApp

How to access files in a jar file?

Can anyone tell me how to access a file contained in my jar file?
I have about 15 classes jarred and deployed as an applet. I want to include in the jar file some .gif files to be used as icons in a tree view. Rather than trying to access them locally with all the security headaches this brings, can I not simply jar them as resources and point to them in my code?
Any help much appreciated,
Thanks in advance,
Chris

Hello Chris,
Please read this note taken directly from Sun, from their Java Tutorial/Creating a GUI with Swing/Using Other Swing Features/How to use Icons/Specifying the Image Source (whew!)
Note: Applets are supposed to be able to load images from JAR files.
Currently, however, some browsers can't read images from a JAR file,
although they do successfully get classes from a JAR file.
With our applets, we currently hedge our bets by both putting
the image files in the applet's archive file (the JAR file containing
the applet's class files) and by putting the image files in the file
system on the server.
*/So......Do you want to take a chance?
-Ron

Deploying EAR using weblogic 10.3.6 under XP

Hi Guys,
tha last step of deployment EAR is to Star--->Servicing all requests, i am getting the following error?
Messages
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment. weblogic.deployment.EnvironmentException: [EJB:010176]The resource-env-ref 'BODQueue' declared in the ejb-jar.xml descriptor or annotation has no JNDI name mapped to it. The resource-env-ref must be mapped to a JNDI name using the resource-env-description element of the weblogic-ejb-jar.xml descriptor or corresponding annotation. at weblogic.ejb.container.deployer.EnvironmentBuilder.addResourceEnvReferences(EnvironmentBuilder.java:691) at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:267) at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentFor(EJBDeployer.java:1131) at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:1025) at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1288) at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:442) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:208) at weblogic.deploy.internal.targetserver.operations.StartOperation.createAndPrepareContainer(StartOperation.java:94) at weblogic.deploy.internal.targetserver.operations.StartOperation.doPrepare(StartOperation.java:107) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) NestedException Message is :[EJB:010176]The resource-env-ref 'BODQueue' declared in the ejb-jar.xml descriptor or annotation has no JNDI name mapped to it. The resource-env-ref must be mapped to a JNDI name using the resource-env-description element of the weblogic-ejb-jar.xml descriptor or corresponding annotation.
Errors were encountered while performing this operation.
what does it mean? is there any idea?
Have a nice day.
Edited by: ashash on Aug 22, 2012 3:36 AM

Atlassian has pretty good user forums, you might be able to get additional help there:
http://forums.atlassian.com/forum.jspa?forumID=46
Does the deployment screen show it has "Running". What does the deployment screen for the app show its context root as?
Also, why not just JIRA standalone? (it comes out of the box running in embedded tomcat).

Urgent :- Unable to deploy EAR file in Oracle application server

Hello folks,
I am trying to deploy an application containing jsps and servlets
packaged into EAR using ant. However when am trying to do so by using
the Deploy EAR option in the Enterprise manager, it throws the
following error -
"Invalid J2EE application file specified - Jar file:
/var/tmp/jar47241.tmp is missing its standard xml descriptor located at
META-INF/ejb-jar.xml"
I suspect that something could be wrong with regards to the way the ear
file has been created.
Please if someone could pin point the problem and help me understand
the the above error message , it will be of great help to me and I d
really appreciate this.
Many Thanks,
Ramn.

Hello,
I try to deploy an ear file (contains jar and war files) in Oracle Application server in linux, but the time is so long. The same file I deploy in a OAS in windows and the deploy time was 2 minutes, but in linux I leave the hole night and the session close and the deploy in unable.
I don't know if I need configure an especial option in the OAS in Linux, how I can load my ear file.
The OAS in windows was installed with oc4j options only, but the OAS in linux was full installation
Please help me....
Thanks.

Deploying EAR files in PI 7.1

Hello,
we are currently upgrading our XI 3.0 system to PI 7.1.
We had developed some adapter modules for XI 3.0 and we have compiled them with new libraries for using in PI 7.1.
But how can we deploy the created EAR-files in PI 7.1 now?
In XI 3.0 we used the Visual Administrator for Deploying. But we can't use this tool any more.
The SAP Netweaver Administrator doesn't have such a feature (we didn't find it anyway until now).
The only thing I found was to deploy EAR-Files using Developer Studio. But we can't deploy EAR files in test and production system this way.
Does anybody know an easy way to deploy EAR files in PI 7.1 (like in XI 3.0)?
Regards,
Thorsten

Hi Sean,
Definitely it is possible to use JSPM to deploy ear files in PI 7.1 (at least SP06). When you open up JSPM tool you will have to select "Hot Fixes" and then next. The file will have to be copied to the following Unix directory /<transport directory>/EPS/in. Unfortunately if the file is already deployed and you want to deploy it again with the same version but changes, you will not be able to redeploy it. For that propose you can use the scripts under unix ../j2ee/deployment/scripts. please have a lock under: http://help.sap.com/saphelp_nwpi71/helpdata/EN/46/1bd4293d034f08e10000000a114a6b/content.htm. There you will also find a script to convert an EAR file to SDA.
Regards,
Toni

Deploying EAR, how to access ?

Similar Messages

Maybe you are looking for