Instance number strategy

[Former Member]

I am interested in developing an instance numbering strategy and would appreciate feedback from anyone who has developed a tested numbering scheme.

I work at a large installation with dozens of SAP instances including CI, app servers and Web Dispatchers. Since most of the these systems are on separate servers or virtual containers, there has been no conflict with ports if the system numbers are the same. Going forward, we are facing installation of additional DEV and QAS landscapes and I want to choose instance numbers wisely since they aren't easy to change.

Also, Adaptive Computing provides the ability to move instances to different hosts easily but only if the the instance numbers are unique to prevent port conflicts.

Are there any other technical considerations beside duplicate ports when choosing system numbers?

I would appreciate any feedback about your number rules or polices.

Keith

[Former Member]

I do not know how much of this will help you, but this is the strategy that we follow

We have 150+ sap systems running on different servers without any virtualization, In come cases we have as many as 15 instances (dailog, CI etc) on same server, so the port numbers have to be different for all the systems to work

This is what we follow

1) Each SAP system will have a different number uniqiue.g 01, 02 , 03 etc ( All instances of the system like dialog, CI should use the same number) . In cases where SCS comes into picture two numbers get assgined to the system

2) Production systems have a different number range (as they are on a seperate set of servers)

3) One physical server will not host more than more instance of the same system

4) CI and dialog instances are always on seperate sets of servers

5) Before installing a new system the system number has to be assigned from a common system number repository.

6) When the system gets deleted the system number is cleared for re-assginment in the system nuber repository