Problem Importing Workspace to another Distributed DTR

[Former Member]

I am attempting to export a Workspace from our own DTR to a remote Development Partner, so that they can develop a project on their own DTR external to our company.

I have followed the steps below but am receiving errors at the IMPORT stage.

1) Created a product and added a component in the SLD.

2) Created a development TRACK in the CMS and added the required build libraries.

3) Downloaded the Development configuration from the DTR to NWDS. I have then added a Web Module and EAR module and begun some coding which I have checked in and activated.

4) Then using the console DTR client I have closed the workspace.

closews -w /..... -c "Closing to export"

5) Then I have exported the workspace

export /...... -f workspaceexportfile - r 12345678 -m 12

(where 12345678 would be the repository id of the DTR I am trying to export to)

6) I have then tried to import the workspace into the other DTR using,

import -w /.... -c "Importing the workspace"

But when I run this command I get the following error

******************************************************

Error importing: Import failed. Not found "/nonvresbyid/522cdd78f85911d9a3660002557b0840"

******************************************************

Does anyone know what this error means? Or why the import is failing.

Thanks

[former_member183805]

Hi Ciaran,

Exporting a workspace is not the correct way to achieve your goal. Ideally, what is needed is a possibility to relocate a whole track, but this is currently not possible.

So what you need to do is to assemble the SC you have developed, and ship the resulting SCA to your development partner, who will then have to import this SCA file into a track he/she has created.

You additionally have to export the SLD content so that your partner also gets the Product and SC you have defined (which can then be used to populate the track created at the partner location).

By doing this, you are not exactly relocating the track, because you can continue using the source track (in your landscape)since this track will contain different workspaces from the one at your partner location. If you do not wish to use this track, you can disable permissions for this track (otherwise, you can split the development between the two locations, and periodically transport SCAs in both directions to keep both repositories in sync).

If you follow this strategy of delivering your SCA to a partner for development, then you must keep in mind the following points:

1)In your track, the "Package Type" of the SC must be "Source"

2) Your CMS domain must be of four characters. This is explained here: http://help.sap.com/saphelp_nw04/helpdata/en/52/784641db92491de10000000a155106/content.htm

Regards,

Manohar

[Former Member]

I found how to export a product/sfotware catalog in the SLD. This action creates a .zip file. But how can you import that .zip file into the destination system?

[sid-desh]

Hi Deborah,

Just go to Administration -> Import in SLD and there you can browse to the file and import it.

Regards

Sidharth

[Former Member]

Thanks for the reply Sidharth.

I found how to import the product into the SLD, import CIM link.

Just to confirm, the steps to have 2 different servers, that are not connected, with the same SCA are the following:

1- Export the Software Catalog/Product of the origin SLD, creating a .zip file

2- Import the .zip file in the destiny SLD, through the SLD Admin -> Import Content

3- Create a new track in the destiny server in the CMS Landscape configurator, adding a SC from the product/software catalog imported through the SLD

4- Create a .sca with the source and archive in the origin server

5- Put the .sca un the inbox folder of the JTrans\CMS\inbox in the destiny

5- In the CMS transport studio in the destiny, check-in the .sca.

In this way, I would be able to have the same source, and be able to edit it.

are these the correct steps?

thanks in advance

Deborah-

[sid-desh]

Hi Deborah,

There seems to something missing here. I just thought you wanted to import the SLD contents of one into another.

I would request you to please let us know your requirement in detail, so that you can get good suggestions.

Regards

Sidharth

[Former Member]

Sidharth,

I'd need to transfer a SCA from two different environments that are not connected, and be able to edit the source in the destiny environment.

So, as Manohar explained earlier in his post, I'd need to export/import the SLD content to "copy" the product/Software catalaog, and then transfer the .SCA to the destiny system, so I can edit the source in the destinty too.

But I didnt understand how to import the .sca. Should I create a new track, create a SC and the new track, checkin the SC, or all of the above?

Do you think the steps that I explained earlier resolved this problem?

thanks again!

[sid-desh]

Hi Deborah,

As Manohar has explained you will have to import the SLD contents first in the target and then create a new track in the target CMS. Add the imported SC in the track and now check-in the sca file which you have as a result of the assemble step.

Just make sure that in the source files also in the sca file. This has been explained by Manohar.

Regards

Sidharth

[former_member189501]

I would like to add this info, regaring the CMS domain ID of 4 char that should be necessary.

The OSS told me the four letter domain is needed only if an ISV (independent software vendor) is going to modify an SAP software, deliver the modifiied

software to the customer and allow the customer to further modify the sources.

In all the others cases you can work with the usual 3 digit CMS Domain ID.

(By the way I tried to change the CMS Domain ID but it seems really not possible. Also to re-deploy the JDI seems to me not usefull -i did not try to do that- because this informatin is written somewhere into the SLD database. THere is the possibility after the re-deploy of the JDI this information is still present ?

regards

[Former Member]

Hi,

can anyone please let me know the steps to create the SCA file.

Divakar

[Former Member]

Thanks for the links. However, i have already read both of these and then implemented the import according to the details defined for the DTR Administartor.

My issue is that the actual technical level import is not working.

Any ideas on thecause of the error message

******************************************************

Error importing: Import failed. Not found "/nonvresbyid/522cdd78f85911d9a3660002557b0840"

******************************************************

Thanks

[Former Member]

Hi Check this link which may help you

http://help.sap.com/saphelp_nw04/helpdata/en/38/33eb9c3e1fe2409a9eba8246b933ca/frameset.htm

<b>Administration of the Distributed Development</b>

Regards,

RK

[Former Member]

Link fix: http://help.sap.com/saphelp_nw04/helpdata/en/cd/c22c6d7135c6498ac9e1be5fcf970a/frameset.htm