Deploying ear from within JDeveloper9.0.2 to ias9.0.2

Hi,
Is there a way to deploy an enterprise archive from within JDeveloper9.0.2 to an Oracle ias9.0.2 instance. If I try to deploy my application I get the following message:
Security error: This operation was denied. The admin.jar utility can not be used to perform operations against OPMN managed OC4J instnaces. Please use Enterprise Manager or dcmctl instead. Refer to the Oracle9iAS Admin Guide or the OC4J User's Guide for more details.
Exit status of Oracle9iAS admin tool (-deploy): 1
I'm guessing that with the new ias version I can only deploy by using oem or dcmctl, but wouldn't it be convenient if we still could use JDev?
Thx,
-J.
BTW. What are 'instnaces' ;-)

You are correct ... you must use dcmctl or OEM - see:
Re: Conditional execution in pl/sql
But JDev 9.0.3 will have the ability to invoke the DCM deployment utility within its application server connections.
As for "instances" - it is a term meant to describe multiple instances of OC4J within Oracle9iAS. In fact, you can multiple application server instances with multiple OC4J instances in each. This clustering architecture is what necessitated the need for dcmctl. For a quick architecture overview with a nice diagram check out:
http://otn.oracle.com/docs/products/ias/doc_library/90200doc_otn/web.902/a95880/cluster.htm#1007996
Mike.

Similar Messages

Oracle Forms 11gR2 - Cannot deploy locally from within Forms

I cannot deploy locally from within forms. The server is up and running and I can deploy the form by putting the correct URL in the address line of the browser window. When I try to deploy from within forms it comes up with some crazy URL that differs everytime.
This is what the URL should be and this works from the browser:
http://machinename:7002/forms/frmservlet?form=WRD608ADMIN_11g.fmx&userid=&otherparams=useSDI=yes
Here is one of the URLs it came up with when I try to run it from within Forms:
http://localhost:60231/lysVL2VjqT33znjfvLwanktVRxTIc6dEwVeRNXXRmhYU2qjf
Localhost is always there, but the rest varies.
In Forms, I have the Preferences, Runtime set to:
http://machinename:7002/forms/frmservlet
Where machine name is my PC, it is the same for this address as the URL above that works directly from the browser.
So what am I missing?
Thank you in advance.

Generally speaking, it is discouraged to manually edit any of the configuration files if they are managed by WLS Console or EM. In this case, default.env is managed by EM. Therefore, changes to the file should be done through EM. If however, you want to alter the file manually, the following is likely the best way to accomplish this:
1. Stop the WLS Admin Server and Node Manager
2. Locate the proper file you wish to edit. By proper I mean, there are several copies of most config files. Most of the config files found in the Oracle Home are actually template files and are not used at runtime. Altering these will not give you the change you want. The default.env you want would be here (assuming Windows)
C:\Oracle\Middleware\user_projects\domains\ClassicDomain\config\fmwconfig\servers\WLS_FORMS\applications\formsapp_11.1.2\config
If you are using a "Development" installation type, the above path will reflect AdminServer instead of WLS_FORMS. Remember that Development installations are not for multi-user purposes. Production deployments require the "Deployment" installation type, which can also include the Builders.
Do NOT make any changes yet.
3. Once you find the correct file, create a backup copy. Then open the file for edit (not the backup).
4. Make the desired changes and save.
5. Restart Node Manager and Admin Server if you plan to use them.
For more information about using EM to manage your configuration, refer to the product documentation:
http://docs.oracle.com/cd/E38115_01/doc.111210/e24477/configure.htm#CHDCCGHI

Deploy EAR from command prompt

What is the best way to deploy an EAR from the command prompt using JDEV11g?

