Default Extended SID Handling
During the setup of your SAP Focused Run system, the Simple System Integration (SSI) SA38 report P_SSI_PREPARATION must be used. The SAP Focused Run Master Guide recommends marking the option Enable Default Extended SID as checked.
Marking the option Enable Default Extended SID Handling as checked, causes extended SID changes at following events:
- Whenever a technical system of the following types is initially registered in the LMDB, the default LMDB extended SID calculation is overridden by SSI:
- Application Server ABAP
- Application Server Java
- Introscope Enterprise Manager (Cluster)
- Introscope Enterprise Manager (Standalone)
- SAP HANA Database
- SAP liveCache
- SAP NetWeaver Master Data Management Server
- SAP Web Dispatcher
During registration in the LMDB, the extended SID of such technical system is set to <SID><CID> (where <SID> stands for: system ID, and <CID> stands for: customer ID).
- Starting with SAP Focused Run 5.0 SP00 the generation of HANA Databases Extended SIDs is based on the LMDB properties:
Short SID: <SID> = dbName. If empty, <SID> = SAPSystemName
Customer ID: <CID> (retrieved from LMDB Namespace into which the Hana Database is registered)
SystemDB/TenantDB: 'S' or 'T' based on LMDB property: IsSystemDB
Replication Node number: x based on LMDB property: ReplicationSiteName (empty vs non-empty)
For a given HANA installation, the registration of the different HANA DB System DB, Tenant DB and their replication nodes, is now leading to the following default ext SID proposals:
<SID><CID>SD for the Hana System DB
<SID><CID>TD for the Hana Tenant
<SID><CID>Sx with x ranging from 1 to 9 for the Hana System DB replication nodes
<SID><CID>Tx with x ranging from 1 to 9 for the Hana Tenant replication nodes
In case suffix range 1-9 is exhausted, the extended SIDs generated by LMDB will fall back to <SID>, <SID00001>, <SID00002> ...
- Later, whenever SSI is executed, the extended SIDs of technical systems of type Database System (databases, excluding SAP HANA Databases) are changed if needed. See section Database Extended SID Renaming below. SSI execution may be triggered manually, via Web Service, or due to LMDB events. The extended SIDs of other system types remain unchanged during SSI execution.
If you have enabled option Enable Default Extended SID Handling, we recommend that you no longer perform manual LMDB extended SID changes for technical systems of type Database System. Those changes may get reverted when running SSI.
If you perform a manual extended SID change for a technical system or database, the LMDB event handling implemented by SSI, will automatically trigger a reconfiguration for the affected technical system or database, thus ensuring configuration-consistency.
Disabling the option will not perform any of the above-mentioned extended SID changes anymore (from the point of disabling onward). Only the default LMDB extended SID calculation will be performed, whenever technical systems or databases are initially registered in the LMDB. This will result in extended SIDs such as JAV, JAV00001, JAV00002.