Verify (Seeburger) deployment

Hello experts,
Our Seeburger BIC tool generates a SCA and SDA file. The SCA file will be deployed using the JSPM (we have SAP PI 7.11).
Now we see some strange things and want to verify if the deployment was correct.
Where/how can I see the different deployed components? And the version?
Thanks a lot.
Dimitri

Hi,
There I see duplicate mapping ID's. Is that normal?
this is due to the deployment of the same mapping twice...(it can be either standard or custom) but it will not cause any harm...
We deployed a new SCA file, but the changes doesn't seem to have any effect.
Could it be that the system still takes an old version?
Check whether the changes made are working first...
HTH
Rajesh

Similar Messages

VueServlet Deployment success but Verifying VueServlet Deployment

Dear All,
I'm on my way to integrate Autovue with Oracle UCM 11g. The UCM is 11.1.1.0.8 and the autovue is 20.2.2. The autovue is already installed and I follow the instruction to deploying vueServlet. The deployment is successfull but when I try to access the url as on the instruction the page couldn't be found. the error is
 Error 404Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
The document I follow is 'Oracle AutoVue Client/Server Deployment Installation and Configuration Guide Release 20.2.2'. I share the screenshot of the deployment process on https://dl.dropboxusercontent.com/u/68343018/Deploy%20vueservlet%20documentation.docx
Does anybody know why I got this error and how to fix it? Really appreciate for your help
Best Regards
Akhmad H Gumas

Hi Akhmad,
I looked at your screenshot and the steps you did looks good. My guess would be that there is either something wrong with your VueServlet WAR file or else the port you are using "16200" is wrong. It might be best for you to create a new SR and add your VueServlet WAR file to the SR, support will be able to test and confirm if it is ok or not. Also I think it would be good to test your VueServlet using your WebLogic port "7001" instead and see what happens.
Thanks,
Daniel

Verifier error on filters during Glassfish deployment

Trying to deploy a couple of simple filter classes like this:
public class MyFilter implements FilterI get this error for every single filter when deploying the WAR in Glassfish with the verifier option checked:
Error: Servlet Class [com.myPackage.MyFilter] does not directly or indirectly implement javax.servlet.Servlet
If I do not pass through the verifier the deployment is OK and the filters seem to run as expected.
thanks for any suggestion,
giovanni

when your class does implement a Filter interface the container
must recognize it as a servletReally? I never heard nor read this before.
Here is an excerpt of: http://www.servlets.com/soapbox/servlet23.html
Filters are not servlets; they do not actually create a response. They are preprocessors of the request before it reaches a servlet, and/or postprocessors of the response leaving a servlet. In a sense, filters are a mature version of the old "servlet chaining" concept.
Maybe you are used to the pre-servlet 2.3 specs?

Issue in deploying Service Bus projects using maven

Hi,
I am following the following documentation for deploying service bus projects to my OSB server.
http://docs.oracle.com/middleware/1213/core/MAVEN/osb_maven_project.htm#MAVEN8973
I was able to issue mvn package as described in documentation and also able to see sbar files in .data/Maven directory of each project.
But i am seeing following error when i issue mvn pre-integration-test. Am i missing any steps.
[INFO] --- oracle-servicebus-plugin:12.1.3-0-0:deploy (default-deploy) @ System ---
[INFO] Service Bus Archive deployed using session Service_Bus_Maven-System-1424718369010.
java.io.IOException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'w
eblogic.management.mbeanservers'
        at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.ja
va:237)
        at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.j
ava:120)
        at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:369)
        at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:267)
        at oracle.sb.maven.plugin.deploy.MBeanHelper$MBeanInvocationHandler.getJMXConnector(MBeanHel
per.java:228)
        at oracle.sb.maven.plugin.deploy.MBeanHelper$MBeanInvocationHandler.invoke(MBeanHelper.java:
131)
        at com.sun.proxy.$Proxy16.createSession(Unknown Source)
        at oracle.sb.maven.plugin.DeployMojo.createSession(DeployMojo.java:141)
        at oracle.sb.maven.plugin.DeployMojo.execute(DeployMojo.java:89)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.j
ava:101)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBu
ilder.java:84)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBu
ilder.java:59)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter
.java:183)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.management.mbeanservers.d
omainruntime'. Resolved 'weblogic.management.mbeanservers' [Root exception is javax.naming.NameNotFo
undException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic
.management.mbeanservers']; remaining name 'domainruntime'
        at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1180
        at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:270)
        at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:187)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:210)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:224)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:224)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:224)
        at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
        at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:701)
        at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:231)
        at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:527)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
        at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:523)

