Importing Speed ESS package
Hello,
we have a portal wirth NW04s SP14, ERP2005 SP12 running on DB2 V.9 and AIX 5.3. If we import over NWDI ESS packages which our developers have changed, the import via NWDI, SDM always takes longer on production system compares to our quality system. For an ESS package it takes 1:30 hours on quality and 3:30 hours on production.
a) Is there a way to speed up the import? Our system get's quite unstable during the importing time.
b) Can the amount of server nodes be a reason for the different importing speed (qa=2, prod=16). also I don't believe it, because as fas as I know the SDM is only importing into one server nodes and afterwards during the start replicating the new data to all the other server nodes.
c) Have someone an idea how to speed up the import? I have heard that Netweaver Enhancement Package 1 will help, because then it isn't necessary anymore to import the whole sca file, which is in case for ess really big (400MB).
Regards,
Alexander
Madhavi,
Check this
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e26a6e3-0601-0010-d798-d307801a158d
Anil
Similar Messages
-
Hi,
I'm trying to configure the ESS Business package to work in the EP6 SP10, but don't work. Page can't be displayed is the error message.
What I've done:
- Imported the ESS package,
- Created the System to connect to the R/3 system (tested and it works)
- Mapped the EP user to the R/3 user
- Added the ESS role to the EP user group
- Created the IT 0105 subty 001 in the R/3 employee.
What else?
Thanks for any information
Best reegards,
AdrianoWe'll need a bit more information...
What is the real http error? 404, 500, ....
Have you traced from the browser and checked that the URLs are correct and pointed to the right host:port?
Have you traced from SM50 on the R/3 side to see whether your request is making it to the backend?
Nick -
Import Speed for EH3 on Portal
Hello,
we are importing over NWDI the (erp2005) EH3 into our portal. The EH3 for example ess 603 sca is now 500MB big and it takes endless time to bring this in the portal. has someone already implemented (erp2005) eh3 on their system? is there a way to speed this up? I can't see any load on the servers, but the import only for the ess packages takes hours. now it is already running for 5 hours. i'm not looking forward to implement the whole eh3 into prod....
regards,
alexanderI usually import on my Windows PC since it has a faster drive and a lot more disk space, and then play it on my Mac Mini (used as a media centre) over the network.
-
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 -
CMS import failure - ESS (Dirty DC)
Hi jdi gurus,
Please help out ...
the MSS, pcui, buildt, jee, jtech packages have been imported successfully into development and consolidation.
however the ess package is not being imported into development.
with respect,
amit
WebAS 640, EP 6.0, SP 13 on Windows with MS SQL server, ESS 100, SP 9.
CMS-make
Info:Starting Step CBS-make at 2006-09-14 17:03:44.0842 +12:00
Info:wait until CBS queue of buildspace EPD_ESSTrack_D is completely processed, before starting the import
Info:waiting for CBS queue activity
Info:wait until CBS queue of buildspace EPD_ESSTrack_D is completely processed, before asking for build results
Info:waiting for CBS queue activity
Info:build process already running: waiting for another period of 30000 ms (1)
Info:CBS server log has been written to CBS log
Fatal:the compartment sap.com_SAP_ESS_1 contains dirty DCs after the CBS build process:
Info:dirty DC in compartment sap.com_SAP_ESS_1 (dcname=ess/tra/tre dcvendor=sap.com)
Info:dirty DC in compartment sap.com_SAP_ESS_1 (dcname=ess/tra/tre/trs dcvendor=sap.com)
Fatal:communication error: CBS error: dirty DCs in buildspace after the CBS build process
Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2006-09-14 17:04:18.0077 +12:00
CBS Log :-
CBS Request Log - [ 295/EPD_ESSTrack_D ]
devep SAP Component Build Server
Build number assigned: 305
Change request state from QUEUED to PROCESSING
ACTIVATION request in Build Space "EPD_ESSTrack_D" at Node ID: 5,717,050
[id: 295; parentID: 0; type: 4]
[options: IGNORE BROKEN DC, FORCE ACTIVATE PREDECESSORS, FORCE INTEGRATED, IGNORE COMPONENT INTERSECTION]
REQUEST PROCESSING started at 2006-09-14 05:03:52.280 GMT
===== Pre-Processing =====
List of activities to be activated:
The following components belong to activities which already have been activated before:
sap.com/ess/tra/tre/trs
sap.com/ess/mx/addr
sap.com/ess/fr/addr
sap.com/ess/tra/trp
sap.com/ess/de/fam
sap.com/ess/br/addr
sap.com/ess/tra
sap.com/ess/au
sap.com/ess/tra/tre
sap.com/ess/it/pdata
sap.com/ess/hk/fam
sap.com/ess/us/pdata
sap.com/ess/tw/fam
sap.com/ess/sg/addr
sap.com/ess/de/pdata
sap.com/ess/ca/addr
sap.com/ess/kr/bank
sap.com/ess/be/fam
sap.com/ess/us
sap.com/ess/kr/fam
sap.com/ess/ar/addr
sap.com/ess/hk/addr
sap.com/ess/ph/pdata
sap.com/ess/wtcor
sap.com/ess/us/addr
sap.com/ess/at/addr
sap.com/ess/mx/pdata
sap.com/ess/wiw
sap.com/ess/ca/empeq
sap.com/ess/th/bank
sap.com/ess/dk/fam
sap.com/ess/tw/bank
sap.com/ess/th/pdata
sap.com/ess/grt/srv
sap.com/ess/be/bank
sap.com/ess/mx/fam
sap.com/ess/es/fam
sap.com/ess/at/pdata
sap.com/ess/ie/fam
sap.com/ess/ch/fam
sap.com/ess/id/addr
sap.com/ess/xx
sap.com/ess/ca/pdata
sap.com/ess/nz/pdata
sap.com/ess/de/dcomp
sap.com/ess/gb/pdata
sap.com/ess/au/addr
sap.com/ess/th/fam
sap.com/ess/cn/bank
sap.com/ess/ve/bank
sap.com/ess/nl/fam
sap.com/ess/es/bank
sap.com/ess/sg/perid
sap.com/ess/skl
sap.com/ess/cat
sap.com/ess/nl/addr
sap.com/ess/fr/pdata
sap.com/ess/se/pdata
sap.com/ess/au/bank
sap.com/ess/ben
sap.com/ess/lea
sap.com/ess/it/addr
sap.com/ess/ie/bank
sap.com/ess/au/pdata
sap.com/ess/th/pid
sap.com/ess/be/pdata
sap.com/ess/id/bank
sap.com/ess/de/addr
sap.com/ess/nz/bank
sap.com/ess/tra/tri
sap.com/ess/jp/addr
sap.com/ess/au/rep
sap.com/ess/us/w4
sap.com/ess/us/bank
sap.com/ess/rep
sap.com/ess/nz/addr
sap.com/ess/za/pdata
sap.com/ess/tra/trr
sap.com/ess/cn/addr
sap.com/ess/de
sap.com/ess/be/addr
sap.com/ess/tw/pdata
sap.com/ess/my/addr
sap.com/ess/hk/perid
sap.com/ess/cod
sap.com/ess/th/addr
sap.com/ess/gb/fam
sap.com/ess/au/tax
sap.com/ess/us/fam
sap.com/ess/ch/pdata
sap.com/ess/ca/bank
sap.com/ess/ie/addr
sap.com/ess/ca/fam
sap.com/ess/za/fam
sap.com/ess/se/bank
sap.com/ess/jp/bank
sap.com/ess/fr/fam
sap.com/ess/ve/fam
sap.com/ess/ve/pdata
sap.com/ess/sg/fam
sap.com/ess/ph/bank
sap.com/ess/sg/bank
sap.com/ess/au/fam
sap.com/ess/sg/pdata
sap.com/ess/sg
sap.com/ess/ve/addr
sap.com/ess/com
sap.com/ess/ar/pdata
sap.com/ess/gb/addr
sap.com/ess/nl/pdata
sap.com/ess/kr/addr
sap.com/ess/tw/pid
sap.com/ess/no/pdata
sap.com/ess/cn/fam
sap.com/ess/hk/bank
sap.com/ess/es/pdata
sap.com/ess/pt/bank
sap.com/ess/se/fam
sap.com/ess/id/fam
sap.com/ess/dk/pdata
sap.com/ess/jp/pdata
sap.com/ess/no/fam
sap.com/ess/at/bank
sap.com/ess/it/fam
sap.com/ess/per
sap.com/ess/br/fam
sap.com/ess/ie/pdata
sap.com/ess/pt/pdata
sap.com/ess/gb/bank
sap.com/ess/hk/pdata
sap.com/ess/my/pdata
sap.com/ess/jp/fam
sap.com/ess/za/bank
sap.com/ess/tw/addr
sap.com/ess/mx/bank
sap.com/ess/ar/bank
sap.com/ess/cn/pdata
sap.com/ess/pt/addr
sap.com/ess/at/fam
sap.com/ess/rem
sap.com/ess/my/bank
sap.com/ess/it/bank
sap.com/ess/br/pdata
sap.com/ess/nl/bank
sap.com/ess/ch/addr
sap.com/temp/testit0188
sap.com/temp/testit0185
sap.com/temp/testit0006_au
sap.com/temp/pers_data_sg
sap.com/temp/essmenu
sap.com/temp/ESS_Homepage
sap.com/temp/bentest
sap.com/temp/address_sg
sap.com/ess/id/pdata
sap.com/ess/de/bank
sap.com/ess/tim
sap.com/ess/my/fam
sap.com/ess/se/addr
sap.com/ess/kr/pdata
sap.com/ess/ar/fam
sap.com/ess/no/bank
sap.com/ess/pt/fam
sap.com/ess/nz/fam
sap.com/ess/no/addr
sap.com/ess/tra/trp/trt
sap.com/ess/dk/bank
sap.com/ess/ph/fam
sap.com/ess/ch/bank
sap.com/ess/es/addr
sap.com/ess/id/pid
sap.com/ess/org
sap.com/ess/dk/addr
sap.com/ess/ph/addr
sap.com/ess/my/pid
sap.com/ess/za/addr
sap.com/ess/fr/bank
sap.com/ess/br/bank
sap.com/ess/tri
sap.com/ess/trt
sap.com/ess/tev
They will be removed from this request.
Analyse dependencies to predecessor activities... started at 2006-09-14 05:03:52.733 GMT
Analyse dependencies to predecessor activities... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
Analyse activities... started at 2006-09-14 05:03:52.733 GMT
Analyse activities... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
Calculate all combinations of components and variants to be built...
Prepare build environment in the file system... started at 2006-09-14 05:03:52.733 GMT
Synchronize development configuration... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
Synchronize component definitions... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
Synchronize sources...
...Skipped for Activation with option : IGNORE BROKEN DC
Synchronize sources... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
Synchronize used libraries...
...Skipped for Activation with option : IGNORE BROKEN DC
Synchronize used libraries... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
Prepare build environment in the file system... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
===== Pre-Processing ===== finished at 2006-09-14 05:03:52.733 GMT and took 438 ms
===== Processing =====
===== Processing ===== finished at 2006-09-14 05:03:52.748 GMT and took 0 ms
===== Post-Processing =====
Check whether build was successful for all required variants...
..SKIPPED. Request option "IGNORE BROKEN DC" was given.
Update component metadata...
STORE build results...
Change request state from PROCESSING to SUCCEEDED
Analyse effect of applied changes to buildspace state... started at 2006-09-14 05:03:52.764 GMT
Handle Cycles...
No cycles detected.
Determine components that have become DIRTY due to this request...
No such components have been found.
Integrate activities into active workspace(s)...
Nothing to integrate in compartment sap.com_SAP_ESS_1
Analyse effect of applied changes to buildspace state... finished at 2006-09-14 05:03:53.327 GMT and took 563 ms
Request SUCCEEDED
===== Post-Processing ===== finished at 2006-09-14 05:03:53.327 GMT and took 563 ms
REQUEST PROCESSING finished at 2006-09-14 05:03:53.327 GMT and took 1 s 47 ms
Message was edited by: Amit ChawatheHi Marc,
Thank you for your time and attention to the problem at hand. It is most appreciated.
The CBS log life of the request in question is pasted below.Please let me know if there is any more information you would require.
with respect,
amit
CBS Request Log - [ 295/EPD_ESSTrack_D ]
devep SAP Component Build Server
Build number assigned: 305
Change request state from QUEUED to PROCESSING
ACTIVATION request in Build Space "EPD_ESSTrack_D" at Node ID: 5,717,050
[id: 295; parentID: 0; type: 4]
[options: IGNORE BROKEN DC, FORCE ACTIVATE PREDECESSORS, FORCE INTEGRATED, IGNORE COMPONENT INTERSECTION]
REQUEST PROCESSING started at 2006-09-14 05:03:52.280 GMT
===== Pre-Processing =====
List of activities to be activated:
The following components belong to activities which already have been activated before:
sap.com/ess/tra/tre/trs
sap.com/ess/mx/addr
sap.com/ess/fr/addr
sap.com/ess/tra/trp
sap.com/ess/de/fam
sap.com/ess/br/addr
sap.com/ess/tra
sap.com/ess/au
sap.com/ess/tra/tre
sap.com/ess/it/pdata
sap.com/ess/hk/fam
sap.com/ess/us/pdata
sap.com/ess/tw/fam
sap.com/ess/sg/addr
sap.com/ess/de/pdata
sap.com/ess/ca/addr
sap.com/ess/kr/bank
sap.com/ess/be/fam
sap.com/ess/us
sap.com/ess/kr/fam
sap.com/ess/ar/addr
sap.com/ess/hk/addr
sap.com/ess/ph/pdata
sap.com/ess/wtcor
sap.com/ess/us/addr
sap.com/ess/at/addr
sap.com/ess/mx/pdata
sap.com/ess/wiw
sap.com/ess/ca/empeq
sap.com/ess/th/bank
sap.com/ess/dk/fam
sap.com/ess/tw/bank
sap.com/ess/th/pdata
sap.com/ess/grt/srv
sap.com/ess/be/bank
sap.com/ess/mx/fam
sap.com/ess/es/fam
sap.com/ess/at/pdata
sap.com/ess/ie/fam
sap.com/ess/ch/fam
sap.com/ess/id/addr
sap.com/ess/xx
sap.com/ess/ca/pdata
sap.com/ess/nz/pdata
sap.com/ess/de/dcomp
sap.com/ess/gb/pdata
sap.com/ess/au/addr
sap.com/ess/th/fam
sap.com/ess/cn/bank
sap.com/ess/ve/bank
sap.com/ess/nl/fam
sap.com/ess/es/bank
sap.com/ess/sg/perid
sap.com/ess/skl
sap.com/ess/cat
sap.com/ess/nl/addr
sap.com/ess/fr/pdata
sap.com/ess/se/pdata
sap.com/ess/au/bank
sap.com/ess/ben
sap.com/ess/lea
sap.com/ess/it/addr
sap.com/ess/ie/bank
sap.com/ess/au/pdata
sap.com/ess/th/pid
sap.com/ess/be/pdata
sap.com/ess/id/bank
sap.com/ess/de/addr
sap.com/ess/nz/bank
sap.com/ess/tra/tri
sap.com/ess/jp/addr
sap.com/ess/au/rep
sap.com/ess/us/w4
sap.com/ess/us/bank
sap.com/ess/rep
sap.com/ess/nz/addr
sap.com/ess/za/pdata
sap.com/ess/tra/trr
sap.com/ess/cn/addr
sap.com/ess/de
sap.com/ess/be/addr
sap.com/ess/tw/pdata
sap.com/ess/my/addr
sap.com/ess/hk/perid
sap.com/ess/cod
sap.com/ess/th/addr
sap.com/ess/gb/fam
sap.com/ess/au/tax
sap.com/ess/us/fam
sap.com/ess/ch/pdata
sap.com/ess/ca/bank
sap.com/ess/ie/addr
sap.com/ess/ca/fam
sap.com/ess/za/fam
sap.com/ess/se/bank
sap.com/ess/jp/bank
sap.com/ess/fr/fam
sap.com/ess/ve/fam
sap.com/ess/ve/pdata
sap.com/ess/sg/fam
sap.com/ess/ph/bank
sap.com/ess/sg/bank
sap.com/ess/au/fam
sap.com/ess/sg/pdata
sap.com/ess/sg
sap.com/ess/ve/addr
sap.com/ess/com
sap.com/ess/ar/pdata
sap.com/ess/gb/addr
sap.com/ess/nl/pdata
sap.com/ess/kr/addr
sap.com/ess/tw/pid
sap.com/ess/no/pdata
sap.com/ess/cn/fam
sap.com/ess/hk/bank
sap.com/ess/es/pdata
sap.com/ess/pt/bank
sap.com/ess/se/fam
sap.com/ess/id/fam
sap.com/ess/dk/pdata
sap.com/ess/jp/pdata
sap.com/ess/no/fam
sap.com/ess/at/bank
sap.com/ess/it/fam
sap.com/ess/per
sap.com/ess/br/fam
sap.com/ess/ie/pdata
sap.com/ess/pt/pdata
sap.com/ess/gb/bank
sap.com/ess/hk/pdata
sap.com/ess/my/pdata
sap.com/ess/jp/fam
sap.com/ess/za/bank
sap.com/ess/tw/addr
sap.com/ess/mx/bank
sap.com/ess/ar/bank
sap.com/ess/cn/pdata
sap.com/ess/pt/addr
sap.com/ess/at/fam
sap.com/ess/rem
sap.com/ess/my/bank
sap.com/ess/it/bank
sap.com/ess/br/pdata
sap.com/ess/nl/bank
sap.com/ess/ch/addr
sap.com/temp/testit0188
sap.com/temp/testit0185
sap.com/temp/testit0006_au
sap.com/temp/pers_data_sg
sap.com/temp/essmenu
sap.com/temp/ESS_Homepage
sap.com/temp/bentest
sap.com/temp/address_sg
sap.com/ess/id/pdata
sap.com/ess/de/bank
sap.com/ess/tim
sap.com/ess/my/fam
sap.com/ess/se/addr
sap.com/ess/kr/pdata
sap.com/ess/ar/fam
sap.com/ess/no/bank
sap.com/ess/pt/fam
sap.com/ess/nz/fam
sap.com/ess/no/addr
sap.com/ess/tra/trp/trt
sap.com/ess/dk/bank
sap.com/ess/ph/fam
sap.com/ess/ch/bank
sap.com/ess/es/addr
sap.com/ess/id/pid
sap.com/ess/org
sap.com/ess/dk/addr
sap.com/ess/ph/addr
sap.com/ess/my/pid
sap.com/ess/za/addr
sap.com/ess/fr/bank
sap.com/ess/br/bank
sap.com/ess/tri
sap.com/ess/trt
sap.com/ess/tev
They will be removed from this request.
Analyse dependencies to predecessor activities... started at 2006-09-14 05:03:52.733 GMT
Analyse dependencies to predecessor activities... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
Analyse activities... started at 2006-09-14 05:03:52.733 GMT
Analyse activities... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
Calculate all combinations of components and variants to be built...
Prepare build environment in the file system... started at 2006-09-14 05:03:52.733 GMT
Synchronize development configuration... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
Synchronize component definitions... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
Synchronize sources...
...Skipped for Activation with option : IGNORE BROKEN DC
Synchronize sources... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
Synchronize used libraries...
...Skipped for Activation with option : IGNORE BROKEN DC
Synchronize used libraries... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
Prepare build environment in the file system... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
===== Pre-Processing ===== finished at 2006-09-14 05:03:52.733 GMT and took 438 ms
===== Processing =====
===== Processing ===== finished at 2006-09-14 05:03:52.748 GMT and took 0 ms
===== Post-Processing =====
Check whether build was successful for all required variants...
..SKIPPED. Request option "IGNORE BROKEN DC" was given.
Update component metadata...
STORE build results...
Change request state from PROCESSING to SUCCEEDED
Analyse effect of applied changes to buildspace state... started at 2006-09-14 05:03:52.764 GMT
Handle Cycles...
No cycles detected.
Determine components that have become DIRTY due to this request...
No such components have been found.
Integrate activities into active workspace(s)...
Nothing to integrate in compartment sap.com_SAP_ESS_1
Analyse effect of applied changes to buildspace state... finished at 2006-09-14 05:03:53.327 GMT and took 563 ms
Request SUCCEEDED
===== Post-Processing ===== finished at 2006-09-14 05:03:53.327 GMT and took 563 ms
REQUEST PROCESSING finished at 2006-09-14 05:03:53.327 GMT and took 1 s 47 ms -
Hi exparts,
We are using EP 7 and <b>ESS 600 SP7</b>...with ECC6. We implemented ESS in our Development server. We had done some customization in ESS. Now is it possible to transport the business package from the <b>EP Dev to our EP Production</b> server. can it be done through the <b>Transport packages</b> from portal by exporting and again importing it in the production. I also worry about the <b>JCOs</b> will working then?? Or we need to do the whole stuffs again?? We had deployed in the development.
BPERP5ESS07_0-10003288.SCA
BPERP5COM07_0-20001067.SCA
SAPESS07_0-20000512.SCA
SAPPCUIGP07_0-20001215.SCA
Please help me out.
Point will be given for any repley.
Regards,
SekharHi Sekhar,
First of all, as you had done on the EP Development Server, you need to deploy these sca files:
BPERP5ESS07_0-10003288.SCA
BPERP5COM07_0-20001067.SCA
SAPESS07_0-20000512.SCA
SAPPCUIGP07_0-20001215.SCA
<b>We had done some customization in ESS.</b>
Depends on what kind of customization you have done.
1) If you have just configured or customized the ESS Applications using SPRO, you need to maintain the same SPRO settings on backend system (I assume it should be R3 Production Server). You can still do with just deploying the above listed .sca files.
2) If it's just customization of worksets, pages, roles or iviews i.e. changing names or removing some of the pages etc. then you can just create a transport package and export them to the production system.
3) If you done both 1) and 2), then you need maintain SPRO as well as create a transport package on portal for roles, pages, worksets and iviews and export from Portal Development to Portal Production.
4) If you have customized the code of these application, you need to deploy these customized ESS applications on Portal Production Server too. I believe you had used JDI for importing these ESS applications and customizing them. I believe you have created tracks for the same. You can just transport these customized applications on Portal Production Server using the same tracks.
5) If it's a combination of 1,2 and 4 then you know by now what you have to do :-).
<b>I also worry about the JCOs will working then.</b>
You will have to configure the JCO connections there on the Portal Production System also. You need to specify the backend server i.e. R3 Production Server that you would be connecting to and the service user which is there on the R3 Production System. And needless to say, we also need to configure SSO between R3 Production System and Portal System.
Hope this helps.
Cheers,
Sunil
PS: Reward points for helpful answers. -
Error deploying the .SCA files in SDM related to ESS packages
Hi Experts,
I am getting the following error , when i deploy the .SCA file related to the ESS packages. Kindly let mek now what could be the issue to fix this problem.
already deployed following files.
1. SAPPCUIGP04_0-20001215.sca
2. BPERP4ESS01_0-10003146.sca
Error:
Unresolved dependencies found for the following SDAs:
1.: development component 'abcau/ess/au/rep'/'abc.com'/'JD3_XSP11MOD_C'/'27510'/'0'
dependency:
name: 'ess/rep'
vendor: 'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
2.: development component 'abcau/ess/au/bank_dc'/'abc.com'/'JD3_XSP11MOD_C'/'27505'/'0'
dependency:
name: 'ess/per'
vendor: 'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
name: 'ess/xx'
vendor: 'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
3.: development component 'abcau/ess_rem'/'abc.com'/'JD3_XSP11MOD_C'/'27509'/'0'
dependency:
name: 'ess/per'
vendor: 'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
Deployment will be aborted.
Regards
VijayHi,
This is known issue....
SAP resolved this in SAP ESS SP Stack 20.
So when deployment error occurs for Austrlian DC's, import SAP ERP SP Stack 20.
Refer SAP Note# 1167226
If you face this again....better contact SAP.
~ Padmanaban -
Purpose of Update/Overwrite Hierarchy in Import master data package
Hi All,
Please let me know what is the difference in update and overwrite option in import master data package. Here when i tried running the package, both the option are altering the hierarchy of existing member.
My requirement is just to add a new member ID, if it already exist it should not affect those records and only update the new master data records.
Thanks & Regards,
RamanathanHi Ramanathan,
You can run Import Master Data DM package in BPC to perform delta master data load. While you run DM package you get option to load Master Data from BW/BI where you can select:
1. MERGE: this will keep old data intact and also load new master data, and
2. COPY and REPLACE: This will copy new data and delete old master data.
As per your requirement, you need to select the First option. If you select Update option then it will not delete old master data, instead update the members and hierarchy according to the parent-children design which you would have given in the dimension membersheet.
Hope this corresponds to your requirement.
Rgds,
Poonam -
Problem in downloading ESS package
Dear All,
I m trying to download ESS package from market place,
Description: BP ERP05 ESS 1.0 Support Package 13
File name: BPERP5ESS13_0-10003288.SCA
But I m getting following message:
"All corrective software packages, for SAP NetWeaver 2004s and SAP Business Suite 2005 and beyond that are delivered after April 2nd, 2007 will ONLY be available via SAP Solution Manager's Maintenance Optimizer."
and Download Status is "Request approval"
Please guide me how to go about it as I dont have any clue, and besides this also let me know what else do I need to download for implementing ESS buss. pakg. in NW7.0, EP6.0
Its really urgent guys....plz throw in your help.
pts will be awarded for any help
Regards,
JJJoshi,
In addition to the Business Packages, you will need the actual packages which contain the WD applications for ESS/MSS, I think they are referred as XSS packages and along with that you will need other two packages PCUI and Common parts package.
Just do a search on marketplace and you will get links for them.
Additionally read these notes : Note 1004528 & 1007341.
Chintan -
How to import a tcl package in Java
Hi,
I want to convert an existing tcl file into a java source file. In my existing tcl file, some tcl packages have been imported, using the syntax
package requires XML
where "XML" is the name of a tcl package.
But I am not sure how to import this tcl package in my Java code. Also, how can i call tcl procedures from Java code. The tcl package file contains a set of tcl procedures.
Please let me know that
1> How can I import/call a tcl package in a Java code.
2> How can I call a tcl procedure in a Java code. The tcl procedure is contained in the tcl package file.I have searched the url provided by you. But I couldn't find anything relevant to my requirements.
They have basically explained about how to call a Java program from a tcl code using java::call command
But they haven't provided anything related to importing tcl package files inside java source.
Please let me know your opinion on this issue. -
Import javax.mail package does not exists
Hi,
when i tried to compile the source code for email using jdk1.3.1, it compiled fine. but when i tried to compile using jdk1.4.., it had the following errors such as
import javax.mail package does not exists,
import javax.mail.internet package does not exists
package javax.activation does not exist
Is it because of the jdk version problem???
Pls help meI have the same problem with javax.ejb
Now i've downloaded and installed the j2ee and set my classpath to the j2ee.jar. I've had to make a new path cause i'm running XP.
This doesn't work.
to compile it in Jcreator or JBuilder I can make it work by adding this package (j2ee.jar) in the project settings - required libraries.
But I have to do this for every project again and again.
I can make it work but i thougt the classpath would be enough ??
Bassegio -
Are there preferences or some other settings that can be adjusted to significantly improve the import speed?
On a system with an e6700 processor, SATA mirror drives, and 4GB of memory running XP64 - I dump a dozen or so directories with around 9500 .dng files total, and LR takes forever to get them imported... This thing has been sitting here churning for over 2 hours and its still not done......
Images, cache, swapfile, and product are all on separate spindles, so I presume there's got to be some setting (or settings) I have dreadfully wrong for things to be this slow... So, what do I change to speed this up 'cause this is only about 20% of what I'm organizing and I'd rather not have LR take a week to just import the images?Since LR is STILL churning I can't look at the preferences, but I thought there was something that told it to just use whatever was in the imported image? If so, shouldn't this get rid of this insanely long process of rendering? Or is this just one of those things I'll have to start when I go to bed and hope its managed to do a few thousand images by morning?...
Are ALL these tools this poor performing? I haven't tried this in iView or one of the others, but if they're significantly faster I can see dumping LR back on the shelf until something gets done to improve this. -
How to Import a DTS Package, while keeping version History in Destination Intact
Hi Guys,
Not sure if this is the right forum for my question. But I couldn't find any other DTS forum to post my query.
Basically, I have my Production Environment in SQL 2008R2 and it contains few DTS [NOT SSIS!!!!] packages in Management > Legacy. One of those packages, Let's say is, 'PackageA.dts'.
Now for the PackageA, we have versions of last couple of years (almost 11 versions we have for this package), recently in Test Environment (again, SQL 2008R2) we made Lot of changes to that Package and now we want bring that package from Test Env. to Production.
But a) we prefer not to 'open it in Prod then make all individual changes one by one' rather we just need to kind of overwrite/replace our existing Production Package b) also, we don't want to loose version history for the Existing PackageA.dts
in Production, so anytime we can rollback when required.
Any Idea if I can? [Please don't post non relevant answer like, convert DTS to SSIS. Sorry if I sound rude, really will appreciate if some one can try helping me.]
Regards, Avik M.Hi ArthurZ... "...No deletions, just import, it overrides the prod package" --- Is that the
case? If so, it could have resolved my issue I guess. But that's not happening...
If I don't delete and try to import same named package, I get below error::
TITLE: Object Explorer
DTS Package 'PackageA' already exists with a different ID in this category. (Microsoft OLE DB Provider for SQL Server)
Regards, Avik M.
EDIT: Also, I found another Post : dts-package-already-exists-with-different-id-in-this-category which
says, we need to basically delete the existing Package to import same named package. -- Just opposite of what you mentioned ArthurZ. So what's the conclusion?
I need to understand why the same package that I'm bringing from a different server is not just creating a new version if that package name already exists?
Any workaround Microsoft? -
Unable to import CRM Business Packager in the Portal
I have downloaded the Business Package for CRM, but it was in Zip file.
I was unable to import it in the Portal since EP6 format has to be in epa not zip?
Please advise.
AAHi,
CRM 4.0 Business package is available for EP 5.0 and above. When importing the business package do pay attention that you import a zip file that contains objects that are EP 5.0 version compatible such as files ending with the "PKG" extension. "EPA" extension is acceptable from EP 6.0 on.
The package content will be available at "migrated content" in your PCD, after the import process is done.
Regards,
Haguy -
Aperture 3.3 Import Speed from CF Card
Interesting import speed comparison vs Lightroom and Photo Mechanic from apertureexpert.com:
http://www.apertureexpert.com/tips/2012/6/19/import-browse-test-aperture-vs-ligh troom-vs-photo-mechanic.html
I am usually as impatient for an import to complete as I am for a lift to arrive, so happy to see that Aperture 3.3 looks to be at the fast end of what is possible.Eeish Stephen, that is not fun
Try sandisk rescue pro. as you are using Sandisks, you'll either have a tiny disk ( that wont fit into your laptop) or a serial number for the program and a link to download.
Disk utility.app, that may work for you as you are on a mac like I am
There are many free and paid for apps for mac and PC that allow you to do rescue files from disk.
I've formatted chips in my camera, prior to taking photos off several times, and after saying a few BAD WORDS taken that chip out , shot with another chip and once home I've used sandisk rescue pro and got all the photos back.
Stating the obvious, but dont reshoot using the suspect chip before trying to rescue, as that would over write of course.
Of course, if they are corrupted, then you may be using BAD WORDS as well.
I'd do a test with another card, and if that card is fine, repeat the test with the suspect card, and if that card breaks, use it as a coaster.
I hope that works for you.
Maybe you are looking for
-
Quicktime won't update, itunes won't open...having no luck :(
I'm getting an error message when I try to download the current quicktime. iTunes won't open without it. The error message is below: It says "Could not open key: HKEYLOCALMACHINE\Software\Classes\QuickTimePlayerLib.QuickTimePlayerApp\CLSID. Verify th
-
my ipad i locked since my IOS7 upgrade. I tried to restore it as explained at apple's support center but still it wont work..
-
Hi , I have automated master data which pushes member data from BW infoobject to BPC member sheet. Now i have a requirement to add 300 rows which are constants or fixed members and the constant valuess are available only in first 3 columns ie ID EVE
-
I have a 9i database exp file called test.dmp. I need to imp to 10.2 g database. I can import everything else but jobs. Following is the error message I got. I checked the 10.2 database, there is no jobs running on that database for that schema. Any
-
Can I use dial up for the new Macbook??? If not, what about the rural users? Suggestions?