Are you trying to deploy your application as EAR or are you trying to deploy the EAR file to an WLS ?
If you are trying to deploy your application you can use ojdeploy
ojdeploy -workspace /usr/jdoe/Application1.jws -profile * If you are trying to deploy the EAR to an WLS
wlserver_10.3\server\bin\setWLSEnv.cmd
java weblogic.Deployer -adminurl "http://wls:7101" -remote -username "user" -password "pass" -deploy -upload MyApp.ear -targets AdminServer

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

Error while deploying EAR from commandline

Hi,
I am getting the following error when i am trying to deploy EAR using commandline in Oracle 10gAS 10.1.2
Error: Unexpected error during lookup : Lookup error: javax.naming.AuthenticationException: Invalid username/password for default (ias_admin);Nested exception is:
javax.naming.AuthenticationException: Invalid username/password for default (ias_admin)
I am using the following commandline:
Java -jar admin.jar ormi://hostname:ormi_port ias_admin ias_admin_password -deploy -file .\applications\<EAR_Filename>ear -deploymentName <deploymentname> -iiopClientJar stub_jar_filename
I have tried without ormi port as well. The userid and password for ias_admin i am using are all correct as i am able to login to enterprise manager successfully.
I am able to deploy the same EAR using EM but I want to create client stub and i don't know what property to set in EM which create client stub along with deployment.
Thanks and Regards
Amit Trivedi

Looks strange, but do you have blanks in your path names? Don't do that. Cause pain only.
--olaf

WebLogic 7.0sp4 - deploying EAR from 6.0 - Console Servlet causes OutOfMemoryError

I downloaded various copies of WebLogic. I'm trying to work with WebLogic 7.0sp4
on a Windows 2000 Server machine, but it's not working well at all. I have a very
simple set-up - one JDBC connection pool to an Oracle database, and one EAR file.
This should work easily.
I have a WebLogic 6.0 produced EAR file. The EAR files contains about 110 Entity
BMP EJBs, about 35 Stateless Session EJBs, and 1 Stateful Session EJB, as well
as a collection of supporting Java classes.
WebLogic 6.0 imports the EAR and deploys the beans with no problem. AND after
deploying the beans, WebLogic 6.0 still lets you start a WebLogic Administrative
Console to interact with and manage the WebLogic server. WebLogic 6.0 doesn't
seem to have any problems.
WebLogic 7.0 imports the EAR file, recompiles the beans, and deploys them. If
you DON'T start an admin console, then you can ping the server, ask the server
for its state, etc. - and everything seems fine. Once you start an admin console
and try to get to the login page of the admin console, THEN WebLogic 7.0 runs
out of memory.
I've already bumped the minimum heapsize up to 350MB and maxsize to over 600MB.
The application never even uses more than 100MB of real memory before it crashes
with an out-of-memory error. Something about starting the admin console is crashing
the server. The console servlet runs out of memory. Why? Is there a separate setting
to increase the Heap Size used by the Console Servlet? I'm already using the "-Xms350m
-Xmx600m" options when starting WebLogic to set aside at least 350MB of heap space.
I'm including:
- log files
- config.xml
- startweblogic.cmd
all wrapped up in files.zip
[files.zip]