Hi Siva,
I am facing same issue I am bale to create package but while deployment goal I am facing problem.I am following same document as you do.
I can see my mvn-pre-integration ..show me sucees in result
[DEBUG]   Excluded: org.apache.maven:maven-artifact:jar:3.0.3
[DEBUG] Configuring mojo com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:package from plugin realm ClassRealm[plugin>com.oracle.servicebus.plugin:oracl
-servicebus-plugin:12.1.3-0-0, parent: sun.misc.Launcher$AppClassLoader@65450f1f]
[DEBUG] Configuring mojo 'com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:package' with basic configurator -->
[DEBUG]   (f) oracleHome = C:\Oracle\Middleware\Oracle_Home
[DEBUG]   (f) project = MavenProject: LinuxMachine:TestOSBLinux:1.0-SNAPSHOT @ C:\JDeveloper\mywork\OSB-DEPLOY\LinuxMachine\TestOSBLinux\pom.xml
[DEBUG]   (f) system = false
[DEBUG] -- end configuration --
[INFO]
[INFO] --- oracle-servicebus-plugin:12.1.3-0-0:deploy (default-deploy) @ TestOSBLinux ---
[DEBUG] Configuring mojo com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:deploy from plugin realm ClassRealm[plugin>com.oracle.servicebus.plugin:oracle
servicebus-plugin:12.1.3-0-0, parent: sun.misc.Launcher$AppClassLoader@65450f1f]
[DEBUG] Configuring mojo 'com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:deploy' with basic configurator -->
[DEBUG]   (f) oraclePassword = Oracle123
[DEBUG]   (f) oracleServerUrl = http://192.168.137.150:7001
[DEBUG]   (f) oracleUsername = weblogic
[DEBUG]   (f) project = MavenProject: LinuxMachine:TestOSBLinux:1.0-SNAPSHOT @ C:\JDeveloper\mywork\OSB-DEPLOY\LinuxMachine\TestOSBLinux\pom.xml
[DEBUG] -- end configuration --
[INFO] Service Bus Archive deployed using session Service_Bus_Maven-TestOSBLinux-1429888616161.
[INFO]
[INFO] --- oracle-servicebus-plugin:12.1.3-0-0:deploy (deploy) @ TestOSBLinux ---
[DEBUG] Configuring mojo com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:deploy from plugin realm ClassRealm[plugin>com.oracle.servicebus.plugin:oracle
servicebus-plugin:12.1.3-0-0, parent: sun.misc.Launcher$AppClassLoader@65450f1f]
[DEBUG] Configuring mojo 'com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:deploy' with basic configurator -->
[DEBUG]   (f) oraclePassword = Oracle123
[DEBUG]   (f) oracleServerUrl = http://192.168.137.150:7001
[DEBUG]   (f) oracleUsername = weblogic
[DEBUG]   (f) project = MavenProject: LinuxMachine:TestOSBLinux:1.0-SNAPSHOT @ C:\JDeveloper\mywork\OSB-DEPLOY\LinuxMachine\TestOSBLinux\pom.xml
[DEBUG] -- end configuration --
[INFO] Service Bus Archive deployed using session Service_Bus_Maven-TestOSBLinux-1429888623126.
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building LinuxMachine 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-so
rces, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, i
tegration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy]
[DEBUG] === PROJECT BUILD PLAN ================================================
[DEBUG] Project:       LinuxMachine:LinuxMachine:1.0-SNAPSHOT
[DEBUG] Dependencies (collect): []
[DEBUG] Dependencies (resolve): []
[DEBUG] Repositories (dependencies): [central (https://repo.maven.apache.org/maven2, default, releases)]
[DEBUG] Repositories (plugins)     : [central (https://repo.maven.apache.org/maven2, default, releases)]
[DEBUG] =======================================================================
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] TestOSBLinux ....................................... SUCCESS [ 20.752 s]
[INFO] LinuxMachine ....................................... SUCCESS [ 0.009 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
But not get deployed .....
When i run mvn com.oracle.servicebus.plugin:oracle-servicebus-plugin:deploy** to invoke deployment goal it fails which below logs
org.apache.maven.plugin.MojoNotFoundException: Could not find goal 'deploy*.*' in plugin com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0 amon
goals deploy, package
        at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:275)
        at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:239)
        at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor(MojoDescriptorCreator.java:233)
        at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:103)
        at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:83)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:85)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[ERROR]
[ERROR]
Thanks&Regards
Prabhat

Weblogic deployment plan will not override variables (Weblogic 10.3.5).

I am having some trouble trying to adjust the deployment settings of our application in weblogic. I feel what I'm trying to do ought to be quite simple, but it's not working as expected.
I am just trying to override the context-root in weblogic.xml and the JNDI name for the data source, so these can both be configured at deployment time.
I have removed the application.xml from the ear file, so that shouldn't be affecting the overrides.
What I have so far:
weblogic.xml:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-web-app xmlns="http://xmlns.oracle.com/weblogic/weblogic-web-app" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.2/weblogic-web-app.xsd">
<context-root>mosaic</context-root>
<resource-description>
<res-ref-name>jdbc/LogicalDS</res-ref-name>
<jndi-name>LogicalDS</jndi-name>
</resource-description>
web.xml
<?xml version='1.0' encoding='UTF-8'?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<resource-ref>
<description>A logical reference to the datasource - mapped in deployment plan</description>
<res-ref-name>jdbc/LogicalDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
plan.xml
<?xml version="1.0" encoding="UTF-8"?>
<wls:deployment-plan xmlns:wls="http://xmlns.oracle.com/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/j2ee_1_4.xsd" global-variables="true">

