view · edit · history · print

Software Logistics (ADM325) Notes

Instructor : Markus Sorensen

If there is NO DOMAIN.CFG in /usr/sap/trans/bin and you enter STMS (client 000) then this system becomes the domain controller.

Q. Can you move a domain controller by using a backup domain controller (eg. in case the domain controller system will be take out-of-service, permanently). => This is not nessecary.

Put the domain controller on a stable system, like the production system. You can also use the DEV or QAS system (in classical 3 way system). Never use a sandbox or training system for this purpose. If you are using DEV as a DC you could define production as backup DC. Moving the DC functionality is possile withouth destroing the transport routes.

Splitting systems from 1 transport group to 2 transport groups can be done by duplicating the filesystems and changing in

  • STMS - system overview - dbl click - transport tool - TRANSDIR
  • RZ10 - DIRTRANS

Cross client customizing are always workbench requests.

Local request is a packages with no transport layer assigned

On older systems Packages where named development classes.

SAP Reference IMG (see tr>SPRO)

tp locksys

The highest return code for ABAP program problems during successful tp is 8. Higher then 8 are failed tp.

J2EE development flow

 
[IDE] "develop"
  V   "store"
[DTR] 
  V   "deploy (SDM)"
[DEV] "release"
  V   "transort"
[...]

For Java development we often have a large number of servers:

  • 1 or 2 systems for DTR (+CMS) and CBS (+CMS)
  • SLD
  • minimum 4 system landscape (DEV,CONS,TEST,PROD)

When applying J2EE patches you need to do it all (ABAP->J2...) in a quite complex sequence but this is (or will be in the future) handled by the JSPM using Netweaver Administrator and SLD.

http=5xx00 telnet=5xx08 P=5xx04

SLD can be a landscape OR name server. The SLD software is installed on all Netweaver2004s system with J2EE but not used. The SLD landscape system sould be a sepperate centralized server. A second SLD nameserver is required but can often be combined with the CMS system.

Combining ABAP(3) and J2EE(4) landscapes:

 
ABAP J2EE
==== ====
DEV  DEV + CONS
QAS  TEST
PRD  PROD

Netweaver Administrator

 http://<host>:<50000>/nwa

Java Visual Administrator

 /usr/sap/<SID>/<instance>/j2ee/admin/go.sh

CMS webinterface

 http://<jdihost>:<52000>/webdynpro/dispatcher/sap.com/tc~SL~CMS~WebUI/Cms

SLD webinterface

 http://<jdihost>:<52000>/sld

J2EE Visual Administrator

 local application (SAP VisualAdmin\...\start.vsb)

SAP NWDS (Netweaver Developer Studio)

 local application (SAP\IDE\...\Saplde.exe -vm ... -data ...)

SDM (Software Deployment/Delivery Manager)

 http://<server>:5xx18/

JDI = SAP Netweaver Java Development Infrastructure (The WebAS system where usually DTR and SLD nameservice runs)

CBS = Central Build System

Get and work on project from DTR, create Central Build and store to CBS.

When the SDM is open no other updates can be done (by devellopers). The SDM is running on the DEV and every other system in the landscape.

admin · attr · attach · edit · history · print
Page last modified on June 15, 2007, at 06:15 AM