Undeployment in NW 7.4 - example

Hi Experts,
Need to undeploy few components in NW 7.4 system.
Can you please give me an example for list out the existing components and undeploy any of them (or) undeploy in together
I would appreciate your guidance
Thanks in advance.

Hi Daniel,
You can undeploy via telnet
telnet LOCALHOST 5XXXX, login with an admin user, add deply commands and undeploy the appliocation
Example:
login to OS level as adm user,
give the following commands
1. telnet localhost 5XXXX
2. give administrator credentials
3. add deploy
suppose u want to undeploy "abc" then give command
list_app |grep abc
you will get output like..... sap.com/abc
give command
undeploy vendor=sap.com name=abc.
Please note that Telnet can olny be accessed locally from the host server via LOCALHOST and port.
It cannot be accessed from another machine remotely via hostname or IP address due to security reasons.
Hope this helps.
Regards,
David

Similar Messages

Can't run the cluster example

 I would appreciate if someone can explanation my long list of questions regarding
 the deployment of EJB in cluster environment.
 I can't run the cluster EJB example( Teller/Account) in a cluster(contains two
 server2). I always get
 java.rmi.RemoteException: Unable to
 resolve examples.cluster.ejb.Account
 Home. Resolved: 'examples.cluster.ejb'
 Unresolved:'AccountHome'
 Following is my setup:
 Machine A: exampleServer:7001 (admin server)
 Machine A: testServer1:8001 (Managed server)
 Machine B: testServer1_B:8001(Managed server)
 MyCluster : testServer1, testServer1_B
 Test Client:
 java examples.cluster.ejb.Client "t3://Machine A:8001"
 ======================
 Q1: Should I use 8001 or 7001 as cluster port number?
 Q2: What will happen when we click "apply" after select/unselect the server in
 the "target", "server" tab?
 Q3: And what will happen if we click deploy/undeploy check box in "configuration"
 tab of EJB item?
 Q4: I check the JNDI tree from all above three servers can't find out JNDI tree
 doesn't reflect the change I did in Q2 or Q3.
 Q5: What is the right way to deploy EJB components, should we select both cluster
 and server in the "target" tab?
 Q6: I got this message from one of the server when I try to undeploy/deploy ejb
 object.
 "examples.cluster.ejb.TellerHome_EO in the jndi tree is non clusterable
 and you have tried to bind more
 once? How could I make it clusterable?
 Q7: Undeploy and EJB doesn't work and sometime I still get " JNDI name in use"
 from the server.
 How could I fix it.
 Thanks


First I can tell you that the ports have to be the same, be on the the
 same network , i.e. Telnet into the other m/c. Next which you probably
 have done is the properties files. Per-cluster ...
 >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
 On 6/7/01, 6:59:48 AM, "James Hsu" <[email protected]> wrote regarding
 Can't run the cluster example:
 > I would appreciate if someone can explanation my long list of
 questions regarding
 > the deployment of EJB in cluster environment.
 > I can't run the cluster EJB example( Teller/Account) in a
 cluster(contains two
 > server2). I always get
 > java.rmi.RemoteException: Unable to
 > resolve examples.cluster.ejb.Account
 > Home. Resolved: 'examples.cluster.ejb'
 > Unresolved:'AccountHome'
 > Following is my setup:
 > Machine A: exampleServer:7001 (admin server)
 > Machine A: testServer1:8001 (Managed server)
 > Machine B: testServer1_B:8001(Managed server)
 > MyCluster : testServer1, testServer1_B
 > Test Client:
 > java examples.cluster.ejb.Client "t3://Machine A:8001"
 > ======================
 > Q1: Should I use 8001 or 7001 as cluster port number?
 > Q2: What will happen when we click "apply" after select/unselect the
 server in
 > the "target", "server" tab?
 > Q3: And what will happen if we click deploy/undeploy check box in
 "configuration"
 > tab of EJB item?
 > Q4: I check the JNDI tree from all above three servers can't find out
 JNDI tree
 > doesn't reflect the change I did in Q2 or Q3.
 > Q5: What is the right way to deploy EJB components, should we select
 both cluster
 > and server in the "target" tab?
 > Q6: I got this message from one of the server when I try to
 undeploy/deploy ejb
 > object.
 > "examples.cluster.ejb.TellerHome_EO in the jndi tree is non
 clusterable
 > and you have tried to bind more
 > once? How could I make it clusterable?
 > Q7: Undeploy and EJB doesn't work and sometime I still get " JNDI
 name in use"
 > from the server.
 > How could I fix it.
 > Thanks
 [att1.html]

Tomcat restarting problem -plz help

hi,
Can anybody tell me why do i have to restart the server everytime i change my servlet.
Kindly help
Thanks and regards
neha