<wls:application-name>mosaic.ear</wls:application-name>
<wls:variable-definition>
<wls:variable>
<wls:name>datasource_name</wls:name>
<wls:value xsi:nil="true"></wls:value>
<wls:description>The name of the datasource to map to the mosaic application</wls:description>
</wls:variable>
<wls:variable>
<wls:name>new_context_root</wls:name>
<wls:value xsi:nil="true"></wls:value>
<wls:description>URL to deploy Mosaic at</wls:description>
</wls:variable>
</wls:variable-definition>
<wls:module-override>
<wls:module-name>mosaic.war</wls:module-name>
<wls:module-type>war</wls:module-type>
<wls:module-descriptor>
<wls:root-element>weblogic-web-app</wls:root-element>
<wls:uri>WEB-INF/weblogic.xml</wls:uri>
<wls:variable-assignment>
<wls:name>new_context_root</wls:name>
<wls:xpath>/weblogic-web-app/context-root</wls:xpath>
<wls:operation>replace</wls:operation>
</wls:variable-assignment>
<wls:variable-assignment>
<wls:description>Data source for mosaic application</wls:description>
<wls:name>datasource_name</wls:name>
<wls:xpath>/weblogic-web-app/resource-env-description/resource-env-ref-name</wls:xpath>
<wls:operation>replace</wls:operation>
</wls:variable-assignment>
<wls:variable-assignment>
<wls:name>datasource_name</wls:name>
<wls:xpath>/weblogic-web-app/resource-description/[res-ref-name="jdbc/LogicalDS"]/jndi-name</wls:xpath>
<wls:operation>replace</wls:operation>
</wls:variable-assignment>
</wls:module-descriptor>
</wls:module-override>
</wls:deployment-plan>
Nothing happens when I use the deployment plan, and neither of the variables appear under the Deployment Plan configuration screens in the admin console. From what I understand, I should at least be asked for these variables, since I have specified that they are null in the deployment plan.
When I use WLST to browse the tree, I find that the runtime configuration just stays as the values in the deployment descriptors.
I have verified the deployment plan is being used in the general tab of the admin console.
Can anyone help me find out what I am doing wrong here? If I don't create a data source called LogicalDS, I get errors about this, suggesting it is not correctly overriding. I am puzzled to why I do not see any variables to specify though..

The documentation implies that this is not the case - see:
http://docs.oracle.com/cd/E24329_01/web.1211/e24443/export.htm#autoId13
'Assigning Null Variables to Require Administrator Input'.
However, require administrator input where? My thoughts were that this option would appear in the admin console under 'deployment plan'. However, although I have specified resource dependencies in the deployment descriptors, and the plan, nothing appears under 'resource dependencies' for the application.
Is the only way to change the context-root deployment URL by actually manually editing an XML file?
To me that seems primitive and will cause us support issues when distributing our application - is there any other way I can enable the ability to specify the data source name and context-root through the web console prior to/during deployment?
Edited by: user12032953 on 11-Jun-2012 07:20

SCCM 2012 OSD; Not finding driver package during deployment

I've been having some trouble setting up my OSD deployment using SCCM 2012 and hope someone can point me in the right direction. Specifically I am having trouble with device driver deployment while deploying my reference image.
I am running SCCM Config Manager 2012 SP1 CU2. This is running on a Server 2012 VM with SQL 2012.  I am building an OSD deployment and have successfully captured my reference image. I am not sure if it matters, but I manually built a reference
PC and using capture media (USB stick), I successfully captured my reference image. I have imported my drivers for the target PC into Config Manager and into a driver package. The driver package has been deployed to the distribution point
(DP).  I checked the status of the driver package within the console and verified it has been deployed to the DP.   I created a new task sequence (TS) to deploy the captured wim. Within the TS, I added an "Apply
Driver Package" step and pointed it to the aforementioned driver package. I added a WMI query to the step as follows
select * from Win32_ComputerSystem where Model like "HP Probook 6570b%."
Incidentally, I did a wmi query on the target PC to verify the model. I deployed the TS to the unknown computers collection and PXE booted the target PC. I ran through the OSD wizard and while OSD is verifying the deployment prerequisites,
the deployment fails with the error, "The task sequence cannot be run because a package referenced by the task sequence could not be found." I checked the smsts.log log and found the following:
Failed to find CCM_SoftwareDistribution object for AdvertID="CT120043", PackageID="CT100044", ProgramID="*"
After some research I found this error means Config Manager cannot find the driver package (PackageID="CT100044")
for deployment. After more research I have done the following:
Deleted the Driver Package and recreated it and updated the TS step to point to this package.
Deleted and recreated the TS along with the driver package.
Recreated the driver package and distributed content, only importing the NIC drivers as a way to make a simple test.
When distributing content I verified it was successfully completed each time as per the console.
Each time I recreated the driver package and the OSD failed, smsts.log is showing the appropriate package ID in the error. If I disable the Apply Driver Package step and configure a Apply Device Drivers step to install the best matched compatible drivers
and limit the driver matching to the specific driver package, the OSD completes but the drivers do not install. It is as if Config Manager is not seeing the imported drivers at all.
I have run out of options to try and hope someone can help point me in the next direction to take.  After reading numerous forums and guides, I am sure I am doing the OSD steps correctly but I am apparently missing something.
Thanks in advance,
Mike G.

Thanks for responding.
Yes after I posted the question I right-clicked on the driver package, and selected to update distribution points. I checked now (about 12 hours later) and the package is showing it has not finished updating. I checked the content status and
it is "waiting for content." I looked at distmgr.log and I found an error "Failed to start DP health monitoring task for package 'CT100044'. Error code: -1". This error would occur every 30 min after each time the DP retried to process
the package. After some research I found a post stating a file called "Microsoft" or "Program" on located on the root of the site server could cause this and renaming or deleting the file would resolve this. I renamed the file and after the next time
it retried, the error cleared, however the package status is still waiting for content. I tried doing a validation on the package but so far there has been no change.

WLW deployment of WebApp fails, where manual deployment succeeds

