Deployment of ESS applicaitons in the cluster
Hi,
We have deployed ESS Applications through NWDI. Ideally it should be available in all the Servers under the clusters, but it is available in only two Server nodes under the cluster. It is not deployed in other servers. In the SLD we have specified the Cluster Name.
Any idea as to why it is not deployed in all the servers?
Any kind of help would be greatly appreciated.
Regards,
Adren
Hi,
Touchbase with Basis Team and try to find out whether replication is done on all the systems in cluster or not.
And is this the first time you tried to deploy the application?
and as Thulasi Mentioned restarting the Server would solve.
Hope this helps.
Cheers-
Pramod
Similar Messages
-
I am trying to deploy a MDBean in my cluster ( two servers). The MDBean requires
the destinestion has to each cluster server. It means that I have to deploy my
JMS server over the cluster. This will result multiple destinations (queue or
topic) are created.
Is there a way to run one JMS server with a clustered MDBean?
Thanks,
Taohe
Check out my posting from 4-3 in this thread.
http://forums.ni.com/ni/board/message?board.id=BreakPoint&message.id=5&jump=true
I think I may have answered your question before you asked it.
In that example I use the picture control to manipulate a bunch of rectangular images of booleans.
I hope this helps,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction -
Best Practice when deploying a single mdb into a cluster
At a high level, we are converting all of our components to Weblogic processes that use Stateless Session Beans and Message Driven Beans. All of the weblogic processes will be clustered, and all of the topic queues will be distributed (Uniform Distributed Topics / Queues).
We have one component that is a single MDB reading from a single queue on 1 machine. It is a requirement that the JMS messages on that queue be processed in order, and the processing of messages frequently requires that the same row in the DB be updated. Does anyone have any thoughts on the best design for that in our clustered environment?
One possible solution we have come up with (not working):
Possible Solution 1: Use a distributed topic and enforce a single client via client-id on the connection factory, causing a single consumer.
1.Deploy a uniform-distributed Topic to the cluster.
2.Create a connection factory with a client-id.
3.Deploy a single FooMDB to the cluster.
Problem with Solution 1: WL allows multiple consumers on Topic with same client-id
1.Start (2) servers in cluster
2.FooMDB running on Server_A connects to Topic
3.FooMDB running on Server_B fails with unique id exception (yeah).
4.Send messages - Messages are processed only once by FooMDB on Server_A (yeah).
5.Stop Server_A.
6.FooMDB running on Server_B connects automatically to Topic.
7.Send messages - Messages are processed by FooMDB on Server_B (yeah).
8.Start Server_A
9.FooMDB successfully connects to Topic, even though FooMDB on Server_B is already connected (bad). Is this a WL bug or our config bug??
10.Send messages - Messages are processed by both FooMDB on Server_A and Server_B (bad). Is this a WL bug or our config bug??
Conclusion: Does anyone have any thoughts on the best design for that in our clustered environment? and if the above solution is doable, what mistake might we have made?
Thank you in advance for your help!
kbThanks for the helpful info Tom.
Kevin - It seems that for both the MDB, and the JMS provider, there are (manual or scripted) actions to be taken during any failure event + failure probes possibly required to launch these actions...?
In the case of the JMS provider, the JMS destination needs to be migrated in the event of managed-server or host failure; if this host is the one that also runs the Admin server then the Admin server also needs to be restarted on a new host too, in order that it can become available to receive the migration instructions and thus update the config of the managed server which is to be newly targetted to serve the JMS destination.
In the case of the MDB, a deployment action of some sort would need to take place on another managed-server, in the event of a failure of the managed server or the host, where the original MDB had been initally deployed.
The JMS Destination migration actions can be totally avoided by the use of another JMS implementation which has a design philosophy of "failover" built into it (for example, Tibco EMS has totally automatic JMS failover features) and could be accessed gracefully by using Weblogic foreign JMS. The sinlge MDB deployed on one of the Weblogic managed servers in the cluster would still need some kind of (possibly scripted) redeployment action, and on top of this, there would need to be some kind of health check process to establish if this re-deployment action was actually required to be launched. It is possible that the logic and actions required just to establish the true functional health of this MDB could themsevles be as difficult as the original design requirement :-)
All of this suggests that for the given requirement; the BEA environment is not well suited; and if no other environment or JMS provider is available at your site, then a manipulation of process itself may be required to enable it to be handled in a highly-available way which can be gracefully administered in a Weblogic cluster.
We have not discussed the message payload design and the reasons that message order must be respected - by changing the message payload design and possibly adding additional data, this requirement "can", "in certain circumstances", be avoided.
If you can't do that, I suggest you buy a 2 node Sun Cluster with shared HA storage and use this to monitor a simple JMS client java program that periodically checks for items on the Queue. The Tibco EMS servers could also be configured on this platform and give totally automatic failover protection for both process and host failure scenarios. With the spare money we can go to the pub.
P.S. I don't work for Tibco or Sun and am a BIG Weblogic fan :-) -
Deployment SDM could not start the J2EE Cluster on the host nw4host
Hello,
I installed the WAS testdrive on Linux SUSE 9.3 and the SNDS on WinXP.
I am trying to deploy the welcome application from the SNDS and get the following error message:
SDM could not start the J2ee Cluster on the host nw4host! The online deployment is terminated. JStartup Framework ist not able to deliver an information about the cluster control instances! Please check the status of the J2EE Engine.
I can start the J2EE Start page on port 50000, the system info shows that dispatcher, server0 and SDM are running. I can start the visual admin with go, the SDM with RemoteGui and the DeployTool.
The comand startsap check nw4host shows, everythings running:
nw4host:nw4adm 54> startsap check nw4host
Checking ADA db Database
ABAP Database is running
Checking ADA db Database
J2EE Database is running
See logfile JdbcCon.log
Checking SAP NW4 Instance SCS01
Instance SCS01 is running
Checking SAP NW4 Instance DVEBMGS00
Instance DVEBMGS00 is running
Logging in to SAP with the Java Gui, the ICM says:
ABAP Server operational = TRUE
J2EE Server configured = FALSE
J2EE HTTP port = 50000
J2EE HTTPS port = 50001
J2EE Server operational = TRUE
Default root access handler = ABAP
URL Prefix Table loaded = TRUE
Any idea where the problem could be ?
Thanks, Manfred.changed the ip address for nw4host in etc/hosts to the real ip address of the server where application runs
-
Error in deployment of ESS package
Hi,
We are importing the business package for ESS.
During the import of PCUI_GP16.sca; ESS16.sca components(version
selected based on the SAP note 761266) through SDM we are getting the
error,due to which deployment fails. Error log file is pasted below.
Infrasture details are as below:
Backend: SAP E.C.C. 5.0 SP16 640 kernel based
Portal : EP7.0 700 kernel based
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[/usr/sap/BMD/DVEBMGS01/SDM/program/log/sdmlog20071017.log]/>
<!PATTERN[sdmlog20071017.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Oct 17, 2007 3:35:10 PM Info:
Oct 17, 2007 3:35:10 PM Info: ===============================================
Oct 17, 2007 3:35:10 PM Info: = Starting to execute command 'remotegui' =
Oct 17, 2007 3:35:10 PM Info: ===============================================
Oct 17, 2007 3:35:18 PM Info: SDM started successfully.
Oct 17, 2007 3:38:46 PM Info:
Oct 17, 2007 3:38:46 PM Info: ============================================
Oct 17, 2007 3:38:46 PM Info: = Starting to execute command 'server' =
Oct 17, 2007 3:38:46 PM Info: ============================================
Oct 17, 2007 3:38:46 PM Info: Starting SDM - Software Deployment Manager...
Oct 17, 2007 3:38:47 PM Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0012.20070328121310.0000
Oct 17, 2007 3:38:52 PM Info: SDM operation mode successfully set to: Integrated
Oct 17, 2007 3:38:53 PM Info: JStartupFramework is active
Oct 17, 2007 3:38:53 PM Info: Operation mode of SDM in JStartupFramework is "Integrated".
Oct 17, 2007 3:38:53 PM Info: Check if Server is running already.
Oct 17, 2007 3:38:53 PM Info: OK server is not running. Enable SDM Process in JStartupFramework.
Oct 17, 2007 3:38:53 PM Info: enabling SDM Process with JStartupFramework
Oct 17, 2007 3:38:53 PM Info: enabled SDM Process with JStartupFramework
Oct 17, 2007 3:38:53 PM Info: Successfully enabled SDM Process in JStartupFramework.
Oct 17, 2007 3:38:57 PM Info:
Oct 17, 2007 3:38:57 PM Info: ============================================
Oct 17, 2007 3:38:57 PM Info: = Starting to execute command 'server' =
Oct 17, 2007 3:38:57 PM Info: ============================================
Oct 17, 2007 3:38:57 PM Info: Starting SDM - Software Deployment Manager...
Oct 17, 2007 3:38:57 PM Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0012.20070328121310.0000
Oct 17, 2007 3:39:01 PM Info: SDM operation mode successfully set to: Integrated
Oct 17, 2007 3:39:02 PM Info: JStartupFramework is requesting to start the SDM Server.
Oct 17, 2007 3:39:02 PM Info: Start the SDM Server integrated in the JStartupFramework.
Oct 17, 2007 3:39:02 PM Info: Initializing Network Manager (50117)
Oct 17, 2007 3:39:02 PM Info: Starting SDM Server listening on port 50118
Oct 17, 2007 3:39:02 PM Info: SDM started successfully.
Oct 17, 2007 3:39:03 PM Info: Opened client connection to loopback (IP address loopback/127.0.0.1, remote port 50633)
Oct 17, 2007 3:39:03 PM Info: SDM started successfully.
Oct 17, 2007 3:39:03 PM Info: Close client connection to loopback/127.0.0.1, remote port 50633
Oct 17, 2007 3:43:00 PM Info:
Oct 17, 2007 3:43:00 PM Info: ===============================================
Oct 17, 2007 3:43:00 PM Info: = Starting to execute command 'remotegui' =
Oct 17, 2007 3:43:00 PM Info: ===============================================
Oct 17, 2007 3:43:03 PM Info: SDM started successfully.
Oct 17, 2007 3:43:29 PM Info: Opened client connection to az18u188 (IP address az18u188/10.196.160.28, remote port 50805)
Oct 17, 2007 3:43:30 PM Info: Request for Logon as admin accepted
Oct 17, 2007 3:44:56 PM Info: Loading archive '/usr/sap/trans/EPS/in/ESS16_0-10002965.SCA'
Oct 17, 2007 3:45:25 PM Info: Loading archive '/usr/sap/trans/EPS/in/ESS16P_1-10002965.SCA'
Oct 17, 2007 3:46:05 PM Info: Actions per selected component:
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/de/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212790'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/no/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212889'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/cn/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212751'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/es/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212845'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tra/tre'/'sap.com'/'MAIN_xss04VAL_C'/'1212869'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/wtcor'/'sap.com'/'MAIN_xss04VAL_C'/'1212723'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/no/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212788'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/jp/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212760'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/rem'/'sap.com'/'MAIN_xss04VAL_C'/'1212734'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ph/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212849'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tw/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212878'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/th/pid'/'sap.com'/'MAIN_xss04VAL_C'/'1212837'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/fi/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212851'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ch/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212830'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/kr/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212873'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/org'/'sap.com'/'MAIN_xss04VAL_C'/'1212719'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/jp/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212757'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ph/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212907'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/fi/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212854'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ph/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212850'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ph/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212906'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tw/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212748'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/au'/'sap.com'/'MAIN_xss04VAL_C'/'1212807'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/au/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212809'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/nz/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212823'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/de/dcomp'/'sap.com'/'MAIN_xss04VAL_C'/'1212791'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/es/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212843'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/se/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212772'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/jp/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212759'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/th/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212902'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/za/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212893'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/se/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212773'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/no/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212789'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/be/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212839'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/za/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212800'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/br/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212766'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/dk/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212826'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/au/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212895'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/kr/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212786'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/no/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212890'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/fr/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212754'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/cn/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212753'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ve/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212816'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ar/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212740'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/pt/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212745'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ar/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212742'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/es/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212844'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/id/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212819'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ie/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212875'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/id/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212821'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/se/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212886'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/us'/'sap.com'/'MAIN_xss04VAL_C'/'1212767'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/za/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212801'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/sg'/'sap.com'/'MAIN_xss04VAL_C'/'1212802'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ch/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212829'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/skl'/'sap.com'/'MAIN_xss04VAL_C'/'1212720'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/cat'/'sap.com'/'MAIN_xss04VAL_C'/'1212718'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/mx/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212896'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/pt/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212747'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/br/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212765'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/fr/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212755'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tra'/'sap.com'/'MAIN_xss04VAL_C'/'1212716'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/mx/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212813'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/pt/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212746'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ar/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212874'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/nl/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212882'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/at/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212887'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/us/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212768'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.16.0.20070410060436''/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/au/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212808'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ca/empeq'/'sap.com'/'MAIN_xss04VAL_C'/'1212778'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/th/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212903'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/sg/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212803'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/hk/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212796'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/dk/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212828'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/th/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212838'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ca/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212779'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/au/tax'/'sap.com'/'MAIN_xss04VAL_C'/'1212811'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/nz/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212898'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/nz/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212825'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/cn/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212752'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/it/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212846'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/dk/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212899'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/hk/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212891'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/sg/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212894'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ve/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212817'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/dk/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212827'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/my/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212835'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ar/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212741'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/gb/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212783'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/fi/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212853'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/it/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212905'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/my/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212901'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/rep'/'sap.com'/'MAIN_xss04VAL_C'/'1212714'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/gb/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212782'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/th/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212836'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/gb/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212784'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/be/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212842'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tra/trp'/'sap.com'/'MAIN_xss04VAL_C'/'1212871'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/wiw'/'sap.com'/'MAIN_xss04VAL_C'/'1212722'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/fr/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212756'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/nz/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212824'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/br/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212764'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ca/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212888'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/in/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212857'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/za/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212892'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/id/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212897'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/sg/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212804'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/nl/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212762'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/xx'/'sap.com'/'MAIN_xss04VAL_C'/'1212795'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/id/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212820'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/nl/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212761'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/fr/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212881'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/at/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212776'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/kr/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212787'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tim'/'sap.com'/'MAIN_xss04VAL_C'/'1212735'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/jp/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212758'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tw/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212879'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ca/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212777'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/de/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212793'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/sg/perid'/'sap.com'/'MAIN_xss04VAL_C'/'1212806'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ve/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212818'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/au/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212810'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/at/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212774'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/br/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212883'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/com'/'sap.com'/'MAIN_xss04VAL_C'/'1212736'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/per'/'sap.com'/'MAIN_xss04VAL_C'/'1212721'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/de'/'sap.com'/'MAIN_xss04VAL_C'/'1212737'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/us/w4'/'sap.com'/'MAIN_xss04VAL_C'/'1212771'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/in/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212858'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/cn/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212880'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/my/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212834'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/grt/srv'/'sap.com'/'MAIN_xss04VAL_C'/'1212738'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/sg/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212805'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tra/trr'/'sap.com'/'MAIN_xss04VAL_C'/'1212715'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ca/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212780'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/us/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212769'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/hk/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212799'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/id/pid'/'sap.com'/'MAIN_xss04VAL_C'/'1212822'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/it/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212848'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/in/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212855'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ie/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212876'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/at/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212775'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/cod'/'sap.com'/'MAIN_xss04VAL_C'/'1212717'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/de/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212792'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tra/trp/trt'/'sap.com'/'MAIN_xss04VAL_C'/'1212872'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/pt/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212877'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/lea'/'sap.com'/'MAIN_xss04VAL_C'/'1212727'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/gb/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212781'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/my/pid'/'sap.com'/'MAIN_xss04VAL_C'/'1212833'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/se/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212885'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ch/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212900'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/us/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212770'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/de/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212794'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/it/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212847'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ie/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212744'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tw/pid'/'sap.com'/'MAIN_xss04VAL_C'/'1212750'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/hk/perid'/'sap.com'/'MAIN_xss04VAL_C'/'1212798'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/in/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212856'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/be/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212841'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/mx/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212812'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/fi/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212852'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/nl/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212763'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ve/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212815'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/kr/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212785'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/be/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212840'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/mx/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212814'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tra/tre/trs'/'sap.com'/'MAIN_xss04VAL_C'/'1212908'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tw/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212749'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/hk/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212797'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/au/rep'/'sap.com'/'MAIN_xss04VAL_C'/'1212739'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ch/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212831'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/tra/tri'/'sap.com'/'MAIN_xss04VAL_C'/'1212870'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/my/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212832'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ie/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212743'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/ben'/'sap.com'/'MAIN_xss04VAL_C'/'1212713'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/us/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212884'/'0' will be deployed.
Oct 17, 2007 3:46:05 PM Info: Initial deployment: Selected development component 'ess/es/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212904'/'0' will be deployed.
Oct 17, 2007 3:46:26 PM Info: Saved current Engine state.
Oct 17, 2007 3:46:29 PM Info: Starting: Initial deployment: Selected development component 'ess/ben'/'sap.com'/'MAIN_xss04VAL_C'/'1212713'/'0' will be deployed.
Oct 17, 2007 3:46:29 PM Info: SDA to be deployed: /usr/sap/BMD/DVEBMGS01/SDM/root/origin/sap.com/ess/ben/MAIN_xss04VAL_C/0/1212713/ess~ben.sda
Oct 17, 2007 3:46:29 PM Info: Software type of SDA: J2EE
Oct 17, 2007 3:46:30 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:48:00 PM Info: Begin of log messages of the target system:
07/10/17 15:46:31 - ***********************************************************
07/10/17 15:46:45 - Start updating EAR file...
07/10/17 15:46:45 - start-up mode is lazy
07/10/17 15:46:45 - EAR file updated successfully for 483ms.
07/10/17 15:46:45 - Start deploying ...
07/10/17 15:47:23 - EAR file uploaded to server for 34995ms.
07/10/17 15:47:55 - Successfully deployed. Deployment took 31943ms.
07/10/17 15:47:55 - Application : sap.com/ess~ben
07/10/17 15:47:55 -
07/10/17 15:47:55 - sap.com/ess~ben - WEBDYNPRO
07/10/17 15:47:55 - ***********************************************************
Oct 17, 2007 3:48:00 PM Info: End of log messages of the target system.
Oct 17, 2007 3:48:00 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:48:00 PM Info: Finished successfully: development component 'ess/ben'/'sap.com'/'MAIN_xss04VAL_C'/'1212713'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.16.0.20070410060436''/'0'
Oct 17, 2007 3:48:00 PM Info: Starting to save the repository
Oct 17, 2007 3:48:02 PM Info: Finished saving the repository
Oct 17, 2007 3:48:09 PM Info: Starting: Initial deployment: Selected development component 'ess/cat'/'sap.com'/'MAIN_xss04VAL_C'/'1212718'/'0' will be deployed.
Oct 17, 2007 3:48:09 PM Info: SDA to be deployed: /usr/sap/BMD/DVEBMGS01/SDM/root/origin/sap.com/ess/cat/MAIN_xss04VAL_C/0/1212718/ess~cat.sda
Oct 17, 2007 3:48:09 PM Info: Software type of SDA: J2EE
Oct 17, 2007 3:48:09 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:48:38 PM Info: Begin of log messages of the target system:
07/10/17 15:48:09 - ***********************************************************
07/10/17 15:48:11 - Start updating EAR file...
07/10/17 15:48:11 - start-up mode is lazy
07/10/17 15:48:11 - EAR file updated successfully for 287ms.
07/10/17 15:48:11 - Start deploying ...
07/10/17 15:48:26 - EAR file uploaded to server for 11797ms.
07/10/17 15:48:33 - Successfully deployed. Deployment took 6856ms.
07/10/17 15:48:33 - Application : sap.com/ess~cat
07/10/17 15:48:33 -
07/10/17 15:48:33 - sap.com/ess~cat - WEBDYNPRO
07/10/17 15:48:33 - ***********************************************************
Oct 17, 2007 3:48:38 PM Info: End of log messages of the target system.
Oct 17, 2007 3:48:38 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:48:38 PM Info: Finished successfully: development component 'ess/cat'/'sap.com'/'MAIN_xss04VAL_C'/'1212718'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.16.0.20070410060436''/'0'
Oct 17, 2007 3:48:38 PM Info: Starting to save the repository
Oct 17, 2007 3:48:39 PM Info: Finished saving the repository
Oct 17, 2007 3:48:47 PM Info: Starting: Initial deployment: Selected development component 'ess/cod'/'sap.com'/'MAIN_xss04VAL_C'/'1212717'/'0' will be deployed.
Oct 17, 2007 3:48:47 PM Info: SDA to be deployed: /usr/sap/BMD/DVEBMGS01/SDM/root/origin/sap.com/ess/cod/MAIN_xss04VAL_C/0/1212717/ess~cod.sda
Oct 17, 2007 3:48:47 PM Info: Software type of SDA: J2EE
Oct 17, 2007 3:48:47 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:49:02 PM Info: Begin of log messages of the target system:
07/10/17 15:48:47 - ***********************************************************
07/10/17 15:48:49 - Start updating EAR file...
07/10/17 15:48:49 - start-up mode is lazy
07/10/17 15:48:49 - EAR file updated successfully for 159ms.
07/10/17 15:48:49 - Start deploying ...
07/10/17 15:48:56 - EAR file uploaded to server for 5159ms.
07/10/17 15:49:00 - Successfully deployed. Deployment took 3408ms.
07/10/17 15:49:00 - Application : sap.com/ess~cod
07/10/17 15:49:00 -
07/10/17 15:49:00 - sap.com/ess~cod - WEBDYNPRO
07/10/17 15:49:00 - ***********************************************************
Oct 17, 2007 3:49:02 PM Info: End of log messages of the target system.
Oct 17, 2007 3:49:02 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:49:02 PM Info: Finished successfully: development component 'ess/cod'/'sap.com'/'MAIN_xss04VAL_C'/'1212717'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.16.0.20070410060436''/'0'
Oct 17, 2007 3:49:02 PM Info: Starting to save the repository
Oct 17, 2007 3:49:03 PM Info: Finished saving the repository
Oct 17, 2007 3:49:10 PM Info: Starting: Initial deployment: Selected development component 'ess/fi/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212852'/'0' will be deployed.
Oct 17, 2007 3:49:10 PM Info: SDA to be deployed: /usr/sap/BMD/DVEBMGS01/SDM/root/origin/sap.com/ess/fi/addr/MAIN_xss04VAL_C/0/1212852/essfiaddr.sda
Oct 17, 2007 3:49:10 PM Info: Software type of SDA: J2EE
Oct 17, 2007 3:49:10 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:49:32 PM Info: Begin of log messages of the target system:
07/10/17 15:49:10 - ***********************************************************
07/10/17 15:49:12 - Start updating EAR file...
07/10/17 15:49:12 - start-up mode is lazy
07/10/17 15:49:13 - EAR file updated successfully for 101ms.
07/10/17 15:49:13 - Start deploying ...
07/10/17 15:49:19 - EAR file uploaded to server for 3943ms.
07/10/17 15:49:23 - Successfully deployed. Deployment took 4561ms.
07/10/17 15:49:23 - Application : sap.com/essfiaddr
07/10/17 15:49:23 -
07/10/17 15:49:23 - sap.com/essfiaddr - WEBDYNPRO
07/10/17 15:49:23 - ***********************************************************
Oct 17, 2007 3:49:32 PM Info: End of log messages of the target system.
Oct 17, 2007 3:49:32 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:49:32 PM Warning: Finished with warnings: development component 'ess/fi/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212852'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.16.0.20070410060436''/'0':
Caught exception during application startup from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while starting application sap.com/ess/fi/addr and wait.
Reason: Clusterwide exception: server ID 19733050:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''sap.com/essfiaddr'' for startup. Reason=
Clusterwide exception: Failed to start application ''sap.com/essfiaddr'': The referenced application ''sap.com/ess~per'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1519)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4612)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4585)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:215)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Oct 17, 2007 3:49:33 PM Info: Starting to save the repository
Oct 17, 2007 3:49:34 PM Info: Finished saving the repository
Oct 17, 2007 3:49:41 PM Info: Starting: Initial deployment: Selected development component 'ess/fi/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212853'/'0' will be deployed.
Oct 17, 2007 3:49:41 PM Info: SDA to be deployed: /usr/sap/BMD/DVEBMGS01/SDM/root/origin/sap.com/ess/fi/bank/MAIN_xss04VAL_C/0/1212853/essfibank.sda
Oct 17, 2007 3:49:41 PM Info: Software type of SDA: J2EE
Oct 17, 2007 3:49:41 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:50:00 PM Info: Begin of log messages of the target system:
07/10/17 15:49:41 - ***********************************************************
07/10/17 15:49:44 - Start updating EAR file...
07/10/17 15:49:44 - start-up mode is lazy
07/10/17 15:49:44 - EAR file updated successfully for 92ms.
07/10/17 15:49:44 - Start deploying ...
07/10/17 15:49:51 - EAR file uploaded to server for 4462ms.
07/10/17 15:49:55 - Successfully deployed. Deployment took 4569ms.
07/10/17 15:49:55 - Application : sap.com/essfibank
07/10/17 15:49:55 -
07/10/17 15:49:55 - sap.com/essfibank - WEBDYNPRO
07/10/17 15:49:55 - ***********************************************************
Oct 17, 2007 3:50:00 PM Info: End of log messages of the target system.
Oct 17, 2007 3:50:00 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:50:00 PM Warning: Finished with warnings: development component 'ess/fi/bank'/'sap.com'/'MAIN_xss04VAL_C'/'1212853'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.16.0.20070410060436''/'0':
Caught exception during application startup from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while starting application sap.com/ess/fi/bank and wait.
Reason: Clusterwide exception: server ID 19733050:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''sap.com/essfibank'' for startup. Reason=
Clusterwide exception: Failed to start application ''sap.com/essfibank'': The referenced application ''sap.com/ess~per'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1519)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4612)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4585)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:215)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Oct 17, 2007 3:50:00 PM Info: Starting to save the repository
Oct 17, 2007 3:50:02 PM Info: Finished saving the repository
Oct 17, 2007 3:50:10 PM Info: Starting: Initial deployment: Selected development component 'ess/fi/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212851'/'0' will be deployed.
Oct 17, 2007 3:50:10 PM Info: SDA to be deployed: /usr/sap/BMD/DVEBMGS01/SDM/root/origin/sap.com/ess/fi/fam/MAIN_xss04VAL_C/0/1212851/essfifam.sda
Oct 17, 2007 3:50:10 PM Info: Software type of SDA: J2EE
Oct 17, 2007 3:50:10 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:50:29 PM Info: Begin of log messages of the target system:
07/10/17 15:50:10 - ***********************************************************
07/10/17 15:50:12 - Start updating EAR file...
07/10/17 15:50:12 - start-up mode is lazy
07/10/17 15:50:12 - EAR file updated successfully for 103ms.
07/10/17 15:50:12 - Start deploying ...
07/10/17 15:50:19 - EAR file uploaded to server for 4423ms.
07/10/17 15:50:24 - Successfully deployed. Deployment took 4678ms.
07/10/17 15:50:24 - Application : sap.com/essfifam
07/10/17 15:50:24 -
07/10/17 15:50:24 - sap.com/essfifam - WEBDYNPRO
07/10/17 15:50:24 - ***********************************************************
Oct 17, 2007 3:50:29 PM Info: End of log messages of the target system.
Oct 17, 2007 3:50:29 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:50:29 PM Warning: Finished with warnings: development component 'ess/fi/fam'/'sap.com'/'MAIN_xss04VAL_C'/'1212851'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.16.0.20070410060436''/'0':
Caught exception during application startup from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while starting application sap.com/ess/fi/fam and wait.
Reason: Clusterwide exception: server ID 19733050:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''sap.com/essfifam'' for startup. Reason=
Clusterwide exception: Failed to start application ''sap.com/essfifam'': The referenced application ''sap.com/ess~per'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1519)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4612)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4585)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:215)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Oct 17, 2007 3:50:29 PM Info: Starting to save the repository
Oct 17, 2007 3:50:30 PM Info: Finished saving the repository
Oct 17, 2007 3:50:39 PM Info: Starting: Initial deployment: Selected development component 'ess/fi/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212854'/'0' will be deployed.
Oct 17, 2007 3:50:39 PM Info: SDA to be deployed: /usr/sap/BMD/DVEBMGS01/SDM/root/origin/sap.com/ess/fi/pdata/MAIN_xss04VAL_C/0/1212854/essfipdata.sda
Oct 17, 2007 3:50:39 PM Info: Software type of SDA: J2EE
Oct 17, 2007 3:50:39 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:50:56 PM Info: Begin of log messages of the target system:
07/10/17 15:50:39 - ***********************************************************
07/10/17 15:50:41 - Start updating EAR file...
07/10/17 15:50:41 - start-up mode is lazy
07/10/17 15:50:41 - EAR file updated successfully for 118ms.
07/10/17 15:50:41 - Start deploying ...
07/10/17 15:50:47 - EAR file uploaded to server for 3980ms.
07/10/17 15:50:52 - Successfully deployed. Deployment took 4287ms.
07/10/17 15:50:52 - Application : sap.com/essfipdata
07/10/17 15:50:52 -
07/10/17 15:50:52 - sap.com/essfipdata - WEBDYNPRO
07/10/17 15:50:52 - ***********************************************************
Oct 17, 2007 3:50:56 PM Info: End of log messages of the target system.
Oct 17, 2007 3:50:56 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:50:56 PM Warning: Finished with warnings: development component 'ess/fi/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'1212854'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.16.0.20070410060436''/'0':
Caught exception during application startup from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while starting application sap.com/ess/fi/pdata and wait.
Reason: Clusterwide exception: server ID 19733050:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''sap.com/essfipdata'' for startup. Reason=
Clusterwide exception: Failed to start application ''sap.com/essfipdata'': The referenced application ''sap.com/ess~per'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1519)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4612)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4585)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:215)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Oct 17, 2007 3:50:56 PM Info: Starting to save the repository
Oct 17, 2007 3:50:57 PM Info: Finished saving the repository
Oct 17, 2007 3:51:05 PM Info: Starting: Initial deployment: Selected development component 'ess/in/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212857'/'0' will be deployed.
Oct 17, 2007 3:51:05 PM Info: SDA to be deployed: /usr/sap/BMD/DVEBMGS01/SDM/root/origin/sap.com/ess/in/addr/MAIN_xss04VAL_C/0/1212857/essinaddr.sda
Oct 17, 2007 3:51:05 PM Info: Software type of SDA: J2EE
Oct 17, 2007 3:51:05 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:51:29 PM Info: Begin of log messages of the target system:
07/10/17 15:51:05 - ***********************************************************
07/10/17 15:51:07 - Start updating EAR file...
07/10/17 15:51:07 - start-up mode is lazy
07/10/17 15:51:07 - EAR file updated successfully for 92ms.
07/10/17 15:51:07 - Start deploying ...
07/10/17 15:51:18 - EAR file uploaded to server for 9799ms.
07/10/17 15:51:23 - Successfully deployed. Deployment took 4606ms.
07/10/17 15:51:23 - Application : sap.com/essinaddr
07/10/17 15:51:23 -
07/10/17 15:51:23 - sap.com/essinaddr - WEBDYNPRO
07/10/17 15:51:23 - ***********************************************************
Oct 17, 2007 3:51:29 PM Info: End of log messages of the target system.
Oct 17, 2007 3:51:29 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 17, 2007 3:51:29 PM Warning: Finished with warnings: development component 'ess/in/addr'/'sap.com'/'MAIN_xss04VAL_C'/'1212857'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.16.0.20070410060436''/'0':
Caught exception during application startup from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while starting application sap.com/ess/in/addr and wait.
Reason: Clusterwide exception: server ID 19733050:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''sap.com/essinaddr'' for startup. Reason=
Clusterwide exception: Failed to start application ''sap.com/essinaddr'': The referenced application ''sap.com/ess~per'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1519)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4612)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4585)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:215)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:1I thinkw aht is happening some of the components which are in error, are referencing some components which are not yet deployed.
Please try and deploy the components which are in error again.
Regards
Jayesh -
The Cluster not failover when i shutdown one managed server?
Hello, I created one cluster whit two managed servers, and deployed an application across the cluster, but the weblogic server gave me two url and two different port for access to this application.
http://server1:7003/App_name
http://server1:7005/App_name
When I shutdown immediate one managed server i lost the connection whit the application from this managed server, My question is, the failover and de load balancer not work, why??
Why two diferent address?
thank any helpWell you have two different addresses (URL) because those are two physical managed servers. By creating a cluster you are not automatically going to have a virtual address (URL) that will load balance requests for that application between those two managed servers.
If you want one URL to access this application, you will have to have some kind of web server in front of your WebLogic. You can install and configure Oracle HTTP Server to route requests to WebLogic cluster. Refer this:
http://download.oracle.com/docs/cd/E12839_01/web.1111/e10144/intro_ohs.htm#i1008837
And this for details on how to configure mod_wl_ohs to route requests from OHS to WLS:
http://download.oracle.com/docs/cd/E12839_01/web.1111/e10144/under_mods.htm#BABGCGHJ
Hope this helps.
Thanks
Shail -
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]
-
Error reading Web application occurs when starting one server in the cluster
Hi All,
I have configured two cluster servers in the win 2000. Admin server also win
2000. One cluster server joins the cluster while other gives following error
and starts. But it seems that it does not join to the cluster view because
prevoius server only serves the requests. I have attached the log also.
<> <101062> <[HTTP synergyserver] Error reading Web application
"D:\bea\wlserver6.0\.\config\bd2kadmindomain\applications\.wl_temp_do_not_de
lete_synergyserver\wl_local_comp12863.war">
java.net.UnknownHostException: java.sun.com
at java.net.InetAddress.getAllByName0(InetAddress.java:571)
at java.net.InetAddress.getAllByName0(InetAddress.java:540)
at java.net.InetAddress.getAllByName(InetAddress.java:533)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:159)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:221)
at weblogic.net.http.HttpClient.<init>(HttpClient.java:85)
at
weblogic.net.http.HttpURLConnection.getHttpClient(HttpURLConnection.java:109
at
weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:30
1)
at java.net.URL.openStream(URL.java:798)
at
weblogic.apache.xerces.readers.DefaultReaderFactory.createReader(DefaultRead
erFactory.java:149)
at
weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternal
Entity(DefaultEntityHandler.java:775)
at
weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternal
Subset(DefaultEntityHandler.java:570)
at
weblogic.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScanner
.java:1131)
at
weblogic.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDecl(XMLDocum
entScanner.java:2177)
at
weblogic.apache.xerces.framework.XMLDocumentScanner.access$0(XMLDocumentScan
ner.java:2133)
at
weblogic.apache.xerces.framework.XMLDocumentScanner$PrologDispatcher.dispatc
h(XMLDocumentScanner.java:882)
at
weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentSca
nner.java:380)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:900)
at
weblogic.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.ja
va:123)
at
weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:1
78)
at weblogic.servlet.internal.HttpServer.loadWARContext(HttpServer.java:446)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:404)
at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
at weblogic.j2ee.Application.addComponent(Application.java:133)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:327)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:143)
at
weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:
76)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:562)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
48)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:439)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:180)
at $Proxy40.addWebDeployment(Unknown Source)
at
weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeploymen
t(WebServerMBean_CachingStub.java:1012)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:313)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:277)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:232)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:192)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:562)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
48)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:439)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:180)
at $Proxy0.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
ServerMBean_CachingStub.java:2299)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
icationManager.java:240)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
r.java:122)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:562)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
48)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:439)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:180)
at $Proxy9.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
ApplicationManagerMBean_CachingStub.java:435)
at weblogic.management.Admin.startApplicationManager(Admin.java:1033)
at weblogic.management.Admin.finish(Admin.java:493)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
Each cluster servers domain names are different i.e. not "mydomain". The
file its complaining is in the specified directory and it has proper
priviledges.
If anyone has an idea please respond.
Thanks
Nalika
[synergyserver.log]
You're getting that probably because the WL instance was not shut down properly.
If that's the case, you'll need to remove an ldap lock file (with a .lok extension) in the directory of ldap files (under the server dir) . -
Deploying a web app into a cluster
Hi Folks,
I like to create a script that will automate the deployment of a web application
(WAR file) into a cluster. I found the weblogic.deploy util which allows updates
on servers.
How do you specify a cluster as the destination of the deployment?
Is there another way to do this?
-RichHi.
You can use weblogic.deploy to deploy to a cluster by specifying the cluster name as
the target parameter instead of individual server names.
Regards,
Michael
Rich wrote:
Hi Folks,
I like to create a script that will automate the deployment of a web application
(WAR file) into a cluster. I found the weblogic.deploy util which allows updates
on servers.
How do you specify a cluster as the destination of the deployment?
Is there another way to do this?
-Rich--
Michael Young
Developer Relations Engineer
BEA Support -
Error calling a webservice from one server process of the cluster
Hi ,
I have a servlet which on startup makes a call to a webservice. I deploy this webapp on the cluster.
The cluster has two instances each instance having one server process.
So when the server restarts one server process on one instance calls the web service the other process on other instance fails with a 503 response code.
When I tried to reproduce the same problem using two server processes on the same instance both processes are able to call the webservice properly.
I am slightly confused as to how different the second scenario is from first one as both are individual server process and may or may not run on same instance.
Can anyone tell me the real cause.
Rgds
ShashankHi Rajat,
This is how the default trace looks
FATAL: Application Servlet failed to notify devices.
Caught java.rmi.RemoteException: Service call exception; nested exception is:
com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (503) Service Unavailable. The requested URL was:"http://<<server>>:50000/ManagementService/ManagementService?style=document"
at com.om.mws.standaloneproxy.ManagementServiceBindingStub.notifyDevice(ManagementServiceBindingStub.java:1289)
at com.om.mws.standaloneproxy.ManagementServiceBindingStub.notifyDevice(ManagementServiceBindingStub.java:1298)
at com.om.ApplicationServlet$NotifyDevices.run(ApplicationServlet.java:86)
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (503) Service Unavailable. The requested URL was:"http://<<server>>:50000/ManagementService/ManagementService?style=document"
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:980)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1430)
at com.om.mws.standaloneproxy.ManagementServiceBindingStub.notifyDevice(ManagementServiceBindingStub.java:1282)
... 2 more
java.lang.NoSuchMethodError
at java.lang.Thread.destroy(Thread.java:779)
at com.omApplicationServlet$NotifyDevices.run(ApplicationServlet.java:92)
Rgds
Shashank -
Problem opening an application deployed in WAS6.40 from the browser
Hello friends!
I developed an application using JBoss-4.0.2. I got the .ear file from there and deployed it in WAS6.40 using "Deploy Tool".I am new to all this. I followed the following steps:-
1. Opened the deploy tool and created a new project with .dlp extension.
2.In the Deployer tab did the following:-
1. Chose Deploy -> EAR -> Load EAR. The File Chooser Window appeared and from the file system, selected the EAR file I wanted to load.
3. The EAR file and all of its components appeared on the Deployer tab as a tree.
4. In the deployer tab clicked on "connect" symbol in the tool bar and entered the following details:-
username - admin
password - *****
host - localhost
port - 50004
5.In the deployer tab Selected the ear file node which is loaded.
6.In the right pane, chose context tab.
7.Set the context root for the war files and pressed modify button.
8.Then with a right click on the loaded ear node in the left pane,selected "deployment"-->"deploy ear" from the context menu.
9.I got a message "Deployed Successfully" and then a message "Start the application y/n".
11.I Chose yes.
12.It gave the message "Application started successfuly". But no browser is opened.
13.So, i tried to open it from the browser using the URL "http://localhost:50000/<context-root>/"
But it is giving the following error:-
404 resource Not Found
The requested resource c:/usr/......./...jsp not found.
I verified the directory where the files are being deployed in the WAS (i.e in C:\usr\sap\J2E\JC00\j2ee\cluster\server0\apps\sap.com\)
The file is present.
What is the problem with my procedure?
Why am I unable to view the application in the browser?
Please tell me if there is any thing else to do.
Also suggest me if there is any other tool in Netweaver that fulfills my requirement apart from "Deploy Tool".
Any kind of help in this regard would be great.Please reply me soon.
Thank You,
Jyothsna.The JNDI call is different when you call an EJB from inside the J2EE.
ctx = new InitialContext();
ref = ctx.lookup("java:comp/env/<JNDI-Name>");
Regards
Stefan -
How to upload files in cluster without bringing down the cluster.
Hi,
Here is my problem:
My weblogic portal 7.0 application should run in 24x7 environment. The production
system is running in a cluster mode with external staging. Both the managed servers
are pointing to the same application sync database.
So to give a solution to this problem, we are trying to bring down one managed
server down and apply the patches into that managed server without bringing down
the other. Since webflow files and entitlements needs to be synchronized with
the portal database. If we perform a sync on the portal database, there might
be a chance that it might corrupt the existing portal database state. Our deployment
would not be complete unless we perform a sync on the other managed servers. So
we could not able to update the latest pathces into the cluster without bringing
down the cluster.
What I would like to know is "Is there any work around to get rid of this problem?".
I would be delighted if any one provides the solution.
Thanks & Regards,
RatnakarHi Ratnakar,
When you perform sync you do it against the admin server which in turn does it
to the managed server. If you want to apply any changes to webflow you can do
it on the live system itself. I mean apply the new webflow and entitlements and
do the sync on the live system. Also while doing sync there are two modes. One
mode will sync only the modified changes and the other will apply all of it. You
can opt for the first option by which you can sync only the modified changes.
This may bring a small disturbance but it will be unnoticed.
The other option is to have two separate domains(each having one admin & one or
more managed servers) which may be having two separate portal databases. In this
way you can apply patches to one domain while other domain may provide the service.
Regards
Shaan
"Ratnakar Sonti" <[email protected]> wrote:
>
Hi,
Here is my problem:
My weblogic portal 7.0 application should run in 24x7 environment. The
production
system is running in a cluster mode with external staging. Both the managed
servers
are pointing to the same application sync database.
So to give a solution to this problem, we are trying to bring down one
managed
server down and apply the patches into that managed server without bringing
down
the other. Since webflow files and entitlements needs to be synchronized
with
the portal database. If we perform a sync on the portal database, there
might
be a chance that it might corrupt the existing portal database state.
Our deployment
would not be complete unless we perform a sync on the other managed servers.
So
we could not able to update the latest pathces into the cluster without
bringing
down the cluster.
What I would like to know is "Is there any work around to get rid of
this problem?".
I would be delighted if any one provides the solution.
Thanks & Regards,
Ratnakar -
About BEA WebLogic JMS on the cluster
Hi,
I have 3 files which together build in 1 EAR, then deploy on the cluster. I can see my message publish to the distributed topic successfully, but the listener process is not work. Could anyone give me a little clue.
// this one publish msg to the distributed topic.
import javax.naming.*;
import javax.jms.*;
import javax.rmi.PortableRemoteObject ;
import java.util.*;
public class PublishTopic {
public final static String JNDI_FACTORY = "weblogic.jndi.WLInitialContextFactory" ;
public final static String JMS_FACTORY = "weblogic.jws.jms.QueueConnectionFactory" ;
public final static String URL = "t3://localhost:7003,localhost:7005" ;
public final static String DIST_TOPIC = "dist_topic" ;
public String publishMsg(String s) throws Exception {
InitialContext ic = getInitialContext();
TopicConnectionFactory tcf = (TopicConnectionFactory) PortableRemoteObject.narrow
(ic.lookup(JMS_FACTORY),TopicConnectionFactory.class);
TopicConnection tc = tcf.createTopicConnection();
TopicSession ts = tc.createTopicSession(false,Session.AUTO_ACKNOWLEDGE);
Topic t = ts.createTopic(DIST_TOPIC);
TopicPublisher tpub = ts.createPublisher(t);
TextMessage msg = ts.createTextMessage(s);
tc.start();
tpub.publish(msg);
tc.close();
return "publish - : " + msg.getText();
public static InitialContext getInitialContext()throws NamingException {
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);
ht.put(Context.PROVIDER_URL,URL);
return new InitialContext(ht);
=================================================
// the listener one.
import javax.rmi.PortableRemoteObject ;
import java.util.HashMap;
import java.util.Date;
import javax.naming.*;
import javax.jms.*;
import java.io.*;
public class ListenMsg implements MessageListener {
private static HashMap hm ;
private static TopicConnection tcon ;
static {
// the coding inside static will process once every time
// class load. The code inside here should be
// 1. subscrib to the distributed topic
// 2. refresh the static var.
ListenMsg lm = new ListenMsg();
lm.retrieveDB();
lm.subscribTopic();
lm = null ;
public void onMessage(Message m) {
try {
PrintWriter p = new PrintWriter(new FileOutputStream
("C:/bea/user_projects/applications/TestJMS/JMSLog.txt",true));
p.println(new Date().toLocaleString());
p.println(((TextMessage)m).getText() + "\n");
// check to see the content of m then decide whether
// to call retrieveDB.
} catch (Exception e) {
} finally {
if (tcon != null)
try {
tcon.close();
} catch (Exception e) {}
private void retrieveDB () {
// connect to DB then select the allow/unallow-list.
private void subscribTopic(){
try {
InitialContext ic = PublishTopic.getInitialContext();
TopicConnectionFactory tcf = (TopicConnectionFactory) PortableRemoteObject.narrow
(ic.lookup(PublishTopic.JMS_FACTORY),TopicConnectionFactory.class);
tcon = tcf.createTopicConnection();
TopicSession tsess = tcon.createTopicSession(false,Session.AUTO_ACKNOWLEDGE);
// crateTopic doesn't actually create a new one but instead
// obtain a reference to the object which given name.
Topic t = tsess.createTopic(PublishTopic.DIST_TOPIC);
TopicSubscriber tsub = tsess.createSubscriber(t);
tsub.setMessageListener(this);
tcon.start();
} catch(JMSException je) {
je.printStackTrace();
} catch (NamingException ne) {
ne.printStackTrace();
} catch (Exception e) {
e.printStackTrace();
public boolean isAuthorized(String username, String servicename) {
// check against hm.
return true ;
===============================================
// the web service file.
public class TestPublish implements com.bea.jws.WebService
static final long serialVersionUID = 1L;
* @common:operation
public String sendMsg(String s) throws Exception {
String r = "";
try {
PublishTopic pt = new PublishTopic();
r = pt.publishMsg(s);
} catch(Exception e) {
e.printStackTrace();
throw e;
return r;
A big thanks in advance.
TaninHi
Please verify that the listener points to the correct JNDI name
Do you see any error in the log ?
Jin -
Deploying with Workshop to a WLI cluster
Hello!
I have a WLI 8.1 cluster running ok on server enviroment.
My WLS Workshop is installed on my workstation were Workflow developing will be
done.
I need Workshop to be able to deploy to the cluster and not to a particular managed
server, like the Tools-Weblogic Server-Server Properties... option only lets me
configure. The ServerHomeDirectory text box assumes a local WLI domain directory.
Mine is in another server on the network.
Please help
RicardoRicardo,
The Workshop IDE supports development in a single server environment. You
can point the IDE to a single WebLogic server instance. After you have
completed the development, you can create an EAR for the Workshop
application and deploy it on a cluster.
Please refer to the Workshop documentation section
How Do I > Deployment and Administration
for further details.
Regards,
Anurag
"Ricardo Madariaga" <[email protected]> wrote in message
news:3f832855$[email protected]..
>
Hello!
I have a WLI 8.1 cluster running ok on server enviroment.
My WLS Workshop is installed on my workstation were Workflow developingwill be
done.
I need Workshop to be able to deploy to the cluster and not to aparticular managed
server, like the Tools-Weblogic Server-Server Properties... option onlylets me
configure. The ServerHomeDirectory text box assumes a local WLI domaindirectory.
Mine is in another server on the network.
Please help
Ricardo -
How to maintain the state in the cluster environment?
HI Guys,
I had a list with String values.I deployed the project in the cluster.
I had a get method which will be invoked by servers in the cluster.
when the request given by first server. it has to remove the first value in the list.
when the request given by other server,it has to remove the next value in the list.
So how to achieve this functionality?
Regards,
PraveenHi,
use a setPropertyListener to save the row key of this select item and then restore this key as the current selected key.
Frank
Ps.: I don't ask why you call clearForRecreate() on the iterator. I am sure you have a reason.
Maybe you are looking for
-
Looking for an app that I can save what I highlight when I am reading an article without having to copy and paste
-
Event Handling in OADialogPage
Hi, I have a scenario for my project. where user should get a alert message with Ok(Proceed) and Cancel Buttons, when the budget for ticket is insufficient. After the alert, if user clicks on "Proceed", then it should navigate to confirmation page. I
-
Windows detects nano but iTunes does NOT detect even aftr doing all steps
my windows detects nano but iTunes does NOT detect even after doing all the steps described in the site. Any help ??? please ....
-
I received an iTunes gift code from some relatives who live in the Uk. I live in Italy, so my account is italian and, apparently, I can't use the code in the italian iTunes store. Is that correct? I tried to create a new english account, but it's nec
-
Dynamic actions on button and dynamic column name
Hi!ynam I want to create a dynamic action on button click in my tabular form. I have a select list with values of my column names (P7_X_COLUMN) and a text field where users input values for update (P7_X_UVALUE). My idea is that when they click the bu