7/22/2019 Nzdm Portal Unix En http://slidepdf.com/reader/full/nzdm-portal-unix-en 1/31 Update Guide CUSTOMER Near-Zero Downtime Maintenance 1.0 for SAP NetWeaver Portal Document Version: 1.0 - 2013-07-15 Near-Zero Downtime Maintenance 1.0 for SAP NetWeaver Portal For SAP NetWeaver Portal Systems on UNIX and Linux
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
1 In the source system, go to the User Management Engine application.2 Create a new user. Choose a user name, for example NZDMTU (nZDM technical user).
3 Fill in all required fields and set the security policy to Technical User.
4 Assign the role SAP_NZDM_ADMINISTRATOR to the user and save your entry.
5 Assign the action Destination_Service_Write_Permission to the role SAP_NZDM_ADMINISTRATOR.
This step is not necessary for SAP NetWeaver 7.0 including enhancement package 2
For more information about creating a technical user, see http://help.sap.com SAP NetWeaver
SAPNetweaver 7.<version> Function-Oriented View SAP NetWeaver by ... Security Identity
Management User Management of Application Server Java Administration of Users and Roles Creating a
Technical User .
Creating a Dedicated nZDM for Portal User for SAP NetWeaver7.0 EHP2 SPS14
Procedure
1 In the source system, go to the User Management application.
2 Create a new user group named NZDMAdministrators.
3 Assign the role SAP_NZDM_ADMINISTRATOR to the new user group.
4 Create a new user. Choose a user name, for example NZDMTU (nZDM technical user).
5 Fill in all required fields and set the security policy to Technical User.
6 Assign the new user to the group. This grants the new user rights to operate the nZDM for Portal procedure.
7 In the source system, go to the Visual Administrator. Navigate to the Security Provider service configuration.
8 Add the NZDMAdministrators group to the administrator server role.
2.3 Target System and Database ParameterRecommendations
Although not mandatory, the following recommendations will minimize the execution effort. Changing the
parameters during the procedure might significantly increase the time required to perform it.
During the copying of the source system, consider changing the following parameters:
● You can set the SID and hostname of the new system (the target system) to match the ones of the original
productive system. This ensures that external connections and Single Sign-On will work without additional
adjustments after the nZDM for Portal procedure has finished.
Near-Zero Downtime Maintenance 1.0 for SAP NetWeaver Portal
● You can set the database SID to match the database SID of the original productive system. This ensures that
the database scripts and br_tools will run correctly after the nZDM for Portal procedure has finished.
● You can set the IP address of the new system to match the IP of the original productive system. This ensures
that load balancing is functional after the nZDM for Portal procedure has finished.
2.4 Planning Aspects for the Portal in EP Core (EPC)
SAP NetWeaver Portal (specifically, the components of usage type EP Core) implements both change recording
and read-only modes during the nZDM for Portal procedure. The mode used depends on the specific Portal
application. Where recording mode is in effect, changes are recorded from the source system and replicated to
the target system; where read-only mode is in effect, the application rejects changes and notifies users that
changes cannot be made in read-only mode.
Note the following exceptions and effects:
● Caches - All caches are cleared and no data cached on the source system is replicated to the target system.
● Activity Data Collector (ADC) - If the ADC is activated, the data collected after the creation of the target
system is lost.
● Admin Tools - Changes made while recording is active are not transferred to the target system and must be
performed again manually in the target system.
● Job Scheduler - Jobs cannot be maintained while recording is active. Planned jobs will be executed both on
the source and target systems.
● Federated Portal Network (FPN) - If the system that is updated is part of a Federated Portal Network
implementation, you must be aware that trust relationships and configurations between consumer andproducer portals need to be manually reestablished after switching to the target system.
2.5 Planning Aspects for Knowledge Management andCollaboration (KMC)
Knowledge Management and Collaboration (KMC) operates in read-only mode during the nZDM for Portal
procedure. This means that all user actions that require data changes, such as configuration changes, CMrepository modifications, collaboration room content modifications, are disabled.
You must consider the following aspects when the read-only mode is initiated:
● Long-running tasks, such as re-indexing, are suspended and resumed after the replication to the target
system is completed.
● Short-running tasks, such as index deletion, which are active when the read-only mode is initiated, are
executed only after the completion of other short running tasks when KMC system switches to read-only
mode. Therefore, it might take a few minutes before KMC enters read-only mode.
● Content exchange - The Information and Content Exchange (ICE) service completes the transfer of the
currently distributed resource, and then terminates all active content transfers without completing the
transfer of the whole package. While the application is in read-only mode, no new transfers are executed.
After the application exits the read-only mode, the content exchange continues as scheduled.
This chapter provides information about performing the nZDM for Portal procedure. The complete procedureincludes all required actions before, during, and after using the nZDM for Portal tool.
Caution
Make sure you do not run nZDM for Portal during daylight saving time shifts. Otherwise, the procedure might
result in errors.
3.1 Downloading and Deploying nZDM for PortalInfrastructure Applications
The nZDM for Portal infrastructure applications are part of the following SAP NetWeaver releases and SPS levels:
● SAP NetWeaver 7.0 including enhancement package 2 with SPS014 and higher
● SAP NetWeaver 7.3 with SPS09 and higher
● SAP NetWeaver 7.3 including enhancement package 1 SPS07 and higher
● SAP NetWeaver 7.4 with SPS level SPS02 and higher
For the nZDM for Portal supported releases lower than the ones listed above, you must download the nZDM for
Portal software archive (including the infrastructure applications) relevant for your release and SPS level from
SAP Note 1831724. Afterwards, deploy the archive using the Software Update Manager (SUM) SP07 and higher.
Related Links
Downloading and Using Software Update Manager [page 20]
3.2 Downloading and Running the nZDM for Portal GUI
Prerequisites
You have SAPCAR on the host where the GUI is started.
Context
By using the nZDM for Portal GUI, you can configure the source and target systems and monitor the progress of
the nZDM recording and replication. After connecting to the systems, you can start or stop the recording on the
source system, or the replication to the target system. Also, you can monitor the current recording and replication
status, as well as the number of recorded and replicated entries. The nZDM for Portal GUI is extracted to a
destination directory named NZDM_EP. After the archive is extracted, this destination directory contains java and
1 Open a command prompt.2 Navigate to the directory in which you have extracted the nZDM for Portal GUI.
3 Start the nZDM for Portal GUI by entering the following command: .
startup.bat "guimode=accessible"
3.4 Connecting to the Source System and Starting theRecording
Prerequisites
The nZDM for Portal GUI must be started. For more information, see section “Downloading and Running the
nZDM for Portal GUI".
Context
Before you start recording for the first time, you must connect to the source system. Proceed as follows:
Procedure
1 Choose Source System Connect .
2 In the Connect dialog, enter the connection values tand the logon credentials that you have configured in the
source system:
a) Host - the host name or IP address of the source systemb) Port Number – the HTTP port of the source system, for example 5<instance_number>00, or HTTPs
port of the source system, for example 5<instance_number>01.
c) User and Password - the credentials of the user for the nZDM for Portal procedure. This can be the
Administrator user or the nZDM for Portal technical user.
d) Enable HTTPs - Leave this checkbox enabled if you are entering an HTTPs port, or disable it if you are
entering an HTTP port. Note that to use the capability of HTTPs communication it is necessary that
HTTPs is enabled in your SAP NetWeaver system.
3 Choose Apply to confirm your entries.
4 Choose Start Recording on the Source System part of the nZDM for Portal GUI.
5 In the Enter source system host dialog, enter the IP address or hostname of the source system database host
All data changes to important business data managed by applications running in recording mode that occur in thesource system will be recorded. To avoid any deployment in the source system after the recording has started,
the system is locked for deployments.
Related Links
Downloading and Running the nZDM for Portal GUI [page 10]
3.5 Removing Freeze Triggers from Third-Party Software
Note
This section is relevant only if you have third-party software in the system.
If you are running third-party software in the SAP NetWeaver Portal system that use own database tables to store
data, be aware that freeze triggers are created in these tables, preventing write access to them. To restore write
access to these tables, you must manually remove all triggers with the prefix TRG_NZD* from the relevant tables.
The triggers can be removed by means of a standard database client connected to your SAP system. They can be
removed from the relevant tables individually or fully via an update statement.
Note
Applications using the Portal Content Directory (PCD) persistence layer are not affected, because PCD will
implicitly implement change recording for the data.
3.6 Creating the Target System
Prerequisites
The recording in the source system must be started before creating the target system.
Context
To apply Support Package Stacks without stopping productive use of your SAP NetWeaver Portal system, you
must create an exact copy or clone of your source system and database. For performing the system copy or
cloning, you can use any procedure and tool of your preference.
Note
Near-Zero Downtime Maintenance 1.0 for SAP NetWeaver Portal
At a point of the nZDM for Portal procedure before it has been finished, you may want to perform testing in thetarget system to verify that the SP stack or other maintenance activity you performed previously has been applied
correctly and all major production scenarios are still operational. You can perform these activities in the target
system without affecting currently active production operation in the source system. You need to take the
following considerations into account:
● Make sure that the replication is stopped while test activities are being performed. If you have already started
the replication, choose Pause Replication to temporarily suspend it before you start testing. After you have
finished testing, choose Continue Replication to resume the replication.
● Data created during testing could interfere with the replication. To avoid such issues, we recommend that you
create a complete backup of the target system database before you start testing. Restore the backup after
you finish testing, and before you start or continue the replication.
3.9 Connecting to the Target System and Starting theReplication
Prerequisites
You have started the nZDM for Portal GUI. For more information, see section "Downloading and Running the
nZDM for Portal GUI ".
Context
Once the target system is set up, you must enter the connection data for the target system in the nZDM for Portal
GUI. The target system also requires a connection to the source system remote database and HTTP access point.
Proceed as follows:
Procedure
1 Configure the target system. Choose Target System Connect .
2 Enter the connection data and the logon credentials of the target system.
○ Host name - host name or IP address of the target system
○ Port Number - HTTP port of the target system, for example5<instance_number>00), or HTTPs port of
the target system, for example (5<instance_number>01)
○ User and Password - the credentials of the authorized user for the nZDM for Portal procedure. This is
either the Administrator user or the nZDM technical user.
The SAP Web Dispatcher serves as a central entry point and load balancer for HTTP or HTTPs requests to SAPapplication servers. In the reference scenario, it is configured to run against the message server of the SCS
instance of the portal.
For more information about the SAP Web Dispatcher, see http://help.sap.com SAP NetWeaver SAP
NetWeaver <release> System Administration and Maintenance Information Technical Operations for SAP
NetWeaver Technical Operations for SAP Web Dispatcher .
4.2.3 System Copy Functionality of Software ProvisioningManager 1.0
In the reference scenario, the target system is created using the system copy functionality of software
provisioning manager 1.0. The tool is operating system and database-specific.
Consider the following recommendations and additional steps:
● Perform a database-specific homogeneous system copy, since only this system copy method allows you to
copy your system without additional downtime.
● When specifying the parameters of the target system make sure that all parameters, such as SID, instance
numbers, ports, and passwords, exactly match the same parameters of the source system.
● After restoring the database backup of the target system database and before continuing with the system
copy, manually remove all database triggers with the prefix TRG_NZD* from the relevant tables. The triggers
can be removed by means of a standard database client connected to your SAP system. They can be
removed from the relevant tables individually or fully via an update statement.
● To have a completely identical target system, copy the kernel and JVM files from the source system to the
target system after the system copy has finished.
You must create a homogeneous system copy of your source system, that is, you must create a database-specific
system copy.
To download the user guide for software provisioning manager 1.0, go to http://service.sap.com/instguidesnw.
See http://scn.sap.com/docs/DOC-8324 for general information about system copy.
4.2.4 The nZDM for Portal Procedure
The nZDM for Portal procedure is carried out as described in chapter "Running nZDM for Portal" of this document,
except for the system switch, which is described in the following sections.
Related Links
Performing the nZDM for Portal Procedure [page 10]
4.2.5 Switching From the Source System to the TargetSystem
The switch from the original production system to the copied system consists of the following steps:
1 Initial switch of application servers - one or several application server instances are taken offline, that is,
disconnected from production operation, in order to free resources for the copied system with application
servers
2 Switch of central entry point to application servers - the system enters the downtime, and the central entry
point (in the reference scenario, the SAP Web Dispatcher) is switched to the new system.
3 Final switch of the application servers - at this moment the switch of the remaining application servers to the
new system takes place.
4.2.6 Switching the Application Servers
Switching the application servers can be done by uninstalling the application server and installing a new one
running against the new system on the dialog instance/additional application server instance host. This switch is
straightforward to implement, but might lead to unnecessary overhead, particularly in landscapes with a large
number of application servers.
4.2.7 Reconfiguring the SAP Web Dispatcher
Context
In the reference scenario the central entry point to the Portal is the SAP Web Dispatcher. It connects to the Portal
system via its message server. For switching to the new system it is sufficient to shutdown the dispatcher and
adapt the profile entries.
Procedure
1 Adapt the profile entries as described in the example below and according to the connection data of the
copied system:
#-----------------------------------------------------------------------# Accessibility of Message Server#--------------------------------------------------------------------------------rdisp/mshost = <message server host>ms/http_port = <message server port>
Note that sessions held by connected users are shut down during this process.
2 Start SAP Web Dispatcher.
Near-Zero Downtime Maintenance 1.0 for SAP NetWeaver Portal