Hi,
I have installed WL Platform 8.1 SP4 on W/XP Professional.
I am attempting to do the most introductory task... i.e. deploy a web application consisting of two pages using WLW. The files are:
<pre>SimpleForm.html</pre>
<pre>SimpleFormHandler.jsp</pre>
I wanted to access the web app as follows:
http://localhost:7001/TestProj/SimpleForm.html
The <pre>SimpleFormHandler.jsp</pre> is registered as the form's action method. When the form is submitted, the JSP simply displays the form data.
It works as expected when I build the WAR file manually and deploy it by copying the file to the 'application' directory for autodeployment.
But I am baffled how to do this using WLW. Which is really the purpose of my experiment.
Hopefully, you can guide me here. I have listed the steps I've taken so maybe you can identify my misstep and set me back on the right path.
To keep things real simple, here is my Domain configuration, HTML form and JSP file.
<pre>-- TestDomain: Basic WebLogic Server Domain Template -----------
Custom: The only thing I customise is the Name = "adminserver".
I select JRockit and Development Mode.
Configuration Name: TestDomain
----------------------------------------------------------------</pre>
<pre>-- SimpleForm.html -----------------------------------------------
<html>
<head>
</head>
<body>
<h1>This is a test html file</h1>
<form action="SimpleFormHandler.jsp" method="get">
Enter first name: <input type="text" name="firstName">
<input type="submit">
</form>
</body>
</html>
-------------------------------------------------------------------</pre>
<pre>-- SimpleFormHandler.jsp ------------------------------------------
<%@ page language="java" contentType="text/html;charset=UTF-8"%>
<html>
<head>
<title>
Web Application Page
</title>
</head>
<body>

New Web Application Page
<% String firstName=request.getParameter("firstName");
out.println("Your first name is: " + firstName); %>

</body>
</html>
--------------------------------------------------------------------</pre>
Here is the steps I followed.
01) WLW Menu: File->New->Application...
-> Empty Application (I also tried "Default Application")
-> Directory: <devel_path> \TestApp
-> Server: <domain_path> \TestDomain
-> >>Create<<
02) WLW Menu: File->New->Project...
-> Web Project
-> Project name : TestProj
-> >>Create<<
03) WLW Menu: File->New->JSP File
-> JSP File
-> File name: SimpleFormHandler.jsp
-> >>Create<<
Edit the file to look like the file above.
04) WLW Menu: File->New->JSP File
-> HTML File
-> File name: SimpleForm.html
-> >>Create<<
Edit the file to look like the file above.
05) WLW Menu: File->Save
06) WLW Menu: Tools->Weblogic Server->Server Properties...
-> Hostname: localhost
-> Use credentials below:
Username: system
Password: weblogic
All other fields are correct.
This immediately results in a deployment error.
<pre>"ClassNotFoundException: weblogic.servlet.WlwJSPServlet"</pre>
This is the result of a bogus entry in weblogic.xml.
Edit <pre>weblogic.xml</pre> to comment out the WlwJSPServlet, so it becomes:
<pre> </pre>
07) WLW Menu: File->Save
F7 (to rebuild and redeploy)
More deployment errors, since web.xml also defines Listeners, Filters, and ....
08) WL Builder: Open TestApp
Servlets: Delete 'action'
Filters: Delete 'PageFlowJspFilter'
Listeners: Delete '...WebappContextListener'
Tag Libraries: Delete netui-tags-[html,databinding,template].tld
File->Save
09) WLW Menu: F7 (to rebuild and redeploy)
This time I get a new warning:
<pre><The current version 0 for DataIdentifier DataIdentifierID: 1 does not match with incoming version 4 for a one-phase update.></pre>
10) Check the WLS Console <pre>http://localhost:7001/console</pre>
Deployments -> General
 TestApp EXPLODED EAR
Deployments -> Descriptors -> application.xml
<pre> <application>
<display-name>TestApp</display-name>
<module>
<web>
<web-uri>TestProj</web-uri>
<context-root>TestProj</context-root>
</web>
</module>
</application></pre>
11) Now try to access the web application:
http://localhost:7001/TestProj/SimpleForm.html
 -> Enter first name: Artimus
 -> >> SUBMIT QUERY <<
This causes the following page to attempt to open:
http://localhost:7001/TestProj/SimpleFormHandler.jsp?firstName=Artimus
Back on the WLS console the following error:
<pre>NoClassDefFoundError: com/bea/wlw/runtime/core/debug/DebugContext</pre>
The full details:
<pre>-- ERROR LOG ---
<29/08/2005 08:47:11 PM EST> <Error> <HTTP> <BEA-101017> <[ServletContext(id=548
7457,name=TestProj,context-path=/TestProj)] Root cause of ServletException.
java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/debug/DebugContext
-----------------------------------------------------------------------</pre>
12) WLW Menu: Tools->Weblogic Server->Deployment->Undeploy
Verified no apps deployed via http://localhost:7001/console
13) Now test a manual deployment:
cd {TestProj}\
jar -cf TestProj.war *
copy TestProj.war (domain}\applications
14) Verified TestProj deployed as Web Application via
 http://localhost:7001/console
15) Access the web application from browser with:
http://localhost:7001/TestProj/SimpleForm.html
 -> Enter first name: Bach
 -> >> SUBMIT QUERY <<
16) This opens the following page:
http://localhost:7001/TestProj/SimpleFormHandler.jsp?firstName=Bach
17) The JSP displays the following in the browser window:
"New Web Application Page Your first name is: Bach "
So manual deployment succeeded!
--- end ---
I would really appreciate some suggestions.
Regards,
Matt.