Hi Neha,
This documentation is from JavaWebServicesDeveloperPack(Evaluation version)
You will get more details if you can download this pack/tutorial from Java site & install it.
http://java.sun.com/webservices/webservicespack.html
Hope this will help you.
Ajay.
Manager App HOW-TO
Introduction
In many production environments, it is very useful to have the capability to deploy a new web application, or undeploy an existing one, without having to shut down and restart the entire container. In addition, you can request an existing application to reload itself, even if you have not declared it to be reloadable in the Tomcat 4 server configuration file.
To support these capabilities, Tomcat 4 includes a web application (installed by default on context path /manager) that supports the following functions:
Deploy a new web application, on a specified context path, from the uploaded contents of a WAR file.
Install a new web application, which can be anywhere on the server's disks.
List the currently deployed web applications, as well as the sessions that are currently active for those web apps.
Reload an existing web application, to reflect changes in the contents of /WEB-INF/classes or /WEB-INF/lib.
Remove an installed web application.
Start a stopped application (thus making it available again).
Stop an existing application (so that it becomes unavailable), but do not undeploy it.
Undeploy a deployed web application and delete its document base directory.
Since Manager is itself a web application, it interacts with you using standard HTTP requests and responses. However, it's "user interface" is minimal, because it is intended to be accessed from scripts set up by the system administrator. For this reason, commands are given as part of the request URI, and responses are in the form of simple text that can be easily parsed and processed.
Future versions of Tomcat 4 will include administrative functionality that is presented in (at least) the following forms:
As web services, so that Tomcat administration can be easily integrated into remote and/or non-Java mnagement environments.
As a web application with a nice user interface (built on top of the web services processing layer) for easy Tomcat administration via a web browser.
In addition to executing Manager commands directly via HTTP, Tomcat 4 includes a convenient set of task definitions for the Ant (version 1.4 or later) build tool. See Executing Manager Commands With Ant for more information.
Configuring Manager Application Access
The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 4, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 4 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
It would be quite unsafe to ship Tomcat with default settings that allowed anyone on the Internet to execute the Manager application on your server. Therefore, the Manager application is shipped with the requirement that anyone who attempts to use it must authenticate themselves, using a username and password that have the role manager associated with them. Further, there is no username in the default users file ($CATALINA_HOME/conf/tomcat-users.xml) that is assigned this role. Therefore, access to the Manager application is completely disabled by default.
To enable access to the Manager web application, you must either create a new username/password combination and associate the role name manager with it, or add the manager role to some existing username/password combination. Exactly where this is done depends on which Realm implementation you are using:
MemoryRealm - If you have not customized your $CATALINA_HOME/conf/server.xml to select a different one, Tomcat 4 defaults to an XML-format file stored at $CATALINA_HOME/conf/tomcat-users.xml, which can be edited with any text editor. This file contains an XML <user> for each individual user, which might look something like this:
<user name="craigmcc" password="secret" roles="standard,manager" />
which defines the username and password used by this individual to log on, and the role names he or she is associated with. You can add the manager role to the comma-delimited roles attriute for one or more existing users, and/or create new users with that assigned role.
JDBCRealm - Your user and role information is stored in a database accessed via JDBC. Add the manager role to one or more existing users, and/or create one or more new users with this role assigned, following the standard procedures for your environment.
JNDIRealm - Your user and role information is stored in a directory server accessed via LDAP. Add the manager role to one or more existing users, and/or create one or more new users with this role assigned, following the standard procedures for your environment.
The first time you attempt to issue one of the Manager commands described in the next section, you will be challenged to log on using BASIC authentication. The username and password you enter do not matter, as long as they identify a valid user in the users database who possesses the role manager.
Supported Manager Commands
All commands that the Manager application knows how to process are specified in a single request URI like this:
http://{host}:{port}/manager/{command}?{parameters}
where {host} and {port} represent the hostname and port number on which Tomcat is running, {command} represents the Manager command you wish to execute, and {parameters} represents the query parameters that are specific to that command. In the illustrations below, customize the host and port appropriately for your installation.
Most commands accept one or more of the following query parameters:
path - The context path (including the leading slash) of the web application you are dealing with. To select the ROOT web application, specify a zero-length string. NOTE - It is not possible to perform administrative commands on the Manager application itself.
war - URL of a web application archive (WAR) file, or pathname of a directory, that contains the web application. You can use URLs in any of the following formats:
file:/absolute/path/to/a/directory - The absolute path of a directory that contains the unpacked version of a web application. This directory will be attached to the context path you specify without any changes.
file:/absolute/path/to/a/webapp.war - The absolute path of a web application archive (WAR) file. This is valid only for the /deploy command, and is the only acceptable format to that command.
jar:file:/absolute/path/to/a/warfile.war!/ - The URL to a local web application archive (WAR) file. You can use any syntax that is valid for the JarURLConnection class for reference to an entire JAR file.
jar:http://hostname:port/path/to/a/warfile.war!/ - You can also deploy web applications from a remote JAR file. You can use any syntax that is valid for the JarURLConnection class for reference to an entire JAR file.
Each command will return a response in text/plain format (i.e. plain ASCII with no HTML markup), making it easy for both humans and programs to read). The first line of the response wil begin with either OK or FAIL, indicating whether the requested command was successful or not. In the case of failure, the rest of the first line will contain a description of the problem that was encountered. Some commands include additional lines of information as described below.
Internationalization Note - The Manager application looks up its message strings in resource bundles, so it is possible that the strings have been translated for your platform. The examples below show the English version of the messages.
Deploy A New Application
http://localhost:8080/manager/deploy?path=/foo
Upload the web application archive (WAR) file that is specified as the request data in this HTTP PUT request, install it into the appBase directory of our corresponding virtual host, and start it on the context path specified by the path request parameter. The application can later be undeployed (and the corresponding application directory removed) by use of the /undeploy.
NOTE - Since this command requires an HTTP PUT request, it is usable only from tools (such as the custom Ant tasks described below). To install a new web application without copying, consider the /install command described below. This command is the logical opposite of the /undeploy command.
If installation and startup is successful, you will receive a response like this:
OK - Deployed application at context path /foo
Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
Application already exists at path /foo
The context paths for all currently running web applications must be unique. Therefore, you must either remove or undeploy the existing web application using this context path, or choose a different context path for the new one.
Encountered exception
An exception was encountered trying to start the new web application. Check the Tomcat 4 logs for the details, but likely explanations include problems parsing your /WEB-INF/web.xml file, or missing classes encountered when initializing application event listeners and filters.
Invalid context path was specified
The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
No context path was specified
The path parameter is required.
Install A New Application
http://localhost:8080/manager/install?path=/foo&war=file:/path/to/foo
http://localhost:8080/manager/install?path=/bar&war=jar:file:/path/to/bar.war!/
Install and start a new web application, attached to the specified context path (which must not be in use by any other web application). The war parameter specifies a URL (including the file: scheme) for either a directory or a web application archive (WAR) file. The supported syntax for a URL referring to a WAR file is described on the Javadocs page for the java.net.JarURLConnection class. Use only URLs that refer to the entire WAR file. This command is the logical opposite of the /remove command.
If installation and startup is successful, you will receive a response like this:
OK - Installed application at context path /foo
Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
Application already exists at path /foo
The context paths for all currently running web applications must be unique. Therefore, you must either remove or undeploy the existing web application using this context path, or choose a different context path for the new one.
Document base does not exist or is not a readable directory
The URL specified by the war parameter must identify a directory on this server that contains the "unpacked" version of a web application, or the absolute URL of a web application archive (WAR) file that contains this application. Correct the value specified by the war parameter.
Encountered exception
An exception was encountered trying to start the new web application. Check the Tomcat 4 logs for the details, but likely explanations include problems parsing your /WEB-INF/web.xml file, or missing classes encountered when initializing application event listeners and filters.
Invalid application URL was specified
The URL for the directory or web application that you specified was not valid. Such URLs must start with file:, and URLs for a WAR file must end in ".war".
Invalid context path was specified
The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
No context path was specified
The path parameter is required.
List Currently Deployed and Installed Applications
http://localhost:8080/manager/list
List the context paths, current status (running or stopped), and number of active sessions for all currently deployed and installed web applications. A typical response immediately after starting Tomcat might look like this:
OK - Listed applications for virtual host localhost
/webdav:running:0
/examples:running:0
/manager:running:0
/:running:0
Reload An Existing Application
http://localhost:8080/manager/reload?path=/examples
Signal an existing application to shut itself down and reload. This can be useful when you've recompiled classes on an application that is not configured with the reloadable="true" attribute in its <Context> entry in $CATALINA_HOME/conf/server.xml, or when you've made other changes (such as to conf/web.xml) that are not automatically recognized by Tomcat.
If this command succeeds, you will see a response like this:
OK - Reloaded application at context path /examples
Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
Encountered exception
An exception was encountered trying to restart the web application. Check the Tomcat 4 logs for the details.
Invalid context path was specified
The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
No context exists for path /foo
There is no deployed or installed application on the context path that you specified.
No context path was specified
The path parameter is required.
Reload note supported on WAR deployed at path /foo
Currently, application reloading (to pick up changes to the classes or web.xml file) is not supported when a web application is installed directly from a WAR file. It only works when the web application is installed from an unpacked directory. If you are using a WAR file, you should remove and then install the application again to pick up your changes.
Remove an Existing Application
http://localhost:8080/manager/remove?path=/examples
Signal an existing application to gracefully shut itself down, and then remove it from Tomcat (which also makes this context path available for reuse later). This command is the logical opposite of the /install command.
If this command succeeds, you will see a response like this:
OK - Removed application at context path /examples
Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
Encountered exception
An exception was encountered trying to remove the web application. Check the Tomcat 4 logs for the details.
Invalid context path was specified
The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
No context exists for path /foo
There is no deployed or installed application on the context path that you specified.
No context path was specified
The path parameter is required.
Session Statistics
http://localhost:8080/manager/sessions?path=/examples
Display the default session timeout for a web application, and the number of currently active sessions that fall within ten-minute ranges of their actual timeout times. For example, after restarting Tomcat and then executing one of the JSP samples in the /examples web app, you might get something like this:
OK - Session information for application at context path /examples
Default maximum session inactive interval 30 minutes
30 - <40 minutes:1 sessions
Start an Existing Application
http://localhost:8080/manager/start?path=/examples
Signal a stopped application to restart, and make itself available again. Stopping and starting is useful, for example, if the database required by your application becomes temporarily unavailable. It is usually better to stop the web application that relies on this database, rather than letting users continuously encounter database exceptions.
If this command succeeds, you will see a response like this:
OK - Started application at context path /examples
Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
Encountered exception
An exception was encountered trying to start the web application. Check the Tomcat 4 logs for the details.
Invalid context path was specified
The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
No context exists for path /foo
There is no deployed or installed application on the context path that you specified.
No context path was specified
The path parameter is required.
Stop an Existing Application
http://localhost:8080/manager/stop?path=/examples
Signal an existing application to make itself unavailable, but leave it deployed or installed. Any request that comes in while an application is stopped will see an HTTP error 404, and this application will show as "stopped" on a list applications command.
If this command succeeds, you will see a response like this:
OK - Stopped application at context path /examples
Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
Encountered exception
An exception was encountered trying to stop the web application. Check the Tomcat 4 logs for the details.
Invalid context path was specified
The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
No context exists for path /foo
There is no deployed or installed application on the context path that you specified.
No context path was specified
The path parameter is required.
Undeploy an Existing Application
http://localhost:8080/manager/undeploy?path=/examples
WARNING - This command will delete the contents of the web application directory if it exists within the appBase directory (typically "webapps") for this virtual host . If you simply want to take an application out of service, you should use the /remove command instead.
Signal an existing application to gracefully shut itself down, and remove it from Tomcat (which also makes this context path available for reuse later). In addition, the document root directory is removed, if it exists in the appBase directory (typically "webapps") for this virtual host. This command is the logical opposite of the /deploy command.
If this command succeeds, you will see a response like this:
OK - Undeployed application at context path /examples
Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
Encountered exception
An exception was encountered trying to undeploy the web application. Check the Tomcat 4 logs for the details.
Invalid context path was specified
The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
No context exists for path /foo
There is no deployed or installed application on the context path that you specified.
No context path was specified
The path parameter is required.
Executing Manager Commands With Ant
In addition to the ability to execute Manager commands via HTTP requests, as documented above, Tomcat 4 includes a convenient set of Task definitions for the Ant (version 1.4 or later) build tool. In order to use these commands, you must perform the following setup operations:
Download the binary distribution of Ant from http://jakarta.apache.org/ant. You must use version 1.4 or later.
Install the Ant distribution in a convenient directory (called ANT_HOME in the remainder of these instructions).
Copy the file server/lib/catalina-ant.jar from your Tomcat 4 installation into Ant's library directory ($ANT_HOME/lib).
Add the $ANT_HOME/bin directory to your PATH environment variable.
Configure at least one username/password combination in your Tomcat user database that includes the manager role.
To use custom tasks within Ant, you must declare them first with a <taskdef> element. Therefore, your build.xml file might look something like this:
<project name="My Application" default="compile" basedir=".">
<-- Configure the directory into which the web application is built -->
<property name="build" value="${basedir}/build"/>
<-- Configure the context path for this application -->
<property name="path" value="/myapp"/>
<-- Configure properties to access the Manager application -->
<property name="url" value="http://localhost:8080/manager"/>
<property name="username" value="myusername"/>
<property name="password" value="mypassword"/>
<-- Configure the custom Ant tasks for the Manager application -->
<taskdef name="deploy" classname="org.apache.catalina.ant.DeployTask"/>
<taskdef name="install" classname="org.apache.catalina.ant.InstallTask"/>
<taskdef name="list" classname="org.apache.catalina.ant.ListTask"/>
<taskdef name="reload" classname="org.apache.catalina.ant.ReloadTask"/>
<taskdef name="remove" classname="org.apache.catalina.ant.RemoveTask"/>
<taskdef name="start" classname="org.apache.catalina.ant.StartTask"/>
<taskdef name="stop" classname="org.apache.catalina.ant.StopTask"/>
<taskdef name="undeploy" classname="org.apache.catalina.ant.UndeployTask"/>
<-- Executable Targets -->
<target name="compile" description="Compile web application">
... construct web application in ${build} subdirectory ...
</target>
<target name="install" description="Install web application"
depends="compile">
<install url="${url}" username="${username}" password="${password}"
path="${path}" war="file://${build}"/>
</target>
<target name="reload" description="Reload web application"
depends="compile">
<reload url="${url}" username="${username}" password="${password}"
path="${path}"/>
</target>
<target name="remove" description="Remove web application">
<remove url="${url}" username="${username}" password="${password}"
path="${path}"/>
</target>
</project>
Now, you can execute commands like ant install to install th applcation to a running instance of Tomcat, or ant reload to tell Tomcat to reload it. Note also that most of the interesting values in this build.xml file are defined as replaceable properties, so you can override their values from the command line. For example, you might consider it a security risk to include the real manager password in your build.xml file's source code. To avoid this, omit the password property, and specify it from the command line:
ant -Dpassword=secret deploy

