Deploying Jar file in Tomcat 4.1

Any guys knoe how to deploy jar files in tomcat4.1.
i know that it should be in the "install_dir/WEB-INF/lib" folder.
but after i develop an applcaiton using packages and zip it to a jar file how do i deploy it?

You want it in a WAR file, not a JAR file - i.e. a zip file just like a JAR file but with a .war extension and the following path structure:
./WEB-INF/classes
./WEB-INF/lib
./WEB-INF/web.xml
Where your JARs go in the lib directory, plain classes in their package structure under the classes directory and your JSPs, HTML etc anywhere you like other than WEB-INF.
Then you just put the WAR in Tomcat/webapps.

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

Error in deploying .jar file from JDeveloper 10.1.3.5

Hello,
I want to deploy .jar file in a machine, instead of having to install JDeveloper to run the application (it contains: Web Services and Data Base).
I have followed the following steps in JDeveloper to create the .jar file:
1) Right click over the project: New... --> General (All Technologies option selected) --> Deployment Profiles --> JAR File
2) I have selected "Include Manifest File" option specifying the application's main class
3) In JAR Deployment Profile Properties window: File Groups --> Project Output --> Contributors are selected: "Project Output Directory" and "Project Dependencies"
4) With the previous steps, JDeveloper generates a .deploy file. It is created in Resources folder. From this folder, I have selected the .deploy file and right click and I have selected "Deploy to JAR file"
The .jar is created succesfully. In this point, I try to execute with the command:
java -jar NAME_OF_THE_DIRECTORY_WHERE_THE FILEIS_DEPLOYED\NameFile.jar
and I have the following error:
Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/rpc/ServiceFactory
at project.proxy.AccountClient.<init><AccountClient.java>
at project.proxy.AccountClient.main<init><AccountClient.java>
The Manifest File content is:
Manifest-Version: 1.0
Created-By: Oracle JDeveloper 10.1.3.5.0
Main-Class: project.proxy.AccountClient
I have tested with differents variables to create the .jar file, but always the error is the same. And I haven't found information to solve it. For this reason, I appreciate any help.
Thank you and regards.
Edited by: user1634407 on 31-mar-2010 8:27
Edited by: user1634407 on 31-mar-2010 8:47