Thanks for the response.
I find that if I don't perform step 8, (i.e. remove the action, filter, servlets, and pageflows), then the deployment fails, since it is expecting to find modules that perform these functions.
I am a little surprised that the Default Application, doesn't also provide default entries for these functions.
For instance, I naively (and wrongly) anticipated that if I create a Default Application and make no changes, then I should be able to immediately deploy it. Unfortunately, this is not possible, since it complains about the entries in web.xml and weblogic.xml.
Perhaps the minimum WebApp deployment requires that I provide the modules in the default descriptors?
I am beginning to wonder what the absolute minimum application is that WLW can be used to deploy.
Regards,
Matt.

J2EE 1.4 Tutorial - problems with deploying web services

Hi folks,
I have a problem with the deployment of the example "MyHelloService" (chapter 8: Building Web Services With JAX-RPC).
I've installed the application server properly and executed all the necessary steps written down in the tutorial (Packaging the Service and Specifying the Endpoint Address).
While deploying the service I get the following error message:
Deploy action running...
com.sun.enterprise.admin.common.exception.DeploymentException: com.sun.enterprise.config.ConfigException: Failed to load deployment descriptor for: MyHelloService
cause: Premature end of file.
     at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.deployWarModuleArchiveOrDirectory(ManagedServerInstance.java:1099)
     at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.deployWarModule(ManagedServerInstance.java:1003)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.enterprise.admin.server.core.jmx.Introspector.invokeMethodOn(Introspector.java:181)
     at com.sun.enterprise.admin.server.core.mbean.config.AdminBase.invoke(AdminBase.java:86)
     at com.sun.enterprise.admin.server.core.mbean.config.ConfigMBeanBase.invoke(ConfigMBeanBase.java:663)
     at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:212)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:218)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:808)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:781)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:223)
     at com.sun.enterprise.admin.server.core.servlet.AdminAPIEntryServlet.callInvoke(AdminAPIEntryServlet.java:203)
     at com.sun.enterprise.admin.server.core.servlet.AdminAPIEntryServlet.callMBean(AdminAPIEntryServlet.java:162)
     at com.sun.enterprise.admin.server.core.servlet.AdminAPIEntryServlet.doGet(AdminAPIEntryServlet.java:103)
     at com.sun.enterprise.admin.server.core.servlet.AdminAPIEntryServlet.doPost(AdminAPIEntryServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at sun.reflect.GeneratedMethodAccessor137.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:202)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:499)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:212)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:149)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:282)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:99)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:189)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:185)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:561)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1018)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:206)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:558)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:561)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1018)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2748)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:186)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:512)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
     at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
     at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:383)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:561)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1018)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:163)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:561)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1018)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:199)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:630)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:463)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:568)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:631)
     at java.lang.Thread.run(Thread.java:536)
!!! Operation Failed !!!
[Completed (time=4.1sec, status=13)]
I verified the deployment descriptor and unpacked the WAR, but there seems to be no mistake. I don't know what to do...I can't imagine that this is a bug, so maybe I've done something wrong.
Any help would be appreciated.

Thank you for your answer, but I encountered the problem with the defect WAR file already in chapter 3 (Getting Started with Web Applications). I searched the forum and found the thread you recommended, made the adjustments in the deploytool.bat file and so fixed the problem.
Thus your recommendation is unfortunately not the right solution for my problem.
For verification purposes, here is an extract from my deploytool.bat file:
set _USER_COUNTRY=US
set _USER_LANG=en
set _USER_REGION=US
set _MAIN=com.sun.enterprise.tools.deployment.ui.Main
set _CPATH=%LIB%\appserv-assemblytool.jar;%AS_IMQ_LIB%\activation.jar; %AS_JHELP%\jhall.jar;%LIB%\appserv-admin.jar;%LIB%\appserv-cmp.jar; %LIB%\appserv-rt.jar;%LIB%\j2ee.jar; %AS_INSTALL%\share\lib\jaxrpc-impl.jar;%LIB%\appserv-ext.jar; %LIB%\deployhelp.jar
echo %_JAVACMD% -Dcom.sun.aas.installRoot="%AS_INSTALL%" -Djava.endorsed.dirs=%AS_INSTALL%\share\lib\endorsed -Dcom.sun.aas.defaultUserName="%AS_ADMIN_USER%" -Dcom.sun.aas.defaultPassword="%AS_ADMIN_PASSWORD%" -Duser.country="%_USER_COUNTRY%" -Duser.language="%_USER_LANG%" -Duser.region="%_USER_REGION%" -cp %_CPATH% %_MAIN% %1 %2
%_JAVACMD% -Dcom.sun.aas.installRoot="%AS_INSTALL%" -Djava.endorsed.dirs=%AS_INSTALL%\share\lib\endorsed -Dcom.sun.aas.defaultUserName="%AS_ADMIN_USER%" -Dcom.sun.aas.defaultPassword="%AS_ADMIN_PASSWORD%" -Duser.country="%_USER_COUNTRY%" -Duser.language="%_USER_LANG%" -Duser.region="%_USER_REGION%" -cp %_CPATH% %_MAIN% %1 %2In addition, I used the verification option from the deploytool and checked the deployment descriptor with the following results (only passed tests):
Test Name : tests.web.ServletLargeIcon
There are no large-icon elements within the servlet [ helloservice.HelloImpl ].
Test Name : tests.web.ServletClass
Servlet class [ helloservice.HelloImpl ] resides in the WEB-INF/classes directory.
Test Name : tests.web.SessionTimeout
Servlet session-timeout [ 30 ] element defines the default session timeout interval expressed in whole minutes.
Test Name : tests.web.ServletInterface
Not Applicable since, Servlet [ helloservice.HelloImpl ] is a JAXRPC Endpoint.
Test Name : tests.web.ParamValue
Test Name : tests.web.ServletSmallIcon
There are no small-icon elements in the servlet [ helloservice.HelloImpl ].
Test Name : tests.web.WebName
Web-App display name is : [ MyHelloService.war ]
Test Name : tests.web.ServletParamName
ServletParam name exists in the web application.
Test Name : tests.web.ResourceAuth
Test Name : tests.web.ServletParamValue
Test Name : tests.web.JarContainsXMLFile
Found deployment descriptor xml file [ WEB-INF/web.xml ]All the other tests were notapplicable (no errors).
Moreover, I unpacked the WAR file (MyHelloService.war): all necessary XML files were included and well-formed.

