A JDI development track has to be updated to the newest SP. To achieve this the SCA files of the new SP have to be imported into the new track. These files are delivered with each new SP by the SAP.
There are two solutions for this issue. Solution 1 is the default one and works almost at all times.
But there are situation when this does not work. I encountered such a situation after the NWDI was updated to a higher SP but I haven´t checked in and activated all my activities (maybe this was a mischange)
Because solution 1 should be quite clear and is well documented this paper mainly describes solution 2, the dirty way.
Solution 2 can also be chosen if you don´t have access to the JTrans/CMS/inbox directory at the server and your administrator is too busy for the next weeks to upload the SCA files there.
Solution 1: CMS Web UI
Solution 1 is the recommended way to update the SCAs. The files must be located in JTrans/CMS/inbox. Then they are checked into the track using the CMS Web UI. Finally they are imported into the development and consolidation system (buildspace).
Solution 2: CBS command line tool
Make iaik_jce.jar available
Set env. variable SAPDEVSTUDIOHOME
The environment variable
must be set to the eclipse folder of the NWDS installation.
e.g.: set SAPDEVSTUDIOHOME=c:\programme\sap\jdt\eclipse
You can also add this line to the file cbstool_nw.bat. Then you can´t forget setting the variable the next time.
Starting the command line tool
The CBS command line tool is started by calling
After it is started it prompts :cbs>
Connecting to CBS Server
Download a SCA file
Test the Upload(s)
To test if your upload(s) was/were successfull you can compare the number of DCs in the appropriate compartment(s) before and after the upload. Usually the number grows with each SP.
In CMS Web UI you have the possibility to check the system state. If you upload the SCA files using CBS command line tool you will still see the old SP number here.
Leave the command line tool
To leave the command line tool and return to DOS command simply type exit at the CBS prompt.
Help for the command line tool: