ESS/XSS Web Dynpro SCA import in CMS to view/modify Web Dynpro Source Code

[Former Member]

I am having problems importing ESS/XSS Web Dynpro related SCA's into CMS.

Following steps were followed

1. Download following files from SAP service marketplace.

BPERP4ESS0_0-10003146.sca

ESS09_0-10002965.zip ( This file shows as SCA in the download page but download as with .zip)

PCUIGP009_0-20000568.zip ( This file shows as SCA in the download page but download as with .zip)

Question: Is this correct, did I get all I need? Do I need to download any more files?

2. Deployed above files using SDM.

3. Created a product in SLD and defined software component dependencies(SAP_BUILDT, SAP_JTECHS, SAP-JEE) I could define any of the above files(BPERP4ESS0_0-10003146, ESS09_0-10002965,PCUIGP009_0-20000568) as software dependencies as I could find in the software catlog.

Question: Should this files show up in the software catlog? If yes what should I do?

4. Created a track in CMS.

5. Added software components for development defined in the SLD. Above files doesn't show up under sap.com to be added as development component. I already copied BPERP4ESS0_0-10003146.sca, ESS09_0-10002965.zip,PCUIGP009_0-20000568.zip to D:\usr\sap\JTrans\CMS\inbox.

Question: How do I add this files to development components??

5. All other required Software Components(SAP_BUILDT, SAP_JTECHS) were automatically added when I added the development component.

What should I do so ESS09_0-10002965.zip,PCUIGP009_0-20000568 would show up under sap.com vendor component list??

Any help on this is greatly appericated.

Thanks!!

[cwcheong]

I agree that it could be dependancies (webdynpro) that is missing for my issue above with SAP_BUILDT / SAP_JTECHS / SAP-JEE.

1. I had problem to locate an URL to create this dependancies in help.sap.com. Could someone enlight me with reference URL / weblogs and etc ?

2. I saw some note that the SAP-JEE can be list out on the inactive DC and the note is able to create new DC (some dependancies) for SAP-JEE. But for my case, I don't get this option to right click and "create new DC" on SAP-JEE.

FYI. My J2EE version is on SPS14.

[Former Member]

Hi,

have a look at the following link:

http://help.sap.com/saphelp_nw04s/helpdata/en/ab/6760b8d7b64b6eb74052eb5bdf1405/frameset.htm

Gaurav

[cwcheong]

-I have done the steps mention in the first msg. Config. JDI and etc.

-followed JDI cook book to import ESS and MSS SCA into CMS.

-NW Dev. Studio now I can see ESS packages.

-right click and Create a new project from e.g. /ess/perid and completed ok.

-able to see some source code of ESS, view, model and etc.

-I would encounter problem when try to build or deploy the newly create project. e.g ess/perid

Error: classpath incomplete. com.sap....IWDController

Any advise is appreciated.

[Former Member]

Your project/DC is missing the dependencies for the Web Dynpro DCs.

[MarkusKlein]

Hello everybody,

i have some problems getting to see the code of the ESS sceanrios. I have done what is said at the JDI cookbook.

- Created a track

- Added SAP_ESS SC (including the SC dependencies) (Source and Archive!)

- Added the Runtime Systems.

- Checked in the files (took me only 10 mins of the SAP_ESS!)

- Imported all SC to Dev and Con (also took me hardly 10 mins for the SAP_ESS SC)

When i then add the Development Configuration at the NWDS i see the SCs but when i click on the SAP_ESS SC it doesnt open the tree with all the DCs....

I guess something went wrong somehow as the import of the ESS SC took barely 20 mins and not 7 hours!!!

[Former Member]

Hi Markus

Could you please check if the entries in the track configuration are valid like the url to the DTR and SLD. Also select the component and click view more details to obtain detailed info what is actually happening

Regards

Pran

[MarkusKlein]

Hello Pran,

here is a snippet from the SDM log (got it from the detail view)