Web Services After Deployment...???

This may be a dumb question since I am new and evaluating BEA WebLogic products.
I follow the tutorials (Web Services, to be specific) all the way to build EAR
file and deploy it.
Now, WHAT DO I DO ???
Suppose my server is TestServer, my BEA Web Services is TestWebServices,
What URL should I navigate to verify the deployment is success ?
Here the the contents of my WebLogic Console Deployments:
Configurations:
Name: TestWebServices
Path: E:\Bea\TestWebServices
Deployment Protocol: Two-Phase
Staging Mode: nostage
Targets:
Independent Servers: TestServer
Deploys:
Module:TestWebServicesWeb Status:Active Target:testServer Type:Server LastAction:Success
Can I have a specific url example to try ?
Thanks.

I'd suggest you start with the tutorials on this site:
http://dev2dev.bea.com/index.jsp
-- Rob
Tom Nagel wrote:
This may be a dumb question since I am new and evaluating BEA WebLogic products.
I follow the tutorials (Web Services, to be specific) all the way to build EAR
file and deploy it.
Now, WHAT DO I DO ???
Suppose my server is TestServer, my BEA Web Services is TestWebServices,
What URL should I navigate to verify the deployment is success ?
Here the the contents of my WebLogic Console Deployments:
Configurations:
Name: TestWebServices
Path: E:\Bea\TestWebServices
Deployment Protocol: Two-Phase
Staging Mode: nostage
Targets:
Independent Servers: TestServer
Deploys:
Module:TestWebServicesWeb Status:Active Target:testServer Type:Server LastAction:Success
Can I have a specific url example to try ?
Thanks.

Deployment verification process

Hello Experts
Do we have a process to verify that Deployment of OBIEE11g from DEv - Test - Prod is done successfully . especially the security part. If one application role was missed in WLS, how do I know that? We need a verification process to verify the environment is expected after finish the deployment.
Edited by: 894860 on Jan 7, 2013 11:30 PM

Hi User,
There is no traditional verification process..
You can have a checklist for the movement of the Dev-Test-Prod.
make sure that all the checklist is moved.
Then you can have a testing cheklist (for Security testing as well) to be followed in dev,test and Prod.
same has to be checked in production env as well.
Basically more of documantation required than the technical work.
after all production enviroment will also have some issue my frend....Nothing is gona be perfect at first shot.
Mark if helpful/Correct
fiaz

Problem deployment EJB

Hi,
When I try to deploy EJB.jar, I have an error :
java.lang.InstantiationException: Error initializing ejb-module; Exception Error in application ejbGestionBase: Error loading package at file:/C:/jdev904/j2ee/home/applications/ejbGestionBase/ejbGestionBase.jar,
Error compiling C:\jdev904\j2ee\home\applications\ejbGestionBase\ejbGestionBase.jar: Syntax error in source
     at com.evermind.server.ejb.EJBContainer.throwInstantiationException(EJBContainer.java:2428)
     at com.evermind.server.ejb.EJBContainer.postInitBatch(EJBContainer.java:2412)
     at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:2195)
     at com.evermind.server.Application.postInit(Application.java:553)
     at com.evermind.server.Application.setConfig(Application.java:170)
     at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1927)
     at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:407)
     at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:127)
     at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:73)
     at com.evermind.server.administration.DefaultApplicationServerAdministrator.internalDeploy(DefaultApplicationServerAdministrator.java:378)
     at com.evermind.server.administration.DefaultApplicationServerAdministrator.deploy(DefaultApplicationServerAdministrator.java:278)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:124)
     at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:48)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Unknown Source)
Can you help me please?

If you are deploying from JDev, run EJB verifier before deploying.
Select ejb-jar.xml in the navigator, right mouse and choose Verify Enterprise JavaBeans.
raghu
JDev Team

Aproove and deploy to production error

Hi,
when i tried to move for Aproove and deploy to production the following error occured.
Failed to approve the project 'project name' for deployment. Unable to obtain exclusive deployment locks to one or more assets. Assets that are locked by other projects must be unlocked before attempting to deploy this project.
Jk

It means the assets you are trying to deploy are also in another project whose "Verify Production Deployment" is not completed or other projects have checked out before you started this project.
So either finish the final step of those projects or delete assets of that project or deploy that project.
-karthik

Activation Agent in SOA Suite 11g

Hi,
The 10g SOA Suite has the activation agents for the BPEL PM - that can start process instances from the reception of an Email for example.
So far, I have not been able to find something like this in the documentation. I am wondering whether there is or will be a mechanism in the 11g SOA infrastructure to have the reception for example of email messages or IM (Chat) messages be processed potentially leading to new service instances. Or would I need to create a custom 'polling' solution for this.
thanks.
Lucas