If you are just building a client that access a Web service you need a JAR and not a WAR.
Ok!
One thing to try is look at the command line that JDeveloper uses to run your client (it's in the log window) - specifically look at the classpath used.
Then try and run the same thing from a command line and see if it works.
Nowadays, the application is running with a .BAT file, it contains the statement released from the JDeveloper console, and it is working perfectlly.
I try to do the same from a command line, and it works too.
Assuming it is - you can either use that, or you'll need to make sure that your JAR includes all the mentioned jars that were in the class path - this is done through the library type file group.
To create the .JAR file I have choosen the following options (JAR Deployment Profile Properties):
1) Include Manifest File --> I have selected the class that contains the main class (from the Browse option)
2) I left the default File Groups (Project Output) --> it has: Project Output Directory + Project Dependencies
3) As you said me, I have created a new File Group (type: Libraries) --> and here, I have selected all the possible Contributors. These match those specified in the project (Oracle XML Parser v2, J2EE, JAX-RPC Client, Commons Logging 1.0.3, Ojdbc14.jar).
4) Deployment to JAR File successfully.
The resulting MANIFEST.MF is:
Manifest-Version: 1.0
Created-By: Oracle JDeveloper 10.1.3.5.0
Main-Class: project.proxy.Execution
It hasn't definied "Class-Path", althought to especified a new File Group with the libraries... Is it an error?
If I extract the .JAR file, I see all libraries, and I have two folders: one with .class files of my project and other one is META-INF with MANIFEST.MF file.
5) From command line I executed:
C:\jdevstudio10135\jdk\bin > java -jar C:\jdevstudio10135\jdev\mywork\project\project\deploy\NameFile.jar
And the result is an error:
Exception in thread "main": java.lang.NoClassDefFoundError: javax/xml/rpc/ServiceFactory
I think the error is because it can not find the library ServiceFactory, but it is especified inside JAX-RPC Client library. What is wrong?
*6)* I have tried too to insert in "JAR Deployment Profile Properties" (in JAR options) an additional Manifest File to merge into MANIFEST.MF, to include "Class-Path" with all libraries's project (the same JAR from the statement released from the JDeveloper console), but I think that it is a limit, because if I insert all libraries the "Class-Path" doesn't inserted in MANIFEST.MF. The maxim is:
Class-Path: C:\jdevstudio10135\jdev\mywork\project\project\classes C:\jdevstudio10135\lib\xmlparserv2.jar C:\jdevstudio10135\lib\xml.jar C:\jdevstudio10135\j2ee\home\lib\activation.jar C:\jdevstudio10135\j2ee\home\lib\ejb.jar C:\jdevstudio10135\j2ee\home\lib\jms.jar C:\jdevstudio10135\j2ee\home\lib\jta.jar C:\jdevstudio10135\j2ee\home\lib\mail.jar C:\jdevstudio10135\j2ee\home\lib\servlet.jar C:\jdevstudio10135\webservices\lib\jaxrpc-api.jar
The following libraries afther the previous one aren't allowed to include because I think that is exceeding the maximum size.
I have tested to create various MANIFEST.MF with different PATHs libraries, but it isn't work to include in the MANIFEST.MF file all libraries...
(C:\jdevstudio10135\webservices\lib\wsclient.jar
C:\jdevstudio10135\webservices\lib\wsserver.jar
C:\jdevstudio10135\webservices\lib\wssecurity.jar
C:\jdevstudio10135\webservices\lib\wsdl.jar
C:\jdevstudio10135\webservices\lib\orasaaj.jar
C:\jdevstudio10135\webservices\lib\saaj-api.jar
C:\jdevstudio10135\webservices\lib\orawsdl.jar
C:\jdevstudio10135\webservices\lib\orawsrm.jar
C:\jdevstudio10135\webservices\lib\jaxr_api.jar
C:\jdevstudio10135\webservices\lib\orajaxr.jar
C:\jdevstudio10135\webservices\lib\relaxngDatatype.jar
C:\jdevstudio10135\webservices\lib\jaxb-impl.jar
C:\jdevstudio10135\webservices\lib\jaxb-libs.jar
C:\jdevstudio10135\webservices\lib\xsdlib.jar
C:\jdevstudio10135\webservices\lib\mdds.jar
C:\jdevstudio10135\jlib\jaxen.jar
C:\jdevstudio10135\jlib\oraclepki.jar
C:\jdevstudio10135\jlib\ojpse.jar
C:\jdevstudio10135\jlib\osdt_core.jar
C:\jdevstudio10135\jlib\osdt_cert.jar
C:\jdevstudio10135\jlib\osdt_xmlsec.jar
C:\jdevstudio10135\jlib\osdt_wss.jar
C:\jdevstudio10135\jlib\osdt_saml.jar
C:\jdevstudio10135\jlib\repository.jar
C:\jdevstudio10135\jlib\ojmisc.jar
C:\jdevstudio10135\j2ee\home\lib\http_client.jar
C:\jdevstudio10135\j2ee\home\jazncore.jar
C:\jdevstudio10135\j2ee\home\oc4jclient.jar
C:\jdevstudio10135\rdbms\jlib\xdb.jar
C:\jdevstudio10135\diagnostics\lib\ojdl2.jar
C:\jdevstudio10135\jakarta-taglibs\commons-logging-1.0.3\commons-logging-api.jar
C:\jdevstudio10135\jakarta-taglibs\commons-logging-1.0.3\commons-logging.jar
C:\oracle\product\10.2.0\client_1\jdbc\lib\ojdbc14.jar
C:\oracle\product\10.2.0\client_1\jdbc\lib\ojdbc14_g.jar
C:\oracle\product\10.2.0\client_1\jdbc\lib\ojdbc14dms.jar
C:\oracle\product\10.2.0\client_1\jdbc\lib\ojdbc14dms_g.jar)
With this .MF file (or including only "C:\jdevstudio10135\jdev\mywork\project\project\classes") I have solved the other problem (not found the libraries), but it still not working, the error is a little different:
Exception in thread "main": java.lang.NoClassDefFoundError: project/proxy/Execution
The path where the main class is: C:\jdevstudio10135\jdev\mywork\project\project\classes\project\proxy\Execution.class
I have tried to insert directlly the following paths in "Main Class" option of "Include Manifest File":
C:\jdevstudio10135\jdev\mywork\project\project\classes\project\proxy\Execution
C:\\jdevstudio10135\\jdev\\mywork\\project\\project\\classes\\project\\proxy\\Execution
And with these values, the error is the same: Exception in thread "main": java.lang.NoClassDefFoundError
I am not sure if the error is a bug of JDeveloper 10.1.3.5 or it is something that I don't correctly. Any idea?
Thank you again and regards.
Edited by: user12085357 on 08-abr-2010 1:31
Edited by: user12085357 on 08-abr-2010 1:38
Edited by: user12085357 on 08-abr-2010 6:58