Rob,
Thanks! That solved the problem! Now I'm going to read http://java.sun.com/docs/hotspot/gc/index.html
to find out why...
Rob Woollen <[email protected]> wrote:
I suspect that you are hitting the JVM's MaxPermSize limitations.
Search on Sun's site or these newsgropus for -XX:MaxPermSize.
Let us know if this doesn't fix your problem.
-- Rob
Bill Horan wrote:
I downloaded various copies of WebLogic. I'm trying to work with WebLogic7.0sp4
on a Windows 2000 Server machine, but it's not working well at all.I have a very
simple set-up - one JDBC connection pool to an Oracle database, andone EAR file.
This should work easily.
I have a WebLogic 6.0 produced EAR file. The EAR files contains about110 Entity
BMP EJBs, about 35 Stateless Session EJBs, and 1 Stateful Session EJB,as well
as a collection of supporting Java classes.
WebLogic 6.0 imports the EAR and deploys the beans with no problem.AND after
deploying the beans, WebLogic 6.0 still lets you start a WebLogic Administrative
Console to interact with and manage the WebLogic server. WebLogic 6.0doesn't
seem to have any problems.
WebLogic 7.0 imports the EAR file, recompiles the beans, and deploysthem. If
you DON'T start an admin console, then you can ping the server, askthe server
for its state, etc. - and everything seems fine. Once you start anadmin console
and try to get to the login page of the admin console, THEN WebLogic7.0 runs
out of memory.
I've already bumped the minimum heapsize up to 350MB and maxsize toover 600MB.
The application never even uses more than 100MB of real memory beforeit crashes
with an out-of-memory error. Something about starting the admin consoleis crashing
the server. The console servlet runs out of memory. Why? Is there aseparate setting
to increase the Heap Size used by the Console Servlet? I'm alreadyusing the "-Xms350m
-Xmx600m" options when starting WebLogic to set aside at least 350MBof heap space.
I'm including:
- log files
- config.xml
- startweblogic.cmd
all wrapped up in files.zip

Error while deploying ear file generated from weblogic to ocj4

Hi All,
I have an .ear file which has been generated from weblogic server.I tried to deploy it on ocj4 aby created a new project in eclipse and deploying it on ocj4.
When I try to run my project it gives me an error:
2008-12-15 19:13:54.811 NOTIFICATION J2EE JSP-0008 Unable to dispatch JSP Page : Exception:oracle.classloader.util.AnnotatedLinkageError: duplicate class definition: javax/xml/rpc/Service
 Invalid class: javax.xml.rpc.Service
 Loader: Test.web.TSOptyQGateWeb:0.0.0
 Code-Source: /C:/OC4J_10.1.3.4/j2ee/home/applications/Test/TSOptyQGateWeb/WEB-INF/lib/jaxrpc.jar
 Configuration: WEB-INF/lib/ directory in C:\OC4J_10.1.3.4\j2ee\home\applications\Test\TSOptyQGateWeb\WEB-INF\lib
 Dependent class: oracle.jsp.runtimev2.JspPageInstFacade$DeclaredAction
 Loader: oc4j:10.1.3
 Code-Source: /C:/OC4J_10.1.3.4/j2ee/home/lib/ojsp.jar
 Configuration: <code-source> in META-INF/boot.xml in C:\OC4J_10.1.3.4\j2ee\home\oc4j.jar
 The original class instance was defined in the shared-library oracle.ws.jaxrpc:1.1, and oc4j:10.1.3 does import that loader. This may be a search-order problem.
Can anyone help??

Hi,
I checked the log-files, but there are no helpful informations, but:
07/04/23 12:08:04 - Start updating EAR file...
07/04/23 12:08:04 - start-up mode is lazy
07/04/23 12:08:20 - com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file Docsndownloads.war
 com.sap.engine.services.deploy.ear.exceptions.BaseIOException: Error during replacement of substitution values. Reason:
 java.io.IOException: Stream closed
and
Apr 23, 2007 12:08:20... Error: Aborted: development component 'Dokusunddownloads'/'sap.com'/'localhost'/'2007.04.23.12.07.47'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy API:
com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file Docsndownloads.war
com.sap.engine.services.deploy.ear.exceptions.BaseIOException: Error during replacement of substitution values. Reason:
java.io.IOException: Stream closed
thanks,
Lu

Deploying ear application - migrating from OC4j to Weblogic

I am trying to migrate application from OC4J to weblogic server. Apart from usual differences in descriptors, structure of EAR etc. I came across unusual error:
"both the remote home and remote component interface must be specified. Currently, only one of them is specified"
It is about deploying session bean. Usual EJB3 stateless session bean with local and remote interface, deployed without any problem on OC4J and JBoss. Of course, I know home interfaces are something to do with EJB 2.1, but this is EJB3 application and, I guess, Weblogic has full support for it. Does it? :)
Anyway, is there workaround? Or am I missing something? I don't have to tell you what problems we will be facing if I have to restructure whole application with dozens and hundreds of session beans.
Thanks a lot!

