Skip to Content
avatar image
Former Member

Checkin own SCAs into a track

Hello,

i had developed Web Dynpro Applications using the JDI. The applications got deployed to Server "SERV1". We then moved our JDI as well as the SLD to a new server. So now i want to check in the already developed Web Dynpros into the new JDI. I do have the SCAs copied to the respective inbox folder of the new JDI Server, but unfortunatelly the SCAs doesnt show up at the checkin tab. The JDI is running on a WAS 6.40 SP16. Im sure im missing something.

As we moved to a new SLD as well there isnt a Product / SC of the respective Application yet. Maybe thats why it doesnt find the SCA at the checkin? Do i have to deploy the SCA using the SDM, even tho it is already running on the server ("SERV1")?

regards,

Markus

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    May 07, 2006 at 08:28 AM

    The SCA needs to have a specific format in order to have it picked up by the CMS Transport Studio. Compare the format of your SCA with the 3 base SCA's to check this. The SCA that you have is probably a deployment SCA and not a JDI build SCA.

    Deploying using SDM will not get the Web Dynpro's into your new JDI configuration.

    Until SAP comes with an official JDI migration guide I'm afraid you'll have to move everything by hand: Set up the SLD, create your Web Dynpro DCs in NWDS and copy the contents of the DCs from the old JDI as described in the SAP Note for moving a DC to a different SC, etc.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      You can have a look at the export01.xml file in the exported zip to check what's in there and find out if it may overwrite something important... This is not a funny task though... This warning might be caused by the fact that you already tried to define the Product and SC in the SLD.

  • avatar image
    Former Member
    Feb 19, 2007 at 05:45 PM

    Hi Markus,

    We are also facing similiar problem with our Custom SCA files when we migrate from old JDI to new JDI. Have you been able to find out the solution?

    Thanks,

    Jojo

    Add comment
    10|10000 characters needed characters exceeded