Info:Starting Step SDM-deploy
Info:start deployment of archives to 
SDM:<server>
Info:The following archives will be deployed (on http:<server>:
Info:D:/usr/sap/JTrans/CMS/extract/200512161306450421_sap.com~SAP_ESS~MAIN_xss04VAL_C~20041209170316/DEPLOYARCHIVES/sap.com_ess~cn~bank.sda
Info:D:/usr/sap/JTrans/CMS/extract/200512161306450421_sap.com~SAP_ESS~MAIN_xss04VAL_C~20041209170316/DEPLOYARCHIVES/sap.com_ess~fr~addr.sda
Info:D:/usr/sap/JTrans/CMS/extract/200512161306450421_sap.com~SAP_ESS~MAIN_xss04VAL_C~20041209170316/DEPLOYARCHIVES/sap.com_ess~id~addr.sda
Info:D:/usr/sap/JTrans/CMS/extract/200512161306450421_sap.com~SAP_ESS~MAIN_xss04VAL_C~20041209170316/DEPLOYARCHIVES/sap.com_ess~ar~fam.sda
Info:D:/usr/sap/JTrans/CMS/extract/200512161306450421_sap.com~SAP_ESS~MAIN_xss04VAL_C~20041209170316/DEPLOYARCHIVES/sap.com_ess~cn~fam.sda
Info:D:/usr/sap/JTrans/CMS/extract/200512161306450421_sap.com~SAP_ESS~MAIN_xss04VAL_C~20041209170316/DEPLOYARCHIVES/sap.com_ess~fr~bank.sda
Info:D:/usr/sap/JTrans/CMS/extract/200512161306450421_sap.com~SAP_ESS~MAIN_xss04VAL_C~20041209170316/DEPLOYARCHIVES/sap.com_ess~cn~addr.sda
Info:D:/usr/sap/JTrans/CMS/extract/200512161306450421_sap.com~SAP_ESS~MAIN_xss04VAL_C~20041209170316/DEPLOYARCHIVES/sap.com_ess~at~fam.sda
Info:D:/usr/sap/JTrans/CMS/extract/200512161306450421_sap.com~SAP_ESS~MAIN_xss04VAL_C~20041209170316/DEPLOYARCHIVES/sap.com_ess~au~pdata.sda
Info:D:/usr/sap/JTrans/CMS/extract/200512161306450421_sap.com~SAP_ESS~MAIN_xss04VAL_C~20041209170316/DEPLOYARCHIVES/sap.com_ess~tra~trr.sda
Info:D:/usr/sap/JTrans/CMS/extract/200512161306450421_sap.com~SAP_ESS~MAIN_xss04VAL_C~20041209170316/DEPLOYARCHIVES/sap.com_ess~gb~fam.sda
Info:D:/usr/sap/JTrans/CMS/extract/200512161306450421_sap.com~SAP_ESS~MAIN_xss04VAL_C~20041209170316/DEPLOYARCHIVES/sap.com_ess~ch~addr.sda
Info:D:/usr/sap/JTrans/CMS/extract/200512161306450421_sap.com~SAP_ESS~MAIN_xss04VAL_C~20041209170316/DEPLOYARCHIVES/sap.com_ess~gb~bank.sda
Info:D:/usr/sap/JTrans/CMS/extract/200512161306450421_sap.com~SAP_ESS~MAIN_xss04VAL_C~20041209170316/DEPLOYARCHIVES/sap.com_ess~cn~pdata.sda
Info:D:/usr/sap/JTrans/CMS/extract/200512161306450421_sap.com~SAP_ESS~MAIN_xss04VAL_C~20041209170316/DEPLOYARCHIVES/sap.com_ess~my~pid.sda
Info:D:/usr/sap/JTrans/CMS/extract/200512161306450421_sap.com~SAP_ESS~MAIN_xss04VAL_C~20041209170316/DEPLOYARCHIVES/sap.com_ess~rep.sda
Info:D:/usr/sap/JTrans/CMS/extract/200512161306450421_sap.com~SAP_ESS~MAIN_xss04VAL_C~20041209170316/DEPLOYARCHIVES/sap.com_ess~ca~empeq.sda
Info:D:/usr/sap/JTrans/CMS/extract/200512161306450421_sap.com~SAP_ESS~MAIN_xss04VAL_C~20041209170316/DEPLOYARCHIVES/sap.com_ess~pt~pdata.sda
Info:D:/usr/sap/JTrans/CMS/extract/200512161306450421_sap.com~SAP_ESS~MAIN_xss04VAL_C~20041209170316/DEPLOYARCHIVES/sap.com_ess~th~pdata.sda
Info:D:/usr/sap/JTrans/CMS/extract/200512161306450421_sap.com~SAP_ESS~MAIN_xss04VAL_C~20041209170316/DEPLOYARCHIVES/sap.com_ess~lea.sda

... there way more sda listed on the log!

Info:Dec 16, 2005 2:08:17 PM  Info: ------------------ Starting deployment --------------------
Info:Dec 16, 2005 2:08:17 PM  Info: Loading selected archives...
Info:Dec 16, 2005 2:08:17 PM  Info: Loading archive 'D:usrsapER4DVEBMGS00SDMprogramtempsap.com_ess~cn~bank.sda'
Info:Dec 16, 2005 2:08:17 PM  Info: Loading archive 'D:usrsapER4DVEBMGS00SDMprogramtempsap.com_ess~fr~addr.sda'
Info:Dec 16, 2005 2:08:18 PM  Info: Loading archive 'D:usrsapER4DVEBMGS00SDMprogramtempsap.com_ess~id~addr.sda'
Info:Dec 16, 2005 2:08:18 PM  Info: Loading archive 'D:usrsapER4DVEBMGS00SDMprogramtempsap.com_ess~ar~fam.sda'
Info:Dec 16, 2005 2:08:18 PM  Info: Loading archive 'D:usrsapER4DVEBMGS00SDMprogramtempsap.com_ess~cn~fam.sda'
Info:Dec 16, 2005 2:08:18 PM  Info: Loading archive 'D:usrsapER4DVEBMGS00SDMprogramtempsap.com_ess~fr~bank.sda'
Info:Dec 16, 2005 2:08:19 PM  Info: Loading archive 'D:usrsapER4DVEBMGS00SDMprogramtempsap.com_ess~cn~addr.sda'
Info:Dec 16, 2005 2:08:19 PM  Info: Loading archive 'D:usrsapER4DVEBMGS00SDMprogramtempsap.com_ess~at~fam.sda'
Info:Dec 16, 2005 2:08:19 PM  Info: Loading archive 'D:usrsapER4DVEBMGS00SDMprogramtempsap.com_ess~au~pdata.sda'
Info:Dec 16, 2005 2:08:20 PM  Info: Loading archive 'D:usrsapER4DVEBMGS00SDMprogramtempsap.com_ess~tra~trr.sda'
Info:Dec 16, 2005 2:08:20 PM  Info: Loading archive 'D:usrsapER4DVEBMGS00SDMprogramtempsap.com_ess~gb~fam.sda'
Info:Dec 16, 2005 2:08:20 PM  Info: Loading archive 'D:usrsapER4DVEBMGS00SDMprogramtempsap.com_ess~ch~addr.sda'
Info:Dec 16, 2005 2:08:21 PM  Info: Loading archive 'D:usrsapER4DVEBMGS00SDMprogramtempsap.com_ess~rep.sda'
Info:Dec 16, 2005 2:08:22 PM  Info: Loading archive 'D:usrsapER4DVEBMGS00SDMprogramtempsap.com_ess~ca~empeq.sda'
Info:Dec 16, 2005 2:08:22 PM  Info: Loading archive 'D:usrsapER4DVEBMGS00SDMprogramtempsap.com_ess~pt~pdata.sda'
Info:Dec 16, 2005 2:08:24 PM  Info: Loading archive 'D:usrsapER4DVEBMGS00SDMprogramtempsap.com_ess~th~pdata.sda'

......

Info:Dec 16, 2005 2:09:10 PM  Info: Loading archive 'D:usrsapER4DVEBMGS00SDMprogramtempsap.com_ess~us~bank.sda'
Info:Dec 16, 2005 2:09:11 PM  Info: Loading archive 'D:usrsapER4DVEBMGS00SDMprogramtempsap.com_ess~kr~pdata.sda'
Info:Dec 16, 2005 2:09:11 PM  Info: Loading archive 'D:usrsapER4DVEBMGS00SDMprogramtempsap.com_ess~br~pdata.sda'
Info:Dec 16, 2005 2:09:11 PM  Info: Selected archives successfully loaded.
Info:Dec 16, 2005 2:09:14 PM  Info: Actions per selected component:
Info:Dec 16, 2005 2:09:14 PM  Info: Update: Selected development component 'ess/de/addr'/'sap.com'/'MAIN_xss04VAL_C'/'16849' updates currently deployed development component 'ess/de/addr'/'sap.com'/'MAIN_xss04VAL_C'/'16849'.
Info:Dec 16, 2005 2:09:14 PM  Info: Update: Selected development component 'ess/no/bank'/'sap.com'/'MAIN_xss04VAL_C'/'16824' updates currently deployed development component 'ess/no/bank'/'sap.com'/'MAIN_xss04VAL_C'/'16824'.
Info:Dec 16, 2005 2:09:14 PM  Info: Update: Selected development component 'ess/cn/addr'/'sap.com'/'MAIN_xss04VAL_C'/'16339' updates currently deployed development component 'ess/cn/addr'/'sap.com'/'MAIN_xss04VAL_C'/'16339'.
Info:Dec 16, 2005 2:09:14 PM  Info: Update: Selected development component 'ess/es/fam'/'sap.com'/'MAIN_xss04VAL_C'/'16163' updates currently deployed development component 'ess/es/fam'/'sap.com'/'MAIN_xss04VAL_C'/'16163'.
Info:Dec 16, 2005 2:09:14 PM  Info: Update: Selected development component 'ess/tra/tre'/'sap.com'/'MAIN_xss04VAL_C'/'16603' updates currently deployed development component 'ess/tra/tre'/'sap.com'/'MAIN_xss04VAL_C'/'16603'.
Info:Dec 16, 2005 2:09:14 PM  Info: Update: Selected development component 'ess/wtcor'/'sap.com'/'MAIN_xss04VAL_C'/'15289' updates currently deployed development component 'ess/wtcor'/'sap.com'/'MAIN_xss04VAL_C'/'15289'.
Info:Dec 16, 2005 2:09:14 PM  Info: Update: Selected development component 'ess/no/addr'/'sap.com'/'MAIN_xss04VAL_C'/'16475' updates currently deployed development component 'ess/no/addr'/'sap.com'/'MAIN_xss04VAL_C'/'16475'.
Info:Dec 16, 2005 2:09:14 PM  Info: Update: Selected development component 'ess/jp/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'15727' updates currently deployed development component 'ess/jp/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'15727'.
Info:Dec 16, 2005 2:09:14 PM  Info: Update: Selected development component 'ess/rem'/'sap.com'/'MAIN_xss04VAL_C'/'16571' updates currently deployed development component 'ess/rem'/'sap.com'/'MAIN_xss04VAL_C'/'16571'.
Info:Dec 16, 2005 2:09:14 PM  Info: Update: Selected development component 'ess/ph/fam'/'sap.com'/'MAIN_xss04VAL_C'/'16059' updates currently deployed development component 'ess/ph/fam'/'sap.com'/'MAIN_xss04VAL_C'/'16059'.
Info:Dec 16, 2005 2:09:14 PM  Info: Update: Selected development component 'ess/tw/bank'/'sap.com'/'MAIN_xss04VAL_C'/'16782' updates currently deployed development component 'ess/tw/bank'/'sap.com'/'MAIN_xss04VAL_C'/'16782'.

.....

Info:Dec 16, 2005 2:09:15 PM  Info: SDM configuration: Do not automatically start/stop J2EE Engine. Do not save current state of J2EE Engine now.
Info:Dec 16, 2005 2:09:15 PM  Info: Error handling strategy: OnErrorStop
Info:Dec 16, 2005 2:09:15 PM  Info: Update strategy: UpdateAllVersions
Info:Dec 16, 2005 2:09:15 PM  Info: Starting: Update: Selected development component 'ess/ben'/'sap.com'/'MAIN_xss04VAL_C'/'15307' updates currently deployed development component 'ess/ben'/'sap.com'/'MAIN_xss04VAL_C'/'15307'.
Info:Dec 16, 2005 2:09:15 PM  Info: SDA to be deployed: D:usrsapER4DVEBMGS00SDMrootoriginsap.comessbenMAIN_xss04VAL_C15307sap.com_ess~ben.sda
Info:Dec 16, 2005 2:09:15 PM  Info: Software type of SDA: J2EE
Info:Dec 16, 2005 2:09:15 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Info:Dec 16, 2005 2:09:20 PM  Info: Begin of log messages of the target system:
Info:05/12/16 14:09:20 -  ***********************************************************
Info:05/12/16 14:09:20 -  dm_msg_0044
Info:Dec 16, 2005 2:09:20 PM  Info: End of log messages of the target system.
Info:Dec 16, 2005 2:09:20 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Info:Dec 16, 2005 2:09:20 PM  Info: Finished successfully: development component 'ess/ben'/'sap.com'/'MAIN_xss04VAL_C'/'15307'
Info:Dec 16, 2005 2:09:21 PM  Info: Starting: Update: Selected development component 'ess/cat'/'sap.com'/'MAIN_xss04VAL_C'/'15253' updates currently deployed development component 'ess/cat'/'sap.com'/'MAIN_xss04VAL_C'/'15253'.
Info:Dec 16, 2005 2:09:21 PM  Info: SDA to be deployed: D:usrsapER4DVEBMGS00SDMrootoriginsap.comesscatMAIN_xss04VAL_C15253sap.com_ess~cat.sda
Info:Dec 16, 2005 2:09:21 PM  Info: Software type of SDA: J2EE
Info:Dec 16, 2005 2:09:21 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Info:Dec 16, 2005 2:09:23 PM  Info: Begin of log messages of the target system:
Info:05/12/16 14:09:22 -  ***********************************************************
Info:05/12/16 14:09:23 -  dm_msg_0044
Info:Dec 16, 2005 2:09:23 PM  Info: End of log messages of the target system.
Info:Dec 16, 2005 2:09:23 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Info:Dec 16, 2005 2:09:23 PM  Info: Finished successfully: development component 'ess/cat'/'sap.com'/'MAIN_xss04VAL_C'/'15253'
Info:Dec 16, 2005 2:09:23 PM  Info: Starting: Update: Selected development component 'ess/cod'/'sap.com'/'MAIN_xss04VAL_C'/'15235' updates currently deployed development component 'ess/cod'/'sap.com'/'MAIN_xss04VAL_C'/'15235'.
Info:Dec 16, 2005 2:09:23 PM  Info: SDA to be deployed: D:usrsapER4DVEBMGS00SDMrootoriginsap.comesscodMAIN_xss04VAL_C15235sap.com_ess~cod.sda
Info:Dec 16, 2005 2:09:23 PM  Info: Software type of SDA: J2EE
Info:Dec 16, 2005 2:09:23 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Info:Dec 16, 2005 2:09:24 PM  Info: Begin of log messages of the target system:
Info:05/12/16 14:09:24 -  ***********************************************************
Info:05/12/16 14:09:24 -  dm_msg_0044
Info:Dec 16, 2005 2:09:24 PM  Info: End of log messages of the target system.
Info:Dec 16, 2005 2:09:24 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Info:Dec 16, 2005 2:09:24 PM  Info: Finished successfully: development component 'ess/cod'/'sap.com'/'MAIN_xss04VAL_C'/'15235'
Info:Dec 16, 2005 2:09:25 PM  Info: Starting: Update: Selected development component 'ess/lea'/'sap.com'/'MAIN_xss04VAL_C'/'15471' updates currently deployed development component 'ess/lea'/'sap.com'/'MAIN_xss04VAL_C'/'15471'.
Info:Dec 16, 2005 2:09:25 PM  Info: SDA to be deployed: D:usrsapER4DVEBMGS00SDMrootoriginsap.comessleaMAIN_xss04VAL_C15471sap.com_ess~lea.sda
Info:Dec 16, 2005 2:09:25 PM  Info: Software type of SDA: J2EE
Info:Dec 16, 2005 2:09:25 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Info:Dec 16, 2005 2:09:28 PM  Info: Begin of log messages of the target system:
Info:05/12/16 14:09:28 -  ***********************************************************

.......

Info:05/12/16 14:15:01 -  dm_msg_0044
Info:Dec 16, 2005 2:15:01 PM  Info: End of log messages of the target system.
Info:Dec 16, 2005 2:15:01 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Info:Dec 16, 2005 2:15:01 PM  Info: Finished successfully: development component 'ess/za/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'15835'
Info:Dec 16, 2005 2:15:01 PM  Info: SDM configuration: Do not automatically start/stop J2EE Engine. Do not restore state of J2EE Engine now.
Info:Dec 16, 2005 2:15:01 PM  Info: --------------- Deployment was successful -----------------
Info:end of log received from SDM
Info:RC of deployment: 0
Info:Step SDM-deploy ended with result 'success' 

If you check the limeline it takes rather 8 mins

regards,

Markus

[Former Member]

Hi,

Have you imported the required/dependent SC's also like the SAP JTECH & etc..These also need to be checked in.

Regards

Gaurav

[cwcheong]

Hi Markus Klein,

You issue of unable to open the tree is bcoz I guess your SPS is lower then sps13 (J2EE, JDI). You will need to patch is up to SPS13 or higher and recreate a new Dev Track.

Hope this helps bcoz I encountered the same issue on SPS9.

Steven Cheong

[MarkusKlein]

Hello Steven,

you could be right, coz im still SP9.

Thanks!

regards

Markus

[former_member183805]

Hi Phani,

Please take a look at the document "JDI Cookbook for ESS" attached with Note 872892 - it addresses the questions you have asked.

Regards,

Manohar

[Former Member]

Hi,

Please let me know how you solved your problem of not getting the SAP_ESS components in the Add SC's section of Tracks.

Please see this:

Regards

Gaurav Gandhi

Message was edited by: Gaurav Gandhi

[Former Member]

Hi Manohar,

Excellent link & Help!!

Thanks for pointing me to the right resource, Note and JDI Cookbook for XSS was of great help.

I still have few issues; I am having hard time importing SAP_ESS.sca. As per the cookbook it's going to take several hours.

Question: Do you know how long it would take?

My System Config is 2GiG RAM with 2GIG clock speed.

After 1 1/2 hours the CMS import page come out with a page error, when I go back to the page it has status of "Import running".

Question: Should I assume the process is still running as I can see some hard disk activity on the system and at the same time I see increase/decrease in the DB connections (Visual Administrator).

Question: Are there any config settings on the system that needs to performed prior to running this import like

DB Space, JVM Heap Size,..?

Any help on this is greatly appreciated.

Thanks

[Former Member]

Hi Gaurav,

Please take a look at the above mentioned note & JDI cookbook by Manohar, you should not have any problems, let me know if you have any problems adding SAP_ESS in the Add SC's section.

[Former Member]

Hi Phani,

I was following the CookBook.

But as mentioned in my thread and here also, i am not able to see the SAP_ESS inside sap.com while adding SC's to the track.

Plese let me know what is going wrong.

Regards

Gaurav Gandhi

Message was edited by: Gaurav Gandhi

[sid-desh]

Hi Phani,

These are some of the important notes which you can look at and determine the optimum configuration for your system.

848708 - Oracle Database Configuration for NWDI server

858084 - First time IMPORT operation is very slow

828628 - CMS import fails with "Internal Server Error"

737368 - Hardware requirements of Java Development

Infrastructure

840524 - NWDI server configuration: J2EE engine/Java VM

parameters

754143 - CMS remarks/restrictions

Regards

Sidharth

[Former Member]

Finally I could get this working and import took 6 1/2 hours to complete.

Import was running in the background with CMS page error.

[Former Member]

Hi Gaurav,

Please follow Sidharth advice's on updating your SLD. It is a prerequisite prior to creating a track as mentioned in JDI Cookbook.

I just don't want to repeat again so take a look at Sidharth reply in your other thread and on top of it pay attention to SAP Note 669669.

SLD update takes a while (I believe it took me 3 hours all together) and you may come across couple of errors but that's "OK" stick with the Note.

Below is some watch-out list while importing ESS.SCA based on my experience & pain.

1. Make sure you have sufficient JDBC connections:

In my case SAP DB: 50 adjust for your situation

2. Add 2-3 gig of DB space, this DB intense operation.

3. Add DB log space too if you have DB log turned ON

3. Make sure you Server JVM heap size is 1 Gig.

4. Plan for 7 hours import for just ESS.sca only. My System config is 2 GIG RAM and it took me 6 ½ hours. Page error is “OK” after a while as the importing process is running background. Close the page and log back into the CMS to see the status “Import Running”. Let it run through still you see status of “Import Finished”. Another way to check the process run is to look for hard disk activity and DB activity.

5. Try to run import for each and every SCA rather than running them together, so you know the status.

6. Make sure you have plenty of OS VM & hard disc space to run this process smoothly.

I guess that's it and good luck. Let us know how it went through.

Cheers!!

[Former Member]

Hi Phani,

Firstly, thanx again..

but i would suggest plz reply to so that i can also reward points for the help that you are offering me.

Actually i am not a Pure BASIS guy and i was not involved in the installation of the JDI server here, thats why i didnt knew abt all these details.

I had to ask a basis guy to sit with me to read your reply

1) As per the note 669669, i have downloaded the 3 ZIP files from service.sap -> SAP MASTER DATA FOR SLD 2.0 -> #OS independent.