How TO DEPLOY JAR FILES INTO XI Server using SDM

Hi XI Gurus,
   im working on adapter development. we have created jar file in NWDS.
   now going ahead to deploy into XI server through SDM.
   can we deploy jar files directly into xiserver through SDM. or it needs to convert to any other formate like EAR, SDA. then how would i convert to SDA.
i any have clear idea on this... pls throw the ways how to convert........
           JAR File to EAR format
           JAR file to SDA format
           EAR file to SDA format
   can any one explain the procedure step by step how to convert jar file into deployment archive file in order to succesfully into XI server.
          thanks i advance. points will be rewarded.
Regards
Rajesh

Hi Rajesh,
JAR file in itself in not deployable.
So v need to envelop this jar file into an EAR file and then v deploy this EAR file on SDM.
Creating Jar
Inside NWDS --> Windows --> Open perspective --> J2EE Development --> right click on ur proj --> Build EJB Archive
Converting .EAR file to .SDA
Converting .EAR file to .SDA
Regards,
Prateek

Deploying jar file in Oracle 9i lite SDK

Hi,
I have packaged my application into a jar file. How can I deploy it in my development environment. I want to use it with Oracle 9i Lite webtogo SDK.
Thanx,
JE

JE
I am not sure why do you want to deploy in SDK after publishing and synchronising the same, if I understand your question correctly.
Let me tell you how we are doing.
1) create the jar files(application) using wtgpack.exe and publish it.
2) This jar may not contain the java business objects etc other than database objects, some files.
3) Synchronize the database. Get the Lite database(ODB file).
4) if you have any stored procedures(upload it now by running batch files or by any means)
5) Deploy your Java objects(Java beans,JSPs,servlets etc) in your app server(Tomcat or OC4J). Run the application as we do against Oracle enterprise.
Yugandhar

EJB 3.0: deployment/jar file generation issue

We have a web application project (ADF Faces) which depends on a model project (EJB 3.0 session/entity beans) that implements both business and persistence layers. This EJB project points to a utility jar file containing some classes we have built. When we run the web project from inside JDev, everything works perfectly, with no error. However, when generating EAR file (deploying web project to WAR) we experience an issue.
As expected, JDev generated the war file for the web app, the jar file for the EJB and finally the EAR file containing both war and jar files. After that, we managed to deploy the ear file to our OAS 10.1.3 test instance (not standalone OC4J) and an error occured. The error is due to the fact JDev did not create the /lib subdirectory inside ejb project jar file /META-INF directory with our utility jar file inside.
We tried to generate a separated jar file for the ejb project alone with the same results.
Is this an IDE bug which does not pack the application as it should? What could we be doing wrong? If yes, is there a work-around? Like I said, the application runs fine on embedded server. Also, when the EJB application does not depend on external libraries, the deployment to OAS 10.1.3 works perfectly. We have tested it!
Could anyone help us?
Thanks in advance.
Best Regards,
Gustavo
PS: Sorry for my English. :)

Hi Shay! I follow what you said and it worked. However, we had to manually edit MANIFEST file for the EJB jar in order to add classpath clause to map our util jar. IMHO, JDev should do it for us. Anyway, we were able to deploy the app successfully.
Best Regards,
Gustavo

Error while Deploying JAR file using SDM in EP system

Hi,
As per below mention URL for Installing and Deploying the Enrichment Controller ,I am confuguring MDM Enrichment Controller in EP system
http://help.sap.com/saphelp_nwmdm71/helpdata/en/44/aa411ce9d57454e10000000a11466f/frameset.htm
So, as per the Help in Step 7, its mention to deploy a specific adapter for the external enrichment service provider i.e JAR file.
And when i am trying to deploy the *.jar file , i am getting this message in SDM:
Summary:
========
There were 1 archives selected.
0 archives successfully loaded.
   Loading of 1 archives failed.
Details:
========
1) Error loading archive
    C:\Documents and Settings\<SDMUserID>.<EPsystemHostName>\Desktop\Adapter\MDMEnrichmentAdapter.jar
    (server side name is: C:\usr\sap\SID\JC00\SDM\program\temp\MDMEnrichmentAdapter.jar)
    com.sap.sdm.util.sduread.IllFormattedSduFileException: The information about the development component found in the manifest is either missing or incomplete!