Hi,
I have placed my transformations in shared folder inside MDS & pass the transformation file to the Oracle SOA transformation function as oramds:/apps/<transformation file name>, i.e in my case I have put the transformation_example.xsl in /apps/testing folder, so I passed oramds:/apps/testing/transformation_example.xsl. I don't deploy shared transformation with composite but put it in shared location.
Your case should also work, look like to me the path issue, jdev ide by default creates all transformation file inside xsl folder, but in the path does not have xsl folder. Check the MDS repository & verify oramds:/deployed-composites/default/DB_Event_rev1.8/Transformation_2.xsl is right.
HTH
Ashish

Dynamic xslt in soa suite 11g

Hi all,
How can we run xslt dynamically in soa suite 11g . I have a requirement to get the xslt file name from the DB based on the input request ID .
Then apply that xslt dynamically in the input request . Whenever we identified any new input request just create the xslt and just copy in a location update the DB
with that ID . No development effort new XSLT.
IS this is possible in 11g i know this is possible in 10g can anyone let me know how to achieve this in 11g.
Thanks
Phani

Hi,
I have placed my transformations in shared folder inside MDS & pass the transformation file to the Oracle SOA transformation function as oramds:/apps/<transformation file name>, i.e in my case I have put the transformation_example.xsl in /apps/testing folder, so I passed oramds:/apps/testing/transformation_example.xsl. I don't deploy shared transformation with composite but put it in shared location.
Your case should also work, look like to me the path issue, jdev ide by default creates all transformation file inside xsl folder, but in the path does not have xsl folder. Check the MDS repository & verify oramds:/deployed-composites/default/DB_Event_rev1.8/Transformation_2.xsl is right.
HTH
Ashish

Sample ANT-generated project