2) We dont have SAP DB but an Oracle installation so JDBC conn are not required -> this is what my basis guy told me.

3) other points are ok..we will take care of them.

But i have a few questions:

1) As per the note, i have downloaded and will be installing SAP MASTER DATA FOR SLD 2.0 but why do i need 2.0? bcos i checked in my SLD Admin -> Details. The server tab shows SLD Version: 2.1.3 & the Data tab shows

Required SAP CIM Model Version: 1.3.26

CR Content Version (sld/active): SAP_CR 1.0

Other Import Content Versions (sld/active): No other imports detected

Do i really need 2.0 or some other previous verions?

2) After all the above imports are finished (3 zip files). Do i need to restart the enjine?

3) After import if zip files, how do i start again with domainid and tracks etc. will the previous data be lost?

4) And after this how do i import the ESS SCA's? I hope i will have to use the same SCA's as i was using earlier and deploy them through SDM only.Last time when i deployed ess.sca, it took around 1 hr and others around 10 mins so my imports through SDM were over in 1.5 hr.

please advise..

Right now this all process is looking amazing to me bcoz i am able to see many components in my software catalogue but not the one which i need and which i deployed through SDM...?

Those were a long list of question & answers..

Let me know if i can contact you by anyother means of communication (phone or email id). Where are u located?