How to delete conext entries in JNDI tree after undeployment?

Hi,
When I deploy an EAR or JAR file with EJBs, they bind in the JNDI server.
When I undeploy the application the beans are no longer bound to the JNDI
tree, but the contexts they created remain.
For example, I deploy a bean that binds its home object to the following
entry in the JNDI:
myapp/mymodule/MyBean
When I undeploy MyBean, the context myapp/mymodule remain.
Is there an utility to remove these entries or do I have to develop my own
utility? I did not find anything in the administration console to do this.
This has been a source of some trouble, because sometimes I get error
messages when I want to redeploy the beans.
Thanks in advance,
Vegeta

Please don't cross post. see my reply in the ejb newsgroup.
Thanks,
Michael
Vegeta wrote:
Hi,
When I deploy an EAR or JAR file with EJBs, they bind in the JNDI server.
When I undeploy the application the beans are no longer bound to the JNDI
tree, but the contexts they created remain.
For example, I deploy a bean that binds its home object to the following
entry in the JNDI:
myapp/mymodule/MyBean
When I undeploy MyBean, the context myapp/mymodule remain.
Is there an utility to remove these entries or do I have to develop my own
utility? I did not find anything in the administration console to do this.
This has been a source of some trouble, because sometimes I get error
messages when I want to redeploy the beans.
Thanks in advance,
Vegeta--
Michael Young
Developer Relations Engineer
BEA Support

Undeploy EAR on Oracle10gAS 10.1.2 using ANT

I am using JDeveloper10g - 10.1.2 on my local machine and Oracle10gAS - 10.1.2 on a remote machine.
I am able to deploy remotely using ANT task oc4j_remote_deploy.jar, but UNDEPLOY doesnt work. Anybody has a readymade UNDEPLOY task on a remote machine?
Also, while using remote DEPLOY task, I noticed that though it takes the Application Name as a parameter, it deploys with the first part of EAR filename. For example, if I specify shop.ear for ear file name and SHOPALR8 for applciation name, still it deploys shop.ear with the name as shop. Any patch available for this?
Any pointers will be highly appreciated.
Thanks,
Aravind.

That seems to be fine. The warning message '[05/Mar/2013:16:39:01 +0800] [warning 11917] [ecid: -] SSL wallet Origin Server Wallet file SYSTEM DEFAULT LOCATION (See Documentation)\ewallet.p12 does not exist." wou;d however indicate that the Web Cache has been configured with SSL so it is quit odd.
Given the fact that it is a warning only, I would expect the web cache to be available. But I noticed a different error as well :
{code}
[05/Mar/2013:16:39:04 +0800] [alert 11201] [ecid: -] OracleAS Web Cache is unable to resolve the IP address of xxxxxxx. Check your DNS setup.
[05/Mar/2013:16:39:04 +0800] [alert 9609] [ecid: -] The server process could not initialize
{code}
That would suggest that you have defined a host name which cannot be resolved to IP number. That may cause the web cache not to start.
Thanks,
EJ

Labview Web Services: How to 'undeploy' web services

I have created the example web services:
Address Book project in labview\examples\comm\webservices\address book for an example of a Web service that handles post data, streaming output, static content, and HTML forms.
Weather Monitor project in labview\examples\comm\webservices\weather monitor
for an example of a Web service that publishes simulated weather statistics.
Using Web UI Builder, they are always included in the list of available web services when I Import Web Service.
How do I get rid of them?
Solved!
Go to Solution.

Hello,
To remove them from the list, you need to undeploy the web service. There are two ways to do this: you can turn off Web Services in Distributed System Manager or you can delete the Web Service file.
To enable the ability to control Web Services in Distributed System Manager follow the steps in KnowledgeBase 5BLESQW5.
To remove an actively running web service go to C:\ProgramData\National Instruments\WebServices\aws (Windows 7) and remove the directory that has your web service name. Because we also cashe the LVWS files in another location on disk we will also have to remove that to ensure the Web service is not redeployed by the system web server at some other time. Go to C:\Windows\System32\config\systemprofile\Documents\LabVIEW Data\WebServices\Standalone and remove the LVWS file associated with you web service.
Hope this helps!
Julianne K
Systems Engineer, Embedded Systems
Certified LabVIEW Architect, Certified LabVIEW Embedded Systems Developer
National Instruments