Manifest attributes are missing or have badly formatted value:
there is no deployment descriptor declared
(C:\usr\sap\SID\JC00\SDM\program\temp\MDMEnrichmentAdapter.jar)
So, kindly guide me how to deploy this jar file on EP syetm or if any settings is required.
Regards;
Hanif
Edited by: Shaikh Hanif on Nov 22, 2010 2:47 PM

Hanif,
Check this wiki's,
http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P29
http://wiki.sdn.sap.com/wiki/display/JSTSG/(GP)CannotDeployGPContent-WrongManifestFileAttributes
Good Luck!
Sandeep Tudumu

Error while deploying jar file in jboss

Hi,
I am trying to deploy a jar file in jboss, i have copied the jar in jboss_home/server/default/deploy/ directory. and i am getting the following errors while starting the jboss server.
ERROR [MainDeployer] Could not create deployment: file:/C:/jboss-4.
0.5.GA/server/default/deploy/AdminServiceBean.jar
org.jboss.deployment.DeploymentException: Verification of Enterprise Beans faile
d, see above for error messages.
at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:610)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor
.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(Intercepto
rServiceMBeanSupport.java:238)
at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInt
erceptor.java:74)
at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(Deployer
InterceptorEJB.java:44)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.
create(SubDeployerInterceptorSupport.java:180)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterce
ptor.java:91)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy26.create(Unknown Source)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor54.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
bstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:490)
at java.lang.Thread.run(Thread.java:595)
can anyone please help me on this
Thanks,
Malert

Hanif,
Check this wiki's,
http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P29
http://wiki.sdn.sap.com/wiki/display/JSTSG/(GP)CannotDeployGPContent-WrongManifestFileAttributes
Good Luck!
Sandeep Tudumu

An issue of deploying war file on tomcat 5.5

Hi,
I know the regular process to deply a war file is like this - stop tomcat server, remove your previous war file and directory, say abc.war and dir abc, copy your new version abc.war into webapps and restart tomcat server.
However, I found an interesting issue today - I was deploying a new release war file as described. While I stopped tomcat, removed all previous version direcotry, and restarted tomcat server, I got an http 404 error saying that the resource /abc/ is not available. I noticed that the org folder was not generated at work/Catalina/locahost/abc.
I stuck there for a long time to try to fix but did not find a solution. I am pretty sure the war file should be ok since it works fine on my local machine. This only happened in the unix box. Later, occasionally, I removed the director abc without stopping the tomcat server. In another word, I removed the war file while tomcat is still running. A new abc directory was created soon and now it works.
Anyone has any idea about that? Thanks!
Michael

Any thoughts? Thanks

How to deploy jar file in WLS using ant script

Hi,
Im trying to deploy a jar file in weblogic 10.3 using ant script and am running into the below error.
+[wldeploy] weblogic.management.DeploymentException: [J2EE:160177]The application at "/u01//RSJBObjects.jar" was not recognized as a valid application type. If this is an EAR file, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment should be an XML file whose name ends with "-jdbc.xml". For other application types, please consult the WebLogic Server documentation.+
When i try to deploy the same manually from the console, i get a warning stating that WLS thought this as a library and hence proceeding to deploy as a library. After this warning the deployment continues and completes.
Problem is when i try to deploy using ant, it breaks at this point.
Is there any means that we can deploy a jar to WLS using ant script. This has to be deployed as a library as other apps would be using this jar.
Im unable to create a ear file for this single jar file.
If there is any suggestion on can this be done, please share.
Thanks,
Vijay.

Hi Sunil,
Thanks for the reply, it worked.
Another doubt on the same lines. Now that the jar has been deployed as a library in WLS, when i try to deploy a WAR which refers to this deployed jar library, im unable to. I run into and error stating that the library is inaccessible.
I have to bounce the server and before doing that, i have to manually copy the library.jar from <WLS_domain>/servers/AdminServer/upload/ directory to <WLS_domain>/lib/ directory, once copied i then try to deploy the WAR, then the deployment goes fine.
Is there any means that this deployed library jar be made available soon after deployment and also to avoid copying the file.
Thanks,
Vijay.

How to deploy jar file for use within mapping user-defined fcn