Regards

Gaurav Gandhi

[Former Member]

Hi Gaurav,

I am not a BASIS guy too; I am Java developer and also do J2EE Engine administration activities.

From the above First list of questions

1. Based on your reply, you would need both SAP MASTER DATA FOR SLD 1.0 & 2.0. Start applying SLD 1.0 first and later apply 2.0 and use the note as the guideline.

2. What ever Database you use, you should need a large JDBC connection pool to perform this process. Little background on this, J2EE engine uses this DB (Oracle or any other) to store system metadata, so you need to set this config, it is important. You could do this through Visual Administrator.

3. Glad to hear that...

From the above Second list of questions

1. Based on your reply, you would need both SAP MASTER DATA FOR SLD 1.0 & 2.0. Start applying SLD 1.0 first and later apply 2.0 and use the note as the guideline. I am not sure if you guys did an initial SLD update or not. You can apply 1.0 and then apply 2.0. You can take a backup copy by exporting the SLD prior to applying the import.

2. Don't have to restart the engine after SLD Update/import.

3. SLD import/update is an update process that would update your software catalog with new SAP components, so you should not loose any of your custom development products/components.

4. If you have already deployed ESS SCA's through SDM, you don't have redeploy them, they can stay as is. You are correct this takes around an hour. This deployment is for the J2EE Engine but you need these components for custom development, so you use CMS to do so and use the JDI cookbook. This process takes 7 hours.