Cannot Run JAX-RPC Hello Service Example

Hello,
I am trying to run the helloservice example from the Java Web Services Tutorial v 1.3 (Chapter 12). Upon running the ant build task, I get the following error.
BUILD FAILED
file:C:/jwstutorial13/examples/jaxrpc/common/targets.xml:151: Warning: Could not
find file C:\jwstutorial13\examples\jaxrpc\helloservice\build\model.gz to copy.
I tried running the ant generate-sei-service task separately. This appears to complete successfully, yet, there is no model file generated.
Any help/suggestions/insights would be very much appreciated!
Thanks,
Sheila

Thanks!
I did that before posting my original message. I'm obviously missing something (noting jumps out at me, as far as being wrong.)
My files look like this:
File: build.xml (C:\jwstutorial13\examples\jaxrpc\helloservice\build.xml)
<!DOCTYPE project [
<!ENTITY jaxrpctargets SYSTEM "../common/targets.xml">
]>
<project name="jaxrpc-tutorial" default="build" basedir=".">
<property file="../../common/build.properties"/>
<property file="../common/build.properties"/>
<property file="build.properties"/>
&jaxrpctargets;
<target name="build" depends="build-service"
description="Executes the targets needed to build the service.">
</target>
</project>
==================================================================================
File: build.properties (C:\jwstutorial13\examples\jaxrpc\helloservice\build.properties).
example=helloservice
war.path=${tut.root}/examples/jaxrpc/helloservice/${dist}/${deployable.war}
context.path=${hello.context}
portable.war=${context.path}-portable.war
deployable.war=${context.path}.war
==================================================================================
File: build.properties (C:\jwstutorial13\examples\jaxrpc\common\build.properties)
# This file contains properties common to the tutorial examples
# for JAX-RPC.
# tut.root=C:/wspack-docs
tut.root=${tutorial.install}
hello.context=hello-jaxrpc
secure.context=secure-jaxrpc
mutualauth.context=secure-mutualauth
url.pattern=/hello
key.store=${tutorial.home}/jwstutorial13/examples/jaxrpc/mutualauth/keystore.jks
key.store.password=changeit
trust.store=${tutorial.home}/jwstutorial13/examples/jaxrpc/mutualauth/cacerts.jks
trust.store.password=changeit
hello.endpoint=http://${host}:${port}/${hello.context}${url.pattern}
secure.endpoint=http://${host}:${port}/${secure.context}${url.pattern}
mutualauth.endpoint=https://${host}:${secure.port}/${mutualauth.context}${url.pattern}
build=build
src=src
dist=dist
client.jar=client.jar
model.file=model.gz
config.wsdl.file=config-wsdl.xml
config.interface.file=config-interface.xml
jwsdp.shared=${jwsdp.home}/jwsdp-shared
jaxp.home=${jwsdp.home}/jaxp
jaxrpc.home=${jwsdp.home}/jaxrpc
saaj.home=${jwsdp.home}/saaj
wscompile.dir=${jaxrpc.home}/bin
wsdeploy.dir=${jaxrpc.home}/bin
javamail.jar=${jwsdp.shared}/lib/mail.jar
jaf.jar=${jwsdp.shared}/lib/activation.jar
jaxp-api.jar=${jaxp.home}/lib/jaxp-api.jar
dom.jar=${jaxp.home}/lib/endorsed/dom.jar
sax.jar=${jaxp.home}/lib/endorsed/sax.jar
xalan.jar=${jaxp.home}/lib/endorsed/xalan.jar
xercesImpl.jar=${jaxp.home}/lib/endorsed/xercesImpl.jar
jaxrpc-api.jar=${jaxrpc.home}/lib/jaxrpc-api.jar
jaxrpc-impl.jar=${jaxrpc.home}/lib/jaxrpc-impl.jar
jaxrpc-spi.jar=${jaxrpc.home}/lib/jaxrpc-spi.jar
commons-logging.jar=${jwsdp.shared}/lib/commons-logging.jar
saaj-api.jar=${saaj.home}/lib/saaj-api.jar
saaj-impl.jar=${saaj.home}/lib/saaj-impl.jar
relaxngDatatype.jar=${jwsdp.shared}/lib/relaxngDatatype.jar
xsdlib.jar=${jwsdp.shared}/lib/xsdlib.jar
jax-qname.jar=${jwsdp.shared}/lib/jax-qname.jar
ant.jar=${jwsdp.home}/apache-ant/lib/ant.jar
==================================================================================
This is where I thought the problem might be, but I can't determine what's wrong. The pathelements in this file, were set in build.properties ((C:\jwstutorial13\examples\jaxrpc\common\build.properties), referenced above.
File: targets.xml (C:\jwstutorial13\examples\jaxrpc\common\targets.xml)

<path id="compile.classpath">
<pathelement location="${javamail.jar}"/>
<pathelement location="${jaf.jar}"/>
<pathelement location="${jaxp-api.jar}"/>
<pathelement location="${dom.jar}"/>
<pathelement location="${sax.jar}"/>
<pathelement location="${xalan.jar}"/>
<pathelement location="${xercesImpl.jar}"/>
<pathelement location="${jaxrpc-api.jar}"/>
<pathelement location="${jaxrpc-impl.jar}"/>
<pathelement location="${jaxrpc-spi.jar}"/>
<pathelement location="${commons-logging.jar}"/>
<pathelement location="${saaj-api.jar}"/>
<pathelement location="${saaj-impl.jar}"/>
<pathelement location="${relaxngDatatype.jar}"/>
<pathelement location="${xsdlib.jar}"/>
<pathelement location="${jax-qname.jar}"/>
<pathelement location="${ant.jar}"/>
<pathelement location="${build}/shared"/>
</path>
<path id="run.classpath">
<path refid="compile.classpath"/>
<pathelement location="${dist}/${client.jar}"/>
</path>
<taskdef name="deploy" classname="org.apache.catalina.ant.DeployTask" />
<taskdef name="undeploy" classname="org.apache.catalina.ant.UndeployTask" />
<taskdef name="list" classname="org.apache.catalina.ant.ListTask" />
<taskdef name="start" classname="org.apache.catalina.ant.StartTask" />
<taskdef name="stop" classname="org.apache.catalina.ant.StopTask" />
<taskdef name="install" classname="org.apache.catalina.ant.InstallTask"/>
<taskdef name="reload" classname="org.apache.catalina.ant.ReloadTask"/>
<taskdef name="remove" classname="org.apache.catalina.ant.RemoveTask"/>
<target name="install" description="Install web application"
depends="build">
<install url="${url}" username="${username}" password="${password}"
path="/${context.path}" war="file:${example.path}/${build}"/>
</target>
<target name="deploy"
description="Deploys a Web application">
<deploy url="${url}" username="${username}" password="${password}"
path="/${context.path}" war="file:${war.path}"
/>
</target>
<target name="undeploy"
description="Undeploys a Web application">
<undeploy url="${url}" username="${username}" password="${password}"
path="/${context.path}"
/>
</target>
<target name="redeploy"
description="Undeploys and deploys a Web aplication">
<antcall target="undeploy" />
<antcall target="deploy" />
</target>
<target name="list"
description="Lists Web applications">
<echo message="Listing the applications...."/>
<list
url="${url}"
username="${username}"
password="${password}"
/>
</target>
<target name="start"
description="Starts a Web application">
<echo message="Starting the application...."/>
<start
url="${url}"
username="${username}"
password="${password}"
path="/${context.path}"
/>
</target>
<target name="stop"
description="Stops a Web application">
<echo message="Stopping the application...."/>
<stop
url="${url}"
username="${username}"
password="${password}"
path="/${context.path}"
/>
</target>
<target name="prepare"
description="Creates the build directory" >
<echo message="Creating the required directories...." />
<mkdir dir="${build}/${example}" />
</target>
<target name="prepare-dist"
description="Creates the dist directory" >
<echo message="Creating the required directories...." />
<mkdir dir="${dist}" />
</target>
<target name="set-wscompile" >
<condition property="wscompile" value="${wscompile.dir}/wscompile.bat">
<os family="windows"/>
</condition>
<condition property="wscompile" value="${wscompile.dir}/wscompile.sh">
<not>
<os family="windows"/>
</not>
</condition>
</target>
<target name="set-wsdeploy" >
<condition property="wsdeploy" value="${wsdeploy.dir}/wsdeploy.bat">
<os family="windows"/>
</condition>
<condition property="wsdeploy" value="${wsdeploy.dir}/wsdeploy.sh">
<not>
<os family="windows"/>
</not>
</condition>
</target>
<target name="compile-service" depends="prepare"
description="Compiles the server-side source code">
<echo message="Compiling the server-side source code...."/>
<javac srcdir="${src}"
destdir="${build}"
includes="*.java"
excludes="*Client.java">
<classpath refid="compile.classpath"/>
</javac>
</target>
<target name="setup-web-inf"
description="Copies files to build/WEB-INF">
<echo message="Setting up ${build}/WEB-INF...."/>
<delete dir="${build}/WEB-INF" />
<copy todir="${build}/WEB-INF/classes/${example}">
<fileset dir="${build}/${example}" />
<fileset dir="${build}/${example}" />
</copy>
<copy file="${build}/${model.file}" todir="${build}/WEB-INF" />
<copy file="web.xml" todir="${build}/WEB-INF" />
<copy file="jaxrpc-ri.xml" todir="${build}/WEB-INF" />
</target>
<target name="package-service" depends="prepare-dist"
description="Packages the WAR file">
<echo message="Packaging the WAR...."/>
<delete file="${dist}/${portable.war}" />
<jar jarfile="${dist}/${portable.war}" >
<fileset dir="${build}" includes="WEB-INF/**" />
</jar>
</target>
<target name="process-war" depends="set-wsdeploy"
description="Runs wsdeploy to generate the ties and
create a deployable WAR file">
<delete file="dist/${deployable.war}" />
<antcall target="run-wsdeploy">
<param name="param1" value="-o dist/${deployable.war} dist/${portable.war}"/>
</antcall>
</target>
<target name="run-wscompile" depends="prepare,set-wscompile"
description="Runs wscompile">
<echo message="Running wscompile:"/>
<echo message=" ${wscompile} ${param1}"/>
<exec executable="${wscompile}">
<arg line="${param1}"/>
</exec>
</target>
<target name="run-wsdeploy" depends="prepare,set-wsdeploy"
description="Runs wsdeploy">
<echo message="Running wsdeploy:"/>
<echo message=" ${wsdeploy} ${param1}"/>
<exec executable="${wsdeploy}">
<arg line="${param1}"/>
</exec>
</target>
<target name="generate-sei-service"
description="Runs wscompile to generate the model file">
<antcall target="run-wscompile">
<param name="param1" value="-define -d ${build} -nd ${build}
-classpath ${build} ${config.interface.file}
-model ${build}/${model.file}"/>
</antcall>
<delete file="${build}/MyHelloService.wsdl"/>
</target>
<target name="generate-interface"
description="Runs wscompile to generate the service endpoint
interface">
<antcall target="run-wscompile">
<param name="param1" value="-import -d ${build} -nd ${build}
-f:norpcstructures -classpath ${build} ${config.wsdl.file}"/>
</antcall>
</target>
<target name="generate-stubs"
description="Runs wscompile to generate the client stub classes">
<antcall target="run-wscompile">
<param name="param1" value="-gen:client -d ${build}
-classpath ${build} ${config.wsdl.file}"/>
</antcall>
</target>
<target name="compile-client" depends="prepare"
description="Compiles the client-side source code" >
<echo message="Compiling the client source code...."/>
<javac srcdir="${src}"
destdir="${build}"
includes="*.java">
<classpath refid="compile.classpath"/>
<classpath path="${build}" />
</javac>
</target>
<target name="package-client" depends="prepare-dist"
description="Builds the JAR file that contains the client">
<echo message="Building the client JAR file...."/>
<delete file="${dist}/${client.jar}" />
<jar jarfile="${dist}/${client.jar}" >
<fileset dir="${build}" />
</jar>
</target>
<target name="package-dynamic" depends="prepare-dist"
description="Builds the JAR file that contains the dynamic proxy client">
<echo message="Building the client JAR file...."/>
<delete file="${dist}/${client.jar}" />
<jar jarfile="${dist}/${client.jar}" >
<fileset dir="${build}" includes="**/HelloClient.class" />
<fileset dir="${build}" includes="**/HelloIF.class" />
</jar>
</target>
<target name="build-service" depends="clean,compile-service,generate-sei-service,
setup-web-inf,package-service,process-war"
description="Executes the targets needed to build the service.">
</target>
<target name="build-static" depends="clean,generate-stubs,
compile-client,package-client"
description="Executes the targets needed to build a static stub client.">
</target>
<target name="build-dii" depends="clean,prepare,compile-client,package-client"
description="Executes the targets needed to build a DII client.">
</target>
<target name="build-dynamic" depends="clean,prepare,generate-interface,
compile-client,package-dynamic"
description="Executes the targets needed to build a dynamic proxy client.">
</target>
<target name="build-webclient" depends="clean,generate-stubs"
description="Executes the targets needed to build a web client.">
</target>
<target name="run-client"
description="Runs a stand-alone (non-J2EE) client">
<java classname="${client.class}" fork="yes" >
<arg line="${endpoint.address}" />
<classpath refid="run.classpath" />
</java>
</target>
<target name="run-secure-client"
description="Runs a client with basic authentication over SSL">
<java classname="${client.class}" fork="yes" >
<arg line="${username} ${password} ${endpoint.address}" />
<classpath refid="run.classpath" />
</java>
</target>
<target name="run-mutualauth-client"
description="Runs a client with mutual authentication over SSL">
<java classname="${client.class}" fork="yes" >
<arg line="${key.store} ${key.store.password}
${trust.store} ${trust.store.password}
${endpoint.address}" />
<classpath refid="run.classpath" />
</java>
</target>
<target name="clean"
description="Removes the build directory">
<delete dir="${build}" />
</target>
<target name="listprops" depends="set-wscompile"
description="Displays values of some of the properties of this
build file">
<echo message="jaxrpc.home = ${jaxrpc.home}" />
<echo message="wscompile = ${wscompile}" />
<echo message="build = ${build}" />
<echo message="src = ${src}" />
<echo message="dist = ${dist}" />
<echo message=" " />
<echo message="example = ${example}" />
<echo message="client.jar = ${client.jar}" />
<echo message="client.class = ${client.class}" />
<echo message=" " />
<echo message="host = ${host}" />
<echo message="port = ${port}" />
<echo message="secure.port = ${secure.port}" />
<echo message="trust.store = ${trust.store}" />
<echo message="trust.store.password = ${trust.store.password}" />
<echo message=" " />
<echo message="username = ${username}" />
<echo message="password = ${password}" />
<echo message="url = ${url}" />
<echo message=" " />
<echo message="context.path = ${context.path}" />
<echo message="secure.context.path = ${secure.context.path}" />
<echo message="url.pattern = ${url.pattern}" />
<echo message="endpoint.address = ${endpoint.address}" />
<echo message="secure.endpoint = ${secure.endpoint}" />
<echo message=" " />
<echo message="war.path = ${war.path}" />
<echo message="portable.war = ${portable.war}" />
<echo message="deployable.war = ${deployable.war}" />
</target>
==================================================================================
File: targets.xml ( C:\jwstutorial13\examples\common\targets.xml)
<taskdef name="list" classname="org.apache.catalina.ant.ListTask"/>
<taskdef name="install" classname="org.apache.catalina.ant.InstallTask"/>
<taskdef name="reload" classname="org.apache.catalina.ant.ReloadTask"/>
<taskdef name="remove" classname="org.apache.catalina.ant.RemoveTask"/>
<taskdef name="deploy" classname="org.apache.catalina.ant.DeployTask"/>
<taskdef name="undeploy" classname="org.apache.catalina.ant.UndeployTask"/>
<target name="list" description="List web applications" >
<list url="${url}" username="${username}" password="${password}" />
</target>
<target name="install" description="Install web application"
depends="build">
<install url="${url}" username="${username}" password="${password}"
path="/${context.path}" war="file:${build}"/>
</target>
<target name="reload" description="Reload web application"
depends="build">
<reload url="${url}" username="${username}" password="${password}"
path="/${context.path}"/>
</target>
<target name="remove" description="Remove web application">
<remove url="${url}" username="${username}" password="${password}"
path="/${context.path}"/>
</target>
<target name="package"
description="Packages the WAR file">
<echo message="Packaging the WAR...."/>
<delete file="dist/${war.file}" />
<jar jarfile="dist/${war.file}" >
<fileset dir="${build}" />
</jar>
</target>
<target name="deploy" description="Deploy a Web application">
<deploy url="${url}" username="${username}" password="${password}"
path="/${context.path}" war="file:/${example.path}/dist/${war.file}"
/>
</target>

<target name="undeploy" description="Undeploy web application">
<undeploy url="${url}" username="${username}" password="${password}"
path="/${context.path}"/>
</target>
==================================================================================
File: build.properties (C:\jwstutorial13\examples\common\build.properties)
tutorial.home=C:/jwstutorial13
tutorial.install=${tutorial.home}
username=******
password=********
host=localhost
port=8080
secure.port=8443
url=http://${host}:${port}/manager
==================================================================================
Finally, here is how I've got my PATH Environmental Variable Set:
PATH:
%JWSDP_HOME%\apache-ant\bin;%JWSDP_HOME%\jwsdp-shared\bin;%JWSDP_HOME%\bin;%JAVA_HOME%\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\system32\WBEM;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\
I set this up according to the instructions at the beginning of the tutorial.
JWSDP_HOME: C:\jwsdp-1.3
JAVA_HOME: C:\j2sdk1.4.1_05
Thanks again for your help.
Sheila

How to undeploy (delete) a Java application

Hi all,
i have deployed using the SAP Netweaver developer studio and the SDM tool a specific Java application.
As i delete it on my PC i can not re-deploy it because the system tells me that there is already a application with the same name.
How can i delete it directly on the server using for example the deploytool tool or another tool ?
Thank in advance,
Eric.

Hello,
You can also undeploy the application using the SDM tool. Launch the tool by running the remotegui from your usr\sap\SID\JC00\SDM\program. enter your sdm password and then go to the undeployment tab. Pick the application you want to undeploy and add it to the right hand pane and follow the steps in the wizard
Regards
Abdul

Problem undeploying/deploying application through command line

Apologies for the newbie question - I've already trawled through the
online help, but to no avail.
I'm trying to uninstall an earlier .ear file and installing a newer
one - however, the code below in my batch file doesn't work:
java weblogic.Deployer -user admin -password holland
C:\bea\user_projects\hypotheekplanner\woscb.ear -name woscb -targets
woscb.ear@wos -undeploy
wzunzip -o C:\distribution\woscb.ear C:\distribution\war
wzunzip -o C:\distribution\war\woscb.war C:\distribution\ear
copy /y C:\distribution\web_xml\woscb\web.xml C:\distribution\ear
del /Q C:\distribution\war\woscb.war
wzzip C:\distribution\war\woscb.war C:\distribution\ear\*.*
wzzip C:\bea\user_projects\hypotheekplanner\woscb.ear
C:\distribution\war\woscb.war
del /Q C:\distribution\war\*.*
del /Q C:\distribution\ear\*.*
java weblogic.Deployer -user admin -password holland -stage -source
C:\bea\user_projects\hypotheekplanner\woscb.ear -name woscb -targets
woscb.war@wos -deploy
Note that the whole unzip/zip operation is for making sure the
application properties (as defined in web.xml) do not have to be
adjusted through the console panel.
So what am I doing wrong?
Thanks in advance for any pointers,
Martin

Martin:
Ok, so your going to use batch........ I am not sure how much community your
going to get around this, not because people don't want to help but because
95% of all java projects use ANT to do this very thing, there just isn't a
knowledge base around using batch and commandline winzip tools. Writing
"scripts" that automate deployment is a "good thing", its just that the tool
of choice for most of the community is ANT, not batch.
So consequently I am having a little bit of a hard time trying to follow
what your are attempting to do.
java weblogic.Deployer -user admin -password holland
C:\bea\user_projects\hypotheekplanner\woscb.ear -name woscb -targets
woscb.ear@wos -undeployAre you specifying targets because you really do in this case have more than
one target (wos) defined? Additionally the syntax of "<component>@<server
N>>" only applies to components INSIDE an ear, if your deploying/undeploy
the entire ear you don't need the component, all you need is "-targets wos".
Perhaps attaching your config.xml will help.
Can you restate your goal?
Is it to update the settings of web.xml in a war that is in an ear and
redeploy? You don't have to do an undeploy to achieve this, just
a -deploy(-activate) will work on an existing deployment, if the application
is already deployed, it -deploy/-activate will do a re-deploy/activate.
I really dont follow this at all not being familiar with wzunzip.
>
wzunzip -o C:\distribution\woscb.ear C:\distribution\warWhy are you unzipping the contents of .ear into the directory war?
wzunzip -o C:\distribution\war\woscb.war C:\distribution\earWhy are you unzipping the contents of .war into the directory ear?
copy /y C:\distribution\web_xml\woscb\web.xml C:\distribution\ear
del /Q C:\distribution\war\woscb.war
wzzip C:\distribution\war\woscb.war C:\distribution\ear\*.*
wzzip C:\bea\user_projects\hypotheekplanner\woscb.ear
C:\distribution\war\woscb.warWhat is this line c:\distribution\war\woscb.war doing? is this something
meant to be on the previous line?
del /Q C:\distribution\war\*.*
del /Q C:\distribution\ear\*.*
java weblogic.Deployer -user admin -password holland -stage -source
C:\bea\user_projects\hypotheekplanner\woscb.ear -name woscb -targets
woscb.war@wos -deployHere the component would be necessary/required/useful since the war file is
what your trying to update.
Why are you using -stage is this because the server "wos" is a managed
server, if so -stage is the default for managed servers and uncessary. If
you only have one server and it is "wos", then it is the admin server and
you dont want to pass -stage.
To help this all out a small, isolated, simplified, reproducible test case
might help.
Something along the lines of an examples.zip I can download and do:
1) cd /temp
2)jar xvf example.zip
3) cd user_projects\
4) deploy.bat (which deploys test.ear)
-I can go hit the web-app in the browser to "see" something in web.xml that
is the first version.
5) update.bat (which attempts to update the web.xml in the webapp and
redeploy)
-I can go hit the web-app in the browser to "see" something in web.xml that
is the updated version.
I could cook this up in ANT, but that wont help you. ;)
cheers
mbg
>
"Martin" <[email protected]> wrote in message
news:[email protected]...
It doesn't work in that it doesn't deploy the new ear file - contained
therein is a version.html file with the build number, if I look up the
file in a browser it shows up the old build number instead of the
build number of the file I just tried to deploy. So why?
And we prefer to do it batchwise, and we're not going to switch to 8.1
anytime soon.
Martin
Ok, so the next question is why doesnt it work? What is the error/stack
trace?
As a suggestion I would reccomend using ANT vs. batch files.
And 8.1 has a lot of new stuff to help you out.
Cheers
mbg
"Martin" <[email protected]> wrote in message
news:[email protected]...
Oops....7.0.
Martin
"Mark Griffith" <[email protected]> wrote in message
news:<[email protected]>...
Martin:
Lets start with what version of WLS are you using? 7.0 or 8.1?
Cheers
mbg
"Martin" <[email protected]> wrote in message
news:[email protected]...
Apologies for the newbie question - I've already trawled through
the
online help, but to no avail.
I'm trying to uninstall an earlier .ear file and installing anewer
one - however, the code below in my batch file doesn't work:
java weblogic.Deployer -user admin -password holland
C:\bea\user_projects\hypotheekplanner\woscb.ear -namewoscb -targets
woscb.ear@wos -undeploy
wzunzip -o C:\distribution\woscb.ear C:\distribution\war
wzunzip -o C:\distribution\war\woscb.war C:\distribution\ear
copy /y C:\distribution\web_xml\woscb\web.xml C:\distribution\ear
del /Q C:\distribution\war\woscb.war
wzzip C:\distribution\war\woscb.war C:\distribution\ear\*.*
wzzip C:\bea\user_projects\hypotheekplanner\woscb.ear
C:\distribution\war\woscb.war
del /Q C:\distribution\war\*.*
del /Q C:\distribution\ear\*.*
java weblogic.Deployer -user admin -passwordholland -stage -source
C:\bea\user_projects\hypotheekplanner\woscb.ear -namewoscb -targets
woscb.war@wos -deploy
Note that the whole unzip/zip operation is for making sure the
application properties (as defined in web.xml) do not have to be
adjusted through the console panel.
So what am I doing wrong?
Thanks in advance for any pointers,
Martin

