on 02-28-2014 1:45 PM
we ran a homogenous system copy (with SWPM - 70SWPM10SP04 + SL-Controller 700 for SWPM-SP04)
the source-system is ECC-606 (NW-7.03) and we recognized this issue:
in the source-system, we did not set (in the default-profile) this attribute (gw/acl_mode) yet,
and (because of NW-7.03 ? , the default-value in RZ11 is shown: gw/acl_mode = 0 )
but
in the target-system (result of system copy) the default profile contains this new entry:
gw/acl_mode = 1
and also in RZ11 the default-value has changed to: gw/acl_mode = 1
http://help.sap.com/saphelp_nw74/helpdata/en/48/b2096b7895307be10000000a42189b/content.htm
maybe the system-copy routine of SWPM contains something from NW-7.31 instead of NW-7.03 ??
and
in higher NW-releases the default-value of gw/acl_mode = changes from = 0 to = 1 ???
so several RFC HTTP Connections with PGM-ID did not work
it took some time of analysation to locate this issue and how to resolve this.
we normally expect that system-copy runs an 1:1 without such changes in behaviour.
Dear Christoph,
SAP has implemented "gw/acl_mode = 1" as the mandatory security settings for all SAP Netweaver 7.0x and higher systems. The new setting is described on SAP note 1843782. I sure you probably run into this note, and that it might only refer to new installations; the truth is that an import system is a new installation with the original database source. New or updated profile values will happen.
In addition, SAP note 1961296 shows this issue will also occur when installing an Addition Application Server. The best to avoid this and other issues in the future is to back up profiles before these operations and thoroughly determined any profile changes and it consecuences.
Best regards,
Luis
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Luis B Gonzalez-Suarez wrote:
Dear Christoph,
SAP has implemented "gw/acl_mode = 1" as the mandatory security settings for all SAP Netweaver 7.0x and higher systems. The new setting is described on SAP note 1843782. I sure you probably run into this note, and that it might only refer to new installations; the truth is that an import system is a new installation with the original database source. New or updated profile values will happen.
In addition, SAP note 1961296 shows this issue will also occur when installing an Addition Application Server. The best to avoid this and other issues in the future is to back up profiles before these operations and thoroughly determined any profile changes and it consecuences.
Best regards,
Luis
maybe it is possible to give a hint to this behaviour of SWMP + systemcopy
(note when running SWPM),
to avoid customers to run into trouble after using homogenous system copy.
thanks
Hi Christoph
On IBM i you perform the system copy without System copy method
1. Take full backup source system & restore the same to new LPAR in the private environment (Without connecting in the live network)
2. By using the SWPM you can rename the SID for refer the links
System Rename | SCN and SAP Note 1619720 - System Rename for SAP Systems based on SAP NetWeaver
Regards
Sriram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.