Lodbrok.be
R/3Ent. R/3Ent. ECC5 ECC6
ERP2004 ERP6.0 CE7.1 CE7.2
Netw Netw04 Netw04s
4.7x110 4.7x200 Netw05 NW7EHP1 NW7EHP2
NW7.0 NW7.01 NW7.1 NW7.2 NW7.3
======== ========= ========= ======= ======= ======= ======= ======= =======
BASIS / ABA 6.20 6.20SP25+ 6.40 7.00 7.01 7.10 7.20
EXTENSION SET 1.10 2.0 5.0 6.0
APPLICATION LAYER 4.7 4.7 5.0 6.0
Note on versioning: SAP ERP 2005 on Netweaver 2004s (v7.00) contains ECC6.
BW and XI also use the ICM. MCOD on Informix will not be available. Communication between ICM and ABAP dispatcher uses MPI (Memory Pipes) to extended memory and RFC to disp+work. Do not use MCOD to mix DEV/QAS/PRD environments. In a next SAP version you will be able to split off MS+ENQ processes, this way you can make them high available and fail-over your single point of failure processes verry quickly (no need for restarting everything). A java vm can only have 1 client to connect with. The JCo component used for communication between Java and ABAP stack uses RMI communication, communication between java stack and Gw is fast RFC.
SAP Netweaver Masterguide => Install guide (preparation & setup+post tasks) => notes
Create a dummy.emergency file that you can delete if the fs gets full, this allows you to get some playing time to backup, clean-up files or extend the fs.
Move archive logs to oraarch instead of saparch. This way brbackup will be able write temp files in saparch while cleaning-up files on oraarch.
Recently Java became a add-in installation, you need files:
Install on:
Install:
tr> rz11 > set rdisp/j2ee_start tr> smicm >menu: goto - http server - >NOTE: for j2ee status you need a SP >= 16 for all components
J2EE ports
ICM <server>:80xx
MS_ABAP <server>:81xx (ci)
MS_JAVA <server>:81zz (cs)
JAVA_SRV
<server>:5xxyy
xx = instance number
yy = 00 for dispatcher,
04 for P4 admin port,
08 for telnet admin,
18 for SDM
and
* http://<server>/8100/msgserver/html/logon
* http://<server>/8102/msgserver/html/logon
* http://<server>/50000/???
Note: for weblogons you can use
user sapjsf with roles SAP_BC_JSF_COMMUNICATION* or
j2ee_admin with role SAP_J2EE_ADMIN
The Java visual administrator can be started like this /usr/sap/<SID>/<instance>/j2ee/admin/go.sh
There is also a new argument for stopsap besides r3, all, etc. It is j2ee. This will not only stop Java but also ABAP stack!!!
Transports are different, tp/r3trans are replaced in Java by SDM.
Download into ctrun, during the start changes between ctrun and exe/run detected and copied from ctrun to exe/run (/usr/sap/<SID>/sys/exe/run).
Install and patch all EA-* components even if you only need 1 of them. This 1 component you need should be activated with transaction SPRO - Activation switch...
SETUP: [ADM110] [ERP_Components] [Export_DVD_1] [Export_DVD_2] [Language_DVD] [Presentation] [RDBMS_ORA] [SAP_Installation_Master_ECC_ORA] [SAP_Installation_Master_NW04_ORA] [SAP_Kernel_DVD_ORA] [SAP_WebAS_JAVA] ADM110: [ChangeToUTF8] [ConfigFilesSAPGuiJava] [InstGuides] [J2EEPatch] [J2SDK] [KernelPatch] [OPatch] [Oracle_patch2] [SAP Download Manager] [SAPGui_Patch] [SupportPackages] ADM110\J2EEPatch: CTRLORA07_0-20000118.SAR [J2EE-RUNT-CD] J2EERT07_0-10001982.SAR J2EERTOS07_0-20000118.SAR LABELIDX.ASC PROD_LABEL [SAPINST-CD] SAPINST07_0-20000118.SAR start patching => ADM110\J2EEPatch\SAPINST-CD\SAPINST\NT\I386\sapinst.exe ERP_Components: [ABAP_SP1] CDLABEL.ASC CDLABEL.EBC COPY_TM.HTM COPY_TM.TXT [CPROJECTS] CRCFILE.DAT [ERECRUIT] [FINBASIS] [IPCSERV] [JAVACOMP] LABEL.ASC LABEL.EBC LABELIDX.ASC [LSOFE] [MSR_2.0] [MTR-MTS_1.6] README.TXT [SEMBW] VERSION.ASC VERSION.EBC [WFMCORE] [XI_CONT]
You can include use ccms variants with treshholds for dialogs etc. in operation modes.
Migration operations should be done by a certified person. Otherwise you will not get a license or no support!