Undeploying Library Project

Hello,
is there another possibility to undeploy a library project as using the sdm (RemotGUI)?
Problem is, when starting the RemoteGUI and selecting the undeployment-TAB the remoteGUI seems to hang. No more action can be done. I also removed the jar-files from the filesystem, but they will be redeployed if the j2ee engine is restartet. There are no log in the sdm_remotegui.err/out.
Any ideas?
best regards Oliver Walter

Hi Olivier,
you can use the Telnet administrator to remove a library from the server. Here are the steps:
1. Connect the telnet using telnet <host> <telnet_port>. For example, for a system with instance number 00 on localhost, the right command will be telnet localhost 50008.
2. Enter Administrator user and password.
3. execute jump 0
4. Execute add deploy
5. Use the change_lib command with the -r option to remove the library you want. For more info on the change_lib command, see http://help.sap.com/saphelp_nw04/helpdata/en/ae/01343ef3f9ff2de10000000a114084/frameset.htm
Hope that helps!

Undeploying java components

Hi
I have installed java components for ess mss from the master dvd on the PORTAL..thou this is wrong since it needs to be in the WAS. How can I uninstall them. I have tried to use sdm to undeploy them but i do not find the compnents there. I searched for sap.com/essaraddr for example to undeploy it..but it is not listed in the undeployment tab.
Am i going about this the wrong way?
Please assist.
Thank you
Namira

