on 05-13-2008 8:18 AM
Hi All,
Can anybody guide me for creating Standby System for Window base Optimizer system of SCM5.0?
Thanks in Advance
Regards
Pranav
Thanks Natalia,
I want to build Disaster Recovry Standby system for Optimizer.
Regards
Pranav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Pranav,
-> "I want to build Disaster Recovery Standby system for Optimizer."
Are you looking for Disaster Recovery Standby system SAP APO Optimizer for SAP SCM 5.0,
installed using "Installation Guide SAP APO Optimizer for SAP SCM 5.0 SR3" ?
=> If - yes. There are no data saved on the system SAP APO Optimizer server.
There are Optimizer's executables & the SAP communication software installed.
Therefore you don't need the Recovery of system SAP APO Optimizer server.
In case the SAP APO Optimizer server will be not available any more, you could
install the SAP APO Optimizer for SAP SCM 5.0 on another server & change the
Optimizer's TCP/IP connections OPTSERVER* to be pointed to the correct location.
You need Disaster Recovery Standby system for SCM 5.0 < liveCache/APO database>.
-> If it's not what you are looking for, please give more details about the architecture of
your system & give the example of the Disaster you would like to prevent.
Thank you and best regards, Natalia Khlopina
Hi Natalia,
Just like in ECC,in case of such situation (standby DR) we will normally sync the File system such as /usr/sap/<SID>...etc
from the primary site to DR site
Can you confirm whether we need to sync any folder located in Optimise server from promary site to DR site.
or we can keep DR site(Optimiser server) installed and at the time of Disaster,we will just point RFC's to new Optimiser server located at DR site
Thanks and Regards
Pranav
Hello Pranav,
-> Please review the SAP notes::
886103 System Landscape Copy for SAP SCM
952783 FAQ: MaxDB high availability
-> As I already wrote you, check that you have installed the SAP APO Optimizer for SAP SCM 5.0 &
& set the Optimizer's TCP/IP connections OPTSERVER* to be pointed to the correct location in /nsm59 of the
Target < DR> system.
If any Optimizer's parameters need to be set the application team could adjust them later.
Please see the SAP note 886103 at section "TCP/IP Connections - RFC Destination Type T to APO Optimizer: "
Thank you & best regards, Natalia Khlopina
Hello Pranav,
Did you already check "Installation Guide SAP APO Optimizer for SAP SCM 5.0 SR3" ?
< Service.sap.com/instguides -> SAP Business Suite Applications -> SAP SCM -> SAP SCM Server
->Using SAP SCM 5.0 Server >
-> If you use a dedicated server for SAP SCM Optimizer, you need to install the SAP Standalone Gateway before:: section "4.3 Installing an SAP Standalone Gateway Instance"
-> "The following DVDs are required for the installation of SCM Optimizer:
-> SAP Business Suite 2005 SR3 Installation Master DVD
-> SAP SCM 5.0 SR3 Components DVD"
==> If the Installation Guide SAP APO Optimizer for SAP SCM 5.0 is still unclear, I recommend you to create the SAP ticket to the component 'SCM-APO-OPT'. This question is not related to the MAXDB/liveCache forum.
Thank you and best regards, Natalia Khlopina
Hello Pranav,
-> If you use a dedicated server for SAP SCM Optimizer, you need to install the SAP Standalone Gateway before, as it's written in the installation guide.
Are you looking for this guide:
service.sap.com/instguides -> SAP Business Suite Applications -> SAP SCM
-> SAP SCM Server -> SAP SCM Using SAP SCM 5.0 ->
"Installation Guide SAP APO Optimizer for SAP SCM 5.0 SR3" ?
All steps are given in this guide.
-> If not, please give more details < question/problems > on the reported issue.
Thank you and best regards, Natalia Khlopina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.