Problem SLD transports and Communication Channel setup

[Former Member]

Questions naming standards for system (SC software Component, TS, BS bus system) in SLD to handle transport/migration from XI Dev, XI QA, XI Prod.

Background system landscape: Three XI boxes with SLD on each box. XI 3.0 XID(Dev), XIQ(QA), XIP(Prod). R/3: GDC(dev),GCQ(QA),GCP(Prod).

1. Any white papers on XI naming standards for objects in IR and ID? Ideas from other companies or Sap in this area? . Also SLD object names to address transport/migration for IR and ID objects from XI Dev, QA, and Prod Systems ?

2. What should R/3(Sap) be named as Software Component in SLD for transport from Dev,QA, Prod? Should R/3 be named "SAP" in each SLD?

3. After setup communication channel in XID (dev) box, can it be transported to XIQ (QA) box? Once transported, Do you have to change logon userid, pswd, sap system on XIQ server then later in Prod once transported as well?

Appreciate the recommendations.

[Former Member · Accepted solution]

There are no naming standards as such.

I stick with the simple rule of: memorable, consistant and understandable.

[michael_muehlberg]

Hello William,

transport of communication channels:

Passwords are never exported and therefore not imported in a target system. They aren't also going to be overwritten there.

All other data are (usually) exported and imported BUT they won't be overwritten in a target system IF they were changed there.

So, you transport your channel and edit the correct values that are valid for your target system, e.g. some host names. Then the next transport of the same channel won't overwrite the edited values, e.g. your host names.

Ciao, Michael