You do not install on the Portal. Instead, you use SDM to install MSS & ESS. SDM is part of WebAS and it should be OK.
Portal, MSS & ESS are applications running on top of WebAS. SDM is the tool you use for Instllation of applications.
Let me know if my understanding of your question is wrong.

Undeployment poor performance

Hi,
JDevoloper has poor performance when deploying und undeploying a application. Below is a example: 3 minutes!
Maybe it's caused by the BEA-000449 messages? How can I avoid this messages and how can I speed up deployment and esp
Any suggestions?
Stefan
Details
[Application termination requested. Undeploying application myapp.]
[09:45:29 AM] ---- Deployment started. ----
[09:45:29 AM] Target platform is (Weblogic 10.3).
<17.12.2009 09:46 Uhr MEZ> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it during the configured idle timeout of 5 secs>
[09:47:23 AM] Undeploying Application...
<17.12.2009 09:47 Uhr MEZ> <Warning> <Deployer> <BEA-149085> <No application version was specified for application 'myapp'. The undeploy operation will be performed against the currently active version 'V2.0'.>
[09:47:24 AM] Application Undeployed Successfully.
<17.12.2009 09:47 Uhr MEZ> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it during the configured idle timeout of 5 secs>
<17.12.2009 09:48 Uhr MEZ> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it during the configured idle timeout of 5 secs>
[09:48:37 AM] Elapsed time for deployment: 3 minutes, 9 seconds
[09:48:37 AM] ---- Deployment finished. ----
[Application myapp stopped and undeployed from Server Instance IntegratedWebLogicServer]