Hi all,
I have a java class I'd like to called from a mapping user-defined function.
Here's what I've done (but hasn't worked)
1. Added 'package com.<mycompany>.xi.util.base64 to the source class file and compiled it.
2. Created a sda with a plain provider.xml file, i.e. no references were made to any other library files.
3. Deployed the sda to the xi 3.0 j2ee server successfully using SDM.
4. Under the Visual Admin tool, I see that the library was deployed successfully.
5. In the import text box in the user-defined function (design time), I enter com.<mycompany>.xi.util.base64.*.
A syntax check returns an error indicating the package could not be found.
Can anyone give me pointers as to how I can get this working?
Thanks,
--jtb

Hey James,
No! That's not the right way!
What you have done is for accessing external JMS & JDBC drivers in their corresponding adapters. For the access inside a mapping user defined function, it's enough if you import the jar files.
Look at this blog and you will be very clear!
/people/divya.vidyanandanprabhu/blog/2005/06/28/converting-xml-to-pdf-using-xi
regards,
Felix

How to deploy jar file in ebs12?

hi, now I want deploy a jar file in ebs12.
for example, my oaf code using jdom to parse xml file. so I need to deploy jdom.jar
into ebs12 server.
Where shall I put this jdom.jar.
Does I need change some configuration.
btw, in ebs11i, I can change Jserv.properties to support this.
thanks
tamsun

Hi Sunil,
Thanks for the reply, it worked.
Another doubt on the same lines. Now that the jar has been deployed as a library in WLS, when i try to deploy a WAR which refers to this deployed jar library, im unable to. I run into and error stating that the library is inaccessible.
I have to bounce the server and before doing that, i have to manually copy the library.jar from <WLS_domain>/servers/AdminServer/upload/ directory to <WLS_domain>/lib/ directory, once copied i then try to deploy the WAR, then the deployment goes fine.
Is there any means that this deployed library jar be made available soon after deployment and also to avoid copying the file.
Thanks,
Vijay.

How to deploy WAR file in tomcat.?

Can anybody please provide step by step information of deploying war file to Jakarta tomcat without IDE.
I am working on Windows XP with jakarta tomcat 4.1.30.
Thanks in advance.
Regards,
Aman Aggarwal

See if tomcat runs as a service in your operating system. If you can locate it, you can set the start type to automatic. A very crud way is to run the tomcat startup file from autoexe.bat.
I don't know how to do this in Linux. Here is a link for tomcat 6. Maybe it is the same in tomcat 4
[http://tomcat.apache.org/tomcat-6.0-doc/setup.html]
Edited by: nirvan on Dec 29, 2008 9:15 AM

Deploying war file on Tomcat: file path problem

Hello all,
i am using my eclipse ide for automatically deploy my webapplication to Tomcat. For Database connectivity i configured hibernate. To configure hibernate i am using the following code:
package de.wfm.hibernate.hibernateUtil;
import org.hibernate.HibernateException;
import org.hibernate.Session;
import org.hibernate.SessionFactory;
import org.hibernate.cfg.Configuration;
public class ESDBFactory {
     private static SessionFactory sf;
     private static Session session = null;
     private static String pathToCfgFile = "de\\"
                         + "wfm\\hibernate\\hibernateUtil\\esdb.cfg.xml";
     public static synchronized Session getSession() throws HibernateException {
          if (session==null) {
               if (sf==null) {
                    sf = new Configuration()
                         .configure(pathToCfgFile).
                         buildSessionFactory();
          session = sf.openSession();
          return session;
}When i use this in the ide all is fine. But when i export my application to a war file and deploy it on Tomcat i got the exception:
2006-07-28 10:06:10 StandardWrapperValve[Urlaubsplanung Servlet]: Servlet.service() for servlet Urlaubsplanung Servlet threw exception
javax.faces.FacesException: #{User.doLogin}: javax.faces.el.EvaluationException: org.hibernate.HibernateException: de\wfm\hibernate\hibernateUtil\esdb.cfg.xml not foundHow to avoid this? What do i have to do to set the file path correctly?
Regards,
ak

hmm.. ic
The .war file when drop in the webapps dir and u restart tomcat, it auto create a dir with your .war filename and the content of .war file is copied to there.
Am i rite to say so?
And wat about the web.xml?
If i need to add users and password how can I accomplished it in tomcat web.xml?
Last but not least, thanks for taking the time to reply. :D

How to build out the deployment JAR file like Visual Cafe?

Hi everybody,
I am wondering if there is tool within JDK could generate the JAR file like Visual Cafe's Deployment function.
It seems that simply to include those library file (jar file's) in the target Jar could not solve the problem.
Looking for the reply.

You must to create your META-INF file.
see more details :
http://java.sun.com/docs/books/tutorial/jar/

Deploying Jar file in Tomcat 4.1

Similar Messages

Maybe you are looking for