SAP Note 821904 - Separating SCS instances for ABAP and J2EE

Component : Installation mySAP.com with DB2 UDB for OS/390, z/OS -

Solution : https://service.sap.com/sap/support/notes/821904 (SAP Service marketplace login required)

Summary :
This SAP Note outlines the process for segregating SCS instances for ABAP and J2EE systems onto a separate host. It discusses the deployment on a dedicated SCS host, applicable for both ABAP-only and J2EE-only systems, as well as mixed ABAP and J2EE scenarios where each receives an independent SCS instance. The note provides detailed steps including preparations, necessary adjustments, and considerations for UNIX and z/OS platforms. Additionally, it addresses prerequisites for running separate SCS instances, like ensuring that no other server listens on predetermined SCS ports, and specifies the use of the system copy method for implementation. It also includes guidance on requesting new SAP licenses post-reconfiguration and precautions to preserve system integrity before undertaking the changes.

Key words :
12<a-ino>   13<a-ino>   14<a-ino>   15<a-ino>   32<a-ino>   33<a-ino>   39<a-ino>   81<a-ino>   32<j-ino>  33<j-ino>  39<j-ino>  81<j-ino>, filename =                                \        /usr/sap/<sid>/sys/profile/<sid>_scs<jscs_ino>_<scshost>  - cluster-data --> global server configuration                --> managers                --> cluster manager               change, filename =                                \        /usr/sap/<sid>/sys/profile/<sid>_scs<jscs_ino>_<scshost>  - cluster-data --> instance_idxxxxx               change, ### 640###abap_ms_port          = 36${ascs_ino}#j2ee_ms_port          = 36${jscs_ino}### 700###abap_ms_port          = 36${ascs_ino}#j2ee_ms_port          = 0#abap_ms_port_internal = 39${ascs_ino}#j2ee_ms_port_internal = 39${jscs_ino}# operation systems, ### 640###abap_ms_port          = 36${ascs_ino}#j2ee_ms_port          = 36${jscs_ino}### 700###abap_ms_port          = 36${ascs_ino}#j2ee_ms_port          = 0#abap_ms_port_internal = 39${ascs_ino}#j2ee_ms_port_internal = 39${jscs_ino}## start, sh  - cluster-data --> global dispatcher configuration                --> managers                --> cluster manager               change, pfl  - cluster-data --> global dispatcher configuration                --> managers                --> locking manager               change, pfl  - cluster-data --> global server configuration                --> managers                --> locking manager               change, execute load tests    cluster --> <sid>   --> server# --> services            --> message info    --> runtime, set#abap_kernel_release  = 640#j2ee_kernel_release  = 640sapsid              = d6zci_ino              = 96ci_instance_name     = dvebmgs${ci_ino}# instance number

Related Notes :

1011190MSCS:Splitting the Central Instance After Upgrade to 7.0/7.1
951910NW2004s High Availability Usage Type PI
875157Syslog: Central syslog only shows the main instance
853510Release Restr.: Usage Type PI of SAP NetWeaver 2004s
831812Config Tool shows incorrect parameters after System Copy
809477startsap/stopsap for SAP WebAs 640, 700, 701, 710, 711, 720
757692Changing the hostname for J2EE Engine 6.40/7.0 installation
751873Problem analysis during the HTTP load distribution
569996High availability and automation solution for DB2 on z/OS
538081High-availability SAPLICENSE
524816Standalone enqueue server
181543License key for high availability environment