Hi Uma,
Did you finally resolve this issue?
I am facing the same problem.
Thanks,
Vibhu

Help with helloworld example

Hi,
I'm new to web services. I downloaded and tried the helloworld program. it worked fine. To figure out how everything works, i copied all the files from the tutorial, deleted which I thought was not necessary and tried to compile and deploy the service. but it is not working.
It is not creating any class files.
It says 'RmiModeler error: java.lang.ClassNotFoundException' in run-wscompile. (I think its tied to prev one)
And 'XML reader error: java.io.EOFException' in run-wsdeploy.
can anyone tell me what am I doing wrong.
Thank you.
/*HelloIF.java: */
package HelloWS;
import java.rmi.Remote;
import java.rmi.RemoteException;
public interface HelloIF extends Remote
public String sayHello(String s) throws RemoteException;
/* HelloImpl: */
package HelloWS;
import java.xml.rpc.server.ServiceLifecycle;
public class HelloImpl implements HelloIF, ServiceLifecycle
public String message ="Hello";
public String sayHello(String s)
return message + s;
/*build.properties*/
username=asdf
password=asdf
host=localhost
secure.port=8443
url=http://localhost/manager
example=helloservice
war.path=C:/HelloWS/hello-jaxrpc.war
portable.war=hello-jaxrpc-portable.war
hello.endpoint=http://localhost/hello-jaxrpc/hello
secure.endpoint=http://localhost/secure-jaxrpc/hello
mutualauth.endpoint=https://localhost:8443/secure-mutualauth/hello
client.jar=client.jar
config.wsdl.file=config-wsdl.xml
jwsdp.home=C:/jwsdp
jwsdp.shared=${jwsdp.home}/jwsdp-shared
jaxp.home=${jwsdp.home}/jaxp
jaxrpc.home=${jwsdp.home}/jaxrpc
saaj.home=${jwsdp.home}/saaj
wscompile.dir=${jaxrpc.home}/bin
wsdeploy.dir=${jaxrpc.home}/bin
javamail.jar=${jwsdp.shared}/lib/mail.jar
jaf.jar=${jwsdp.shared}/lib/activation.jar
jaxp-api.jar=${jaxp.home}/lib/jaxp-api.jar
dom.jar=${jaxp.home}/lib/endorsed/dom.jar
sax.jar=${jaxp.home}/lib/endorsed/sax.jar
xalan.jar=${jaxp.home}/lib/endorsed/xalan.jar
xercesImpl.jar=${jaxp.home}/lib/endorsed/xercesImpl.jar
jaxrpc-api.jar=${jaxrpc.home}/lib/jaxrpc-api.jar
jaxrpc-impl.jar=${jaxrpc.home}/lib/jaxrpc-impl.jar
commons-logging.jar=${jwsdp.shared}/lib/commons-logging.jar
saaj-api.jar=${saaj.home}/lib/saaj-api.jar
saaj-impl.jar=${saaj.home}/lib/saaj-impl.jar
relaxngDatatype.jar=${jwsdp.shared}/lib/relaxngDatatype.jar
xsdlib.jar=${jwsdp.shared}/lib/xsdlib.jar
jax-qname.jar=${jwsdp.shared}/lib/jax-qname.jar
ant.jar=${jwsdp.home}/apache-ant/lib/ant.jar
/*build.xml*/
<project name="jaxrpc-tutorial" default="build" basedir=".">
<property file="build.properties"/>
<path id="compile.classpath">
<pathelement location="${javamail.jar}"/>
<pathelement location="${jaf.jar}"/>
<pathelement location="${jaxp-api.jar}"/>
<pathelement location="${dom.jar}"/>
<pathelement location="${sax.jar}"/>
<pathelement location="${xalan.jar}"/>
<pathelement location="${xercesImpl.jar}"/>
<pathelement location="${jaxrpc-api.jar}"/>
<pathelement location="${jaxrpc-impl.jar}"/>
<pathelement location="${commons-logging.jar}"/>
<pathelement location="${saaj-api.jar}"/>
<pathelement location="${saaj-impl.jar}"/>
<pathelement location="${relaxngDatatype.jar}"/>
<pathelement location="${xsdlib.jar}"/>
<pathelement location="${jax-qname.jar}"/>
<pathelement location="${ant.jar}"/>
<pathelement location="build/shared"/>
</path>
<path id="run.classpath">
<path refid="compile.classpath"/>
<pathelement location="dist/client.jar"/>
</path>
<taskdef name="deploy" classname="org.apache.catalina.ant.DeployTask" />
<taskdef name="undeploy" classname="org.apache.catalina.ant.UndeployTask" />
<taskdef name="list" classname="org.apache.catalina.ant.ListTask" />
<taskdef name="start" classname="org.apache.catalina.ant.StartTask" />
<taskdef name="stop" classname="org.apache.catalina.ant.StopTask" />
<taskdef name="install" classname="org.apache.catalina.ant.InstallTask"/>
<taskdef name="reload" classname="org.apache.catalina.ant.ReloadTask"/>
<taskdef name="remove" classname="org.apache.catalina.ant.RemoveTask"/>
<target name="build" depends="build-service"
 description="Executes the targets needed to build the service.">