SDM is used J2EE component deployment where as CMS is used for JDI deployment. These are two different processes. Seems you are done with SDM, all info in this thread is about CMS.

Once you update your SLD and ready to create development track for ESS as per JDI Book, prior to creating the track, you need to update your CMS by clicking on update CMS under Landscape Configurator --> Track Data --> Update CMS. Now you should see SAP_ESS component under sap.com vendor while Adding SC's

From my experience & pain -- > Don't rush!! Think through the process completely and write down the steps and come up with a check list for each step like: Is my system ready for this step to run? Do I have enough hard space, DB space, memory, time to complete the step?

I am OK without points, I am replying to this thread, just to keep all the information together. Here is my e-mail address in case sri_edala@yahoo.com, but I prefer to communicate through this forum as it could be of help to others too and someone could add something that we both might be missing. I am located in US.

Good luck with your import!

Cheers!!

[Former Member]

Hi Phani,

Thanx for your generosity and modesty.

We are now planning for a complete re-check of the JDI installation along with the other points which you have mentioned.

But one thing abt which i want some more explanation:

Abt the point no. 4:

<i>4. ................This deployment is for the J2EE Engine but you need these components for custom development, so you use CMS to do so and use the JDI cookbook. This process takes 7 hours. </i>

- Didnt understood much..How to use CMS for uploading SCA's?are u refering to the check-in activity? But check-in comes after track creation..Can u plz explain?

<i>SDM is used J2EE component deployment where as CMS is used for JDI deployment. These are two different processes. Seems you are done with SDM, all info in this thread is about CMS.</i>

- Do u mean that if i have to implemented the ESS Web Dynpro in portal, i should use SDM deployement but if i want to change code i have to use CMS deployment.? and my CMS XSS components will not be available in portal and SDM XSS components will not be available in CMS?

But through SDM Deployment, i am able to see SC's in SLD(system landscape)

didnt understood much here also...Do u have some docs or links for these?

Regards

Gaurav Gandhi

[sid-desh]

Hi Gaurav,

I will try to explain what Phani has said.

The sca files are deployed using SDM so that the classes present inside the sca'a are available at runtime to your applications.

However you also need these classes during the design and build time. For this you define a usage dependency to the software components in your custom software components. Then the same thing reflects in the TRACK.

However this is still not enough. You also need to checkin the same SCA files so that they are then present in your Dev config which you import into NDS. This way you ensure that these are present during the design and build time.

Hope this helps in clearing some doubts.

Regards

Sidharth

[Former Member]

Hi,

1. Its ok if you get .zip file instead of the .SCA file.

2. there is no need to deploy these file directly via SDM. if you use track then you can deply these file using tracks.