OK. I just want to make sure that there are no problems with the deployment descriptors.
To pin point the problem do the following in JDeveloper:
1. Create a simple EJB 3.0 session bean
2. On that session bean create a Sample Java Client.
3. Run the Session Bean
4. Run the Client
5. If both are running fine, compare the deployment descriptors from the sample and your real application.
--olaf

Using Web Dynpro WDUrlGenerator from within J2EE Application deployed on NW

I have two applications deployed on a NetWeaver Application Server 2004s.
1. A Web Dynpro application.
2. A J2EE Application
What I want to do is to be able to build a url to the Web Dynpro application from within the J2EE application. Obviously the problem is using Web Dynpro classes within the J2EE application.
So I edited the Java Build Path of the J2EE application to include the werbdynproservices.jar file and exception.jar files by extending ECLIPSE_HOME variable in the libraries section. I also checked them in Order and Export. I verified the built .war file and it does contain the two .jar files.
This was sufficient to get my project build and deployed, however the servlet in my J2EE application shows NoClassDefFoundException when I run it. My guess is there's more I need to do to get the WDUrlGenerator to run in my J2EE class.
Is this possible or is there a better way? I am trying to avoid the client having to modify a web.xml for each depployment.
Thanks in Advance.

This looks like what I want, but I am unable to test it.
I found the application-j2ee-engine.xml file under the <project-root>/gen_wdp folder. I then attempted to open it with the SAP EARDD editor. It opens with the Source tab selected. If I try to click the General tab I get an error saying:
"The source page has errors. Other pages cannot be used until these erros are corrected."
I see nothing wrong with the XML document. It's source is here:
<?xml version="1.0" encoding="UTF-8"?>
<application-j2ee-engine>
 <provider-name>local</provider-name>
 <modules-additional>
 <module>
 <entry-name>EVENTS_WorkflowNotification.wda</entry-name>
 <container-type>webdynpro</container-type>
 </module>
</modules-additional>
</application-j2ee-engine>
When I deploy the application, everything works fine. I was going to edit the XML document by hand, but of course there is no DTD listed so I don't know what's supposed to go in there without the Editor doing it for me.
Getting closer. Thanks so much.

How to deploy Oracel Business Rule (11 TP4) from within JDeveloper?

Hello,
I'm testing the Oracle Business Rules functionality provided in JDeveloper 11TP4.
Development looks nice. I'd like to test the rules, wether it be from within a Java Class or as a Web Service.
- How can I test the Business Rule 11G in Jdev TP4?
- How can I deploy the Business Rules to an Application Server?
Who's got ideas?
Thanks in advance,
Regards Léon Smiers

Leon,
Try the business rules sample for TP4. It includes instructions on how to build the rule and deploy it from JDev.
http://www.oracle.com/technology/products/ias/bpel/techpreview/index.html
Heidi.

Deploy EAR file to OC4J from PL/SQL Store Procedure

Hi
Can you deploy an EAR File from PL/SQL Store Procedure?
are there any API'S to achieve that?
Thanks.

Customer has an IAS 10.1.3 Environment with multiple OC4J's for different projects.
We would like to allow each Project Team to be able to perform deployment on their own.
Problem is, that we want to be able to control which OC4J Container each project team can deploy to and restrict them from creating into other containers.
Although IAS 10.1.3 does allow you to define different users and groups, it doesnt allow you to restrict a user/group into one specific OC4J.
This is a big problem for customer and in the quest of searching some Creative Solutions, we wanted to try and create a simple Web UI (i.e, in APEX) that will allow customer to
upload new EAR (or WAR) file and it will deploy it to their container automatically.
to achieve this, we need to find (easy) way to deploy files from PL/SQL.
we can always use external pl/sql procedure that run a Shell Script which does this,
but customer is searching for a more "direct" way to do this.
any suggestions on this issue?

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