</target>
<target name="build-service" depends="clean,compile-service,generate-sei-service,
setup-web-inf,package-service,process-war"
description="Executes the targets needed to build the service.">
</target>
<target name="clean"
description="Removes the build directory">
<delete dir="build" />
</target>
<target name="compile-service" depends="prepare"
description="Compiles the server-side source code">
<echo message="Compiling the server-side source code...."/>
<javac srcdir="src" destdir="build/hellows">
<classpath refid="compile.classpath"/>
</javac>
</target>
<target name="prepare"
description="Creates the build directory" >
<echo message="Creating the required directories...." />
<mkdir dir="build/hellows" />
</target>
<target name="generate-sei-service"
description="Runs wscompile to generate the model file">
<antcall target="run-wscompile">
<param name="param1" value="-define -d build -nd build
-classpath build config-interface.xml
-model build/model.gz" />
</antcall>
<delete file="build/MyHelloService.wsdl" />
</target>
<target name="setup-web-inf"
description="Copies files to build/WEB-INF">
<echo message="Setting up build/WEB-INF...." />
<delete dir="build/WEB-INF" />
<copy todir="build/WEB-INF/classes/hellows">
<fileset dir="build/hellows" />
<fileset dir="build/hellows" />
</copy>
<copy file="build/model.gz" todir="build/WEB-INF" />
<copy file="web.xml" todir="build/WEB-INF" />
<copy file="jaxrpc-ri.xml" todir="build/WEB-INF" />
</target>
<target name="package-service" depends="prepare-dist"
description="Packages the WAR file">
<echo message="Packaging the WAR...." />
<delete file="dist/hello-jaxrpc-portable.war" />
<jar jarfile="dist/hello-jaxrpc-portable.war" >
<fileset dir="build" includes="WEB-INF/**" />
</jar>
</target>
<target name="prepare-dist"
description="Creates the dist directory" >
<echo message="Creating the required directories...." />
<mkdir dir="dist" />
</target>
<target name="process-war" depends="set-wsdeploy"
description="Runs wsdeploy to generate the ties and
create a deployable WAR file">
<delete file="dist/hello-jaxrpc.war" />
<antcall target="run-wsdeploy">
<param name="param1" value="-o dist/hello-jaxrpc.war dist/hello-jaxrpc-portable.war" />
</antcall>
</target>
<target name="set-wsdeploy" >
<condition property="wsdeploy" value="${wsdeploy.dir}/wsdeploy.bat">
<os family="windows" />
</condition>
<condition property="wsdeploy" value="${wsdeploy.dir}/wsdeploy">
<not>
<os family="windows" />
</not>
</condition>
</target>
<target name="set-wscompile" >
<condition property="wscompile" value="${wscompile.dir}/wscompile.bat">
<os family="windows"/>
</condition>
<condition property="wscompile" value="${wscompile.dir}/wscompile">
<not>
<os family="windows"/>
</not>
</condition>
</target>
<target name="run-wscompile" depends="prepare,set-wscompile"
description="Runs wscompile">
<echo message="Running wscompile:"/>
<echo message=" ${wscompile} ${param1}"/>
<exec executable="${wscompile}">
<arg line="${param1}"/>
</exec>
</target>
<target name="run-wsdeploy" depends="prepare,set-wsdeploy"
description="Runs wsdeploy">
<echo message="Running wsdeploy:"/>
<echo message=" ${wsdeploy} ${param1}"/>
<exec executable="${wsdeploy}">
<arg line="${param1}"/>
</exec>
</target>
</project>
/*config-interface.xml*/
<?xml version="1.0" encoding="UTF-8"?>
<configuration xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
<service name="MyHelloService"
targetNamespace="urn:Foo"
typeNamespace="urn:Foo"
packageName="hellows">
<interface name="hellows.HelloIF"/>
</service>
</configuration>
/*jaxrpc-ri.xml*/
<?xml version="1.0" encoding="UTF-8"?>
<webServices xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/dd"
 version="1.0"
 targetNamespaceBase="urn:Foo"
 typeNamespaceBase="urn:Foo"
 urlPatternBase="/ws">
<endpoint name="MyHello"
 displayName="HelloWorld Service"
 description="A simple web service"
 interface="HelloWS.HelloIF"
 model="/WEB-INF/model.gz"
 implementation="HelloWS.HelloImpl"/>
<endpointMapping endpointName="MyHello" urlPattern="/hello"/>
</webServices>
/*web.xml*/
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE
 web-app
 PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
 "http://java.sun.com/j2ee/dtds/web-app_2_3.dtd">
<web-app>
<display-name>Hello World Application</display-name>
<description>A web application containing a simple JAX-RPC endpoint</description>
<session-config><session-timeout>60</session-timeout>
</session-config>
</web-app>

I would encourage you to go through the tutorial
setup process again. The only time you should have
this is issues is as a resulty of missing / wrong
env.

Maven plugin for Deploy/undeploy tasks

Hi all,
Have anybody an experience in automating the deployment/undeployment tasks using apache maven 1?
If so, give me some examples and plugins links please!
Thanks in advance.

Thanks. I had seen the link before I post this. The page doesn't really answer my question though and is far from being complete. For instance, it won't tell you anything about plugin's behavior (e.g.: if you configure it in Parent project, would it deploy all modules defined in its POM or not?).
Anyway, I finally found a post somewhere else that helped me to make some real progress.
http://maven.40175.n5.nabble.com/WebLogic-Deployment-ok-from-child-fails-from-parent-td91659.html

Weblogic undeployment

HI ,
When I undeploy my app in weblogic does all classes belonging to my app are garbage collected ?...... the problem i am facing is when i undeploy my app in weblogic some classes are not GC and next time deploy and undeploy the same app the same set of classes are reloaded..
for example lets say i have class com.web.domain.APPConfig
when i undeploy com.web.domain.APPConfig is not GC when i Use reploy the app I see in jrockit mission control toll
classes loaded as
com.web.domain.APPConfig
com.web.domain.APPConfig
ideallly there should only be one class com.web.domain.APPConfig be loaded but it shows 2 and no goes on increasing as i deploy/undeploy

After undeploying an application, delete all the temp files of the application before deploying the next application.
This should help.

Undeployment in NW 7.4 - example

Similar Messages

Maybe you are looking for