Anyone know where I can download source for a simple project that uses ANT/XDoclet and is built, verified and deployed to the Sun Java System Application Server Platform Edition 8? Ideally, such a project would house CMP beans and an application client. I've been messing around with this off an on for ages but am constantly stymied by cryptic error messages and a glacial deployment process. For the record, I'll list ANT script that I'm using and the resultant problems. Perhaps someone will immediately recognize a rookie mistake. I'd be just as happy, though, if someone could simply direct me to a functional example that I can copy and tweak. I'd love to focus on actually learning J2EE rather than struggling with configuration issues.
Working
* Java Application Verification Kit for the Enterprise StaticArchiveTest/SourceScan
* Delpoying the application and viewing JSP/HTML pages
* Creating and finding CMP beans from JSP
* Deplying application client via deploytool
Crashing and Burning
* Verifying EAR
Error Name : Exception : java.io.IOException: Verify Error: Module specified in application.xml not found in ear file:
Error Description : java.io.IOException: Verify Error: Module specified in application.xml not found in ear file:
at com.sun.enterprise.tools.verifier.Verifier.updateClasspath(Verifier.java:3023)
* Verifying JAR
Test Name : tests.ejb.runtime.ASEntBeanCmpResource
Test Assertion : Enterprise beans cmp-resource test. cmp-resource element contains the database to be used for storing CMP beans in an ejb-jar
Test Description : For [ C:-eclipse-workspace-test-jars-test_ear-test.jar#test.jar#Building ]
FAILED [AS-EJB cmp-resource] : jndi-name cannot be an empty string
* Deploying an application client via "asadmin deploy"
CLI171 Command deploy failed : Deployment Error -- Error while running ejbc -- F
atal Error from EJB Compiler -- com.hollis.residentiator.interfaces.BuildingMgrS
essionHome
WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.err|_ThreadID=12;|java.lang.ClassNotFoundException
at com.sun.enterprise.loader.EJBClassLoader.findClass(EJBClassLoader.java:505)
* Running an application client with 'appclient'
C:\eclipse\workspace\testclient\jars>appclient -client testClient.jar
#### Error: Unable to load module. File -client does not exist.
Client Container Error:
Failed to load the archive specified
C:\eclipse\workspace\testclient\jars>appclient testClient.jar
Please specify uri for the the client jar using -uri
Usage: appclient <client-archive> [-uri <uri>] [client-arg1 client-arg2 ..]
ANT file
<project name="Test project" default="deploy" basedir=".">
 <property file="build.properties"/>
 <property environment="env"/>
 <path id="xdocletlib">
 <fileset dir="${xdoclet.dir}/lib"><include name="**/*.jar"/></fileset>
 <pathelement location="${env.ANT_HOME}/lib/ant.jar"/>
 <pathelement location="${env.J2EE_HOME}/lib/j2ee.jar"/>
 </path>
 <target name="setup">
 <copy todir="${env.J2EE_HOME}/lib/system">
 
 <fileset dir="${log4j.dir}/dist/lib" includes="*.jar"/>
 </copy>
 </target>
 <target name="xdoclet">
 <mkdir dir="${xdoclet.output}"/>
 
 <delete includeemptydirs="true">
 <fileset dir="${xdoclet.output}" includes="**/*"/>
 </delete>
 <mkdir dir="${xdoclet.output}/java"/>
 <taskdef
 name="ejbdoclet"
 classname="xdoclet.modules.ejb.EjbDocletTask"
 classpathref="xdocletlib"
 />
 <ejbdoclet destDir="${xdoclet.output}/java" excludedTags="@version,@author,@todo">
 <fileset dir="${entity.ejb.src.dir}"><include name="**/*Ejb.java"/></fileset>
 <fileset dir="${session.ejb.src.dir}"><include name="**/*Ejb.java"/></fileset>
 <packageSubstitution packages="ejb" substituteWith="interfaces"/>
 <remoteinterface/>
 <homeinterface/>
 <localinterface/>
 <localhomeinterface/>
 <entitypk/>
 <entitycmp/>
 <session/>
 <utilobject>
 <packageSubstitution packages="ejb" substituteWith="util"/>
 </utilobject>
 <valueobject>
 <packageSubstitution packages="ejb" substituteWith="model"/>
 </valueobject>
 <deploymentdescriptor
 destdir="${xdoclet.output}/META-INF"
 validateXml="true"
 />
 <sunone destdir="${xdoclet.output}/META-INF"/>
 </ejbdoclet>
 </target>
 <target name="compile" depends="xdoclet">
 <mkdir dir="${build.dir}"/>
 <javac destdir="${build.dir}">
 <classpath>
 <fileset dir="${log4j.dir}/dist/lib"><include name="*.jar"/></fileset>
 <pathelement location="${env.J2EE_HOME}/lib/j2ee.jar"/>
 </classpath>
 <src path="${entity.ejb.src.dir}"/>
 <src path="${session.ejb.src.dir}"/>
 <src path="${xdoclet.output}/java"/>
 </javac>
 </target>
 <target name="webdoclet">
 <taskdef
 name="webdoclet"
 classname="xdoclet.modules.web.WebDocletTask"
 classpathref="xdocletlib"
 />
 <webdoclet destdir="${xdoclet.output}/${web.dir}/META-INF" excludedtags="@version,@author">
 <deploymentdescriptor
 schema="http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
 displayname="Test App"
 description="A quick and dirty test"
 >
 <welcomefile file="index.html"/>
 <welcomefile file="index.jsp"/>
 </deploymentdescriptor>
 <fileset dir="${entity.ejb.src.dir}"/>
 <fileset dir="${session.ejb.src.dir}"/>
 </webdoclet>
 </target>
 <target name="build" depends="compile,webdoclet">
 <mkdir dir="${jars.dir}"/>
 <jar destfile="${jars.dir}/test.jar">
 <fileset dir="${build.dir}"/>
 <fileset dir="${xdoclet.output}" includes="META-INF/*ejb-jar.xml"/>
 </jar>
 <war
 basedir="${web.dir}"
 destfile="${jars.dir}/test.war"
 webxml="${xdoclet.output}/${web.dir}/META-INF/web.xml"
 >
 <classes dir="${build.dir}">
 <include name="**/*Local.class"/>
 <include name="**/*LocalHome.class"/>
 </classes>
 </war>
 
 <ear destfile="${jars.dir}/test.ear" appxml="META-INF/application.xml">
 <fileset dir="${jars.dir}" includes="*.jar,*.war"/>
 <fileset dir="${basedir}" includes="META-INF/sun-application.xml"/>
 
 <fileset dir="${basedir}/../testclient/${jars.dir}" includes="*.jar"/>
 </ear>
 </target>
 <target name="test">
 <exec executable="${env.J2EE_HOME}\bin\verifier.bat">
 <arg value="${jars.dir}/test.ear"/>
 </exec>
 <property
 name="cpath"
 value="${avk.home}/appserver/lib/sun-appserv-ant.jar:${avk.home}/lib/javke-ant.jar"
 />
 <taskdef
 name="ArchiveTest"
 classname="org.apache.tools.ant.taskdefs.optional.sun.verification.StaticArchiveTest"
 classpath="${cpath}"
 />
 <ArchiveTest appName="${jars.dir}/test_ear/test.jar"/>
 <taskdef name="SourceScan"
 classname="org.apache.tools.ant.taskdefs.optional.sun.verification.SourceScan"
 classpath="${cpath}"
 />
 <SourceScan srcDir="${basedir}/entity_ejb_src" srcServer="sunone"/>
 <SourceScan srcDir="${basedir}/session_ejb_src" srcServer="sunone"/>
 </target>
 <target name="deploy" depends="build">
 <copy todir="${env.J2EE_HOME}/domains/domain1/autodeploy" file="${jars.dir}/test.ear"/>
 <ant target="start_server"/>
 </target>
 <target name="undeploy" depends="stop_server">
 <delete file="/**/*">
 <fileset dir="${env.J2EE_HOME}/domains/domain1/autodeploy" includes="**/*"/>
 </delete>
 </target>
 <target name="start_server">
 <exec dir="${env.J2EE_HOME}\bin" executable="${env.J2EE_HOME}\bin\asadmin.bat">
 <arg value="start-domain"/>
 <arg value="domain1"/>
 </exec>
 </target>
 <target name="stop_server">
 <exec dir="${env.J2EE_HOME}\bin" executable="${env.J2EE_HOME}\bin\asadmin.bat">
 <arg value="stop-domain"/>
 <arg value="domain1"/>
 </exec>
 </target>
</project>

There are quite a few sample apps and blueprint apps that Sun provides. Have you looked at any ofThanks for the response. I looked over the Sun examples and can get them to work. I'm just not interested in manually writing so much code. Every bean seems to require a zillion files and configuration settings. XDoclet was supposed to help me avoid all the typing. I'd also like to steer clear of the deploytool; being able to do a complete build in one step is very important to me. I suppose I could compare and contrast with the functional examples but it's such slow going...

Verify (Seeburger) deployment

Similar Messages

Maybe you are looking for