Exception while to deploy ear at managed server

I have a wli cluster version 8.1 sp3. It has two nodes. The node that is hosted in a machine different machine from admin server displayes a message
 javax.management.InvalidAttributeValueException: Unable to create path to /appl/webbus/bea/user_projects/domains/MY_DOMAIN/./adminServer/upload/xxx/xxx.ear
 whenever it starts. But the application seems to starts correctly.
 This node has different path than the other.
 It is /appl/webdbus/bea/user_projects/
 I can not find anything relating in newsgroups. Can anyone explain me why this happens.

Hi,
 My suspicion about the exception is the it's caused by the different directory structure of the two nodes. As you can see at bold words, weblogic tries to create ear at a directory that does not exist at this node. It finds the latter webbus from the path of admin server at the other machine. My question is straightforwad, Can we have different paths at cluster nodes ? In this case, Should we deploy ear (webservice application) in a different way ?
 <Feb 22, 2005 12:33:26 PM EET> <Info> <Deployer> <BEA-149060> <Module faxManWeb of application faxManAppl successfully transitioned from prepared to active on server wliBusServerPatmosDevel.>
 javax.management.InvalidAttributeValueException: Unable to create path to /appl/webbus/bea/user_projects/domains/ITIC-DEVEL-WLI/adminServerDevel/upload/faxManAppl/faxManAppl.ear
 at weblogic.management.internal.BootStrap.apply(BootStrap.java:580)
 at weblogic.management.internal.BootStrap.apply(BootStrap.java:474)
 at weblogic.management.mbeans.custom.Application.getFullPath2(Application.java:3476)
 at weblogic.management.mbeans.custom.Application.getFullPath(Application.java:3055)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
 at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
 at weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.java(Compiled Code))
 at weblogic.management.internal.ConfigurationMBeanImpl.getAttribute(ConfigurationMBeanImpl.java(Compiled Code))
 at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java(Compiled Code))
 at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java(Inlined Compiled Code))
 at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java(Compiled Code))
 at weblogic.management.internal.MBeanProxy.getAttribute(MBeanProxy.java(Compiled Code))
 at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java(Compiled Code))
 at weblogic.management.configuration.ApplicationMBean_Stub.getFullPath(ApplicationMBean_Stub.java:543)
 at com.bea.wli.broker.manifest.ApplicationManager.load(ApplicationManager.java:71)
 at com.bea.wli.broker.MessageBroker.registerApplication(MessageBroker.java:999)
 at com.bea.wli.management.WLIAppListener$1.run(WLIAppListener.java:294)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at com.bea.wli.management.WLIAppListener.applicationInitialized(WLIAppListener.java:290)
 at weblogic.j2ee.ListenerInvocationAction.run(ListenerInvocationAction.java:46)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.j2ee.J2EEApplicationContainer.notifySecureListener(J2EEApplicationContainer.java:4721)
 at weblogic.j2ee.J2EEApplicationContainer.notify(J2EEApplicationContainer.java:4706)
 at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2201)
 at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2146)
 at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2094)
 at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:2976)
 at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1751)
 at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:359)
 at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
 at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
 at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
 at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
 at weblogic.Server.main(Server.java:32)
 --------------- nested within: ------------------
 weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested exception:
 [javax.management.InvalidAttributeValueException: Unable to create path to /appl/webbus/bea/user_projects/domains/ITIC-DEVEL-WLI/adminServerDevel/upload/faxManAppl/faxManAppl.ear]
 at weblogic.management.mbeans.custom.Application.getFullPath2(Application.java:3479)
 at weblogic.management.mbeans.custom.Application.getFullPath(Application.java:3055)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
 at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
 at weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.java(Compiled Code))
 at weblogic.management.internal.ConfigurationMBeanImpl.getAttribute(ConfigurationMBeanImpl.java(Compiled Code))
 at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java(Compiled Code))
 at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java(Inlined Compiled Code))
 at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java(Compiled Code))
 at weblogic.management.internal.MBeanProxy.getAttribute(MBeanProxy.java(Compiled Code))
 at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java(Compiled Code))
 at weblogic.management.configuration.ApplicationMBean_Stub.getFullPath(ApplicationMBean_Stub.java:543)
 at com.bea.wli.broker.manifest.ApplicationManager.load(ApplicationManager.java:71)
 at com.bea.wli.broker.MessageBroker.registerApplication(MessageBroker.java:999)
 at com.bea.wli.management.WLIAppListener$1.run(WLIAppListener.java:294)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at com.bea.wli.management.WLIAppListener.applicationInitialized(WLIAppListener.java:290)
 at weblogic.j2ee.ListenerInvocationAction.run(ListenerInvocationAction.java:46)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.j2ee.J2EEApplicationContainer.notifySecureListener(J2EEApplicationContainer.java:4721)
 at weblogic.j2ee.J2EEApplicationContainer.notify(J2EEApplicationContainer.java:4706)
 at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2201)
 at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2146)
 at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2094)
 at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:2976)
 at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1751)
 at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:359)
 at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
 at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
 at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
 at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
 at weblogic.Server.main(Server.java:32)

Get weblogic deployment version from webcenter portal application

Hi everybody,
I was wondering whether it is possible to retrieve the version number of a deployed webcenter portal application from the application itself. The usecase here is that we want to display the version number in the portal application itself. I have set the current version in the MANIFEST.MF and the deployment works and provides the correct version number. Now I am wondering how to retrieve this value. I have tried reading from the MANIFEST.MF from within the application but I only manage to get the manifest for the webcenter framework... (This is undoubtedly because it reads from the WAR and not the EAR)
I am using Webcenter Portal 11.1.1.6.
Any pointers?
Thank you!

Hi! Thanks for your reply. I think you may have misunderstood me. I do not need the server version, but the version of a deployed application on the server. (like "portalapp (V1.0)") Using the MANIFEST.MF I can specify a version.
I can see there might be a way to do so by connecting to the weblogic server using the method referenced by you but I wonder if there could be an easier way.
Greetings,
Marcel

Error while deploying ear-file to J2EE via NWDS/SDM

Hi everybody,
i have a problem deploying an ear-file. I was looking for similar cases in forums, but didn't find anything. My application is developed by jsp/servlets. The deployment aborts with following error-massage:
Caught exception during application deployment from SAP J2EE Engine's deploy API:
com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file Docsndownloads.warcom.sap.engine.services.deploy.ear.exceptions.BaseIOException: Error during replacement of substitution values. Reason: java.io.IOException: Stream closed
I don't know what the reason could be. The application is running on tomcat. And I can deploy other applications to j2ee with nwds/sdm.
Maybe somebody had or has the same problem. Or somebody knows the answer for the problem. Please help, points will be regarded. Thanks in advance.
best regards
Lu

Hi,
I checked the log-files, but there are no helpful informations, but:
07/04/23 12:08:04 - Start updating EAR file...
07/04/23 12:08:04 - start-up mode is lazy
07/04/23 12:08:20 - com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file Docsndownloads.war
com.sap.engine.services.deploy.ear.exceptions.BaseIOException: Error during replacement of substitution values. Reason:
java.io.IOException: Stream closed
and
Apr 23, 2007 12:08:20... Error: Aborted: development component 'Dokusunddownloads'/'sap.com'/'localhost'/'2007.04.23.12.07.47'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy API:
com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file Docsndownloads.war
com.sap.engine.services.deploy.ear.exceptions.BaseIOException: Error during replacement of substitution values. Reason:
java.io.IOException: Stream closed
thanks,
Lu

Deploying ear from within JDeveloper9.0.2 to ias9.0.2

Similar Messages

Maybe you are looking for