SAP AG. All rights reserved

Transcription

On Demand to On Premise Migration
SAP Sourcing/CLM Webcast series
SAP Sourcing Center of Excellence
November 2012
SAP Sourcing / CLM 2012 Webcast Series
Goal
• Spread the knowledge about SAP Sourcing
• Build and leverage the SAP Sourcing
community
Audience
• SAP Consulting and Field Services
• Partner Consulting
• SAP Sourcing Customers
Upcoming Webcasts
• New Features in SAP CLM – eSignature,
Delegation & Clauses
© 2011 SAP AG. All rights reserved.
Internal
2
Agenda
1. Project Outline
2. Preparation
3. Initialization
4. Testing
5. Production Preparation
6. Migration
7. Cutover
8. Other Information
Internal
3
Project outline
On Demand to On Premise Migration
Audience
• SAP Consulting
• SAP Hosting
• Customers & Partners
Scope
• High level project outline
• Timelines
• Documentation
Goal
• Migrate your On Demand system to
an On Premise deployment
Internal
5
Sample Project Plan
Scalable Timeline proposal
Activity
Preparation
1
2
3
4
5
6
7
8
9
Preparation
Kickoff
Schedule
Upgrade OD staging
Review supported platforms
Discuss Authentication strategy
Initialization
Initialize
Provision software/hardware
Setup OP landscape
Communicate to users
Installation
Installation
Install and configure NW
Install Sourcing/CLM OP
Testing
Testing
Dry run export DB
Document/DB adjustments
Test migration/authentication
Migration
Migrate
Transport Production DB
to customer
Import and perform DB adjustments
Test authentication
Cutover
Cutover
Go/No-Go Decision
End User Communication
Internal
6
Process
Preparation
Initialization
Testing
Production
preparation
Migration
Cutover
Documentation
Provision Hardware
and Software
Document process
Production installation
Shut down On-Demand
/ Hosted system
Communication
Prerequisites
Build Sandbox
Test migrated systems
Plan Communication
Transport production
database to customer
End Users
Release Strategy
DB Writeback
Test user
authentication
mechanisms
Final preparations
before migration
Import Database
SAP Hosting
General Considerations
Database Dry Run
Turn on email
Go/No go decision
Landscape
Datapump import
Declaring Intent
Start Sandbox
Software Download
Load NW system
properties
Installation and Initial
setup of NetWeaver
and Sourcing
production
Test
Deploy application
Remap cluster
information
Authentication
Internal
7
Preparation
Documentation Requirements
SAP Delivered Documents
 Installation Guide
 Configuration Guide
 Master Guide / Supported Platforms
 https://service.sap.com/eso
Project recommended documents
 Timeline
 Landscape Diagram
 Hardware Specifications
 Software Specifications
 Export of System and Enterprise level
properties.
Internal
9
Prerequisites and Upgrade Strategy
Prerequisites
• Licensed SAP Sourcing Customer
• On a release in maintenance
• Running on Oracle
General Considerations
• It is required that the On Premise version be the same as the On Demand / Hosted
version. [including patch level]
Additional Planning
•
•
•
•
•
SAP Sourcing / CLM user authentication strategy
How to handle any custom integrations
Optional services : Optimizer, Contract Generation
Authorizations – Plan for Internal and External authorization issues.
Migrate from the On Demand ORACLE system to an On Premise ORACLE system: NO
CONVERSIONS TO OTHER DATABASE PLATFORMS.
Internal
10
On Premise version the same as the On Demand
What does this mean?
If a customer is on On Demand wave n+1 they cannot migrate to version n
until that corresponding version or higher is available On Premise.
 Example 1:Once Wave 7 customers are on Wave 8, On Demand to On Premise
is not be an option until Wave 9 is out and their On Demand system has been
upgraded to it.
 Example 2: A customer is on E-Sourcing 5.X or 7.0 our preference is that they
upgrade to SAP Sourcing 9.0 in the hosted environment prior to migrating On
Premise. For some customers, the act of upgrading to version 9.0 prior to
migration may be a several month process.
Internal
11
Landscape considerations
1/3
 Hardware Resources
 High Availability
 Application
 Database
 Authentication method(s)
 Security Design
 Securing external users
 Load balancing
 User concurrency for # of instances.
 Peak
 Average
 Network layers
 Domain Name Settings
Internal
12
Landscape considerations
2/3
 A detailed landscape diagram covering all environments, networks, firewalls, OS
versions, etc. is required to ensure that the proper hardware is ordered and
setup.
 The installation guide can be used as a reference. It is important to consider what
additional "services" (e.g., Contract Generation, Optimizer, Virus scanner,
Supplier Portal) will be included in the landscape.
 During this landscape preparation, it should also be determined what user
authentication method will be used and how that will impact the migration.
 These steps should also review the supported platforms documentation to
ensure desired landscape is supported.
Internal
13
Example system landscape
SAP Sourcing 9.0
3/3
Web/App Layer
Web Server
e.g. Enterprise Portal
IDS/IPS
http(s)
https
Firewall e.g. VPN
Firewall
https
Load Balancer
Buyside User
Sellside User
http
SAP Sourcing
SAP ERP
ftp
ftp
SMTP
LDAP
Virus
Scan*
Database Layer
NW CE
J2 EE
.NET*
Optimizer*
Database
JDBC Layer Firewalls
Oracle 11G
*: These servers are optional and only required if that particular usage
scenario is enabled
FTP*
Process
Integration*
ECC 6.0+*
SERVER DESCRIPTIONS
 SMTP: Outbound SMTP Relay Required
 LDAP: Used for authentication
 Virus Scan: Symantec AV Scan Engine (server side software. Attachments are
streamed through his service before being written to disk)
 NW CE J2EE: NetWeaver Java Web Application Server
(NW CE 7.3 SP3)
 .NET: Server used for contract generation (requires MS-Word)
 Process Integration: SAP NW PI 7.0+ (for integration to ERP)
 FTP: typically used to move integration files around. File share
could also be used
 IDS: Intrusion Detection/Protection; recommended: MacAfee 2750
 ECC 6.0+: SAP ERP-MM (6.00 and higher)
Internal
14
Declaring Intent to Migrate to On Premise
Create a CSN message under the component LOD-ESO-HST
Message must contain the following:
 SAP Consultant involved
 Customer information and SMP S#.
 Proposed dates
 Dry run
 Final cutover
At a later date it is recommended to provide SAP Hosting with a static HTML page
to replace On Demand login page.
Internal
15
Software Preparation
 Check current On Demand version
 Discover what version you will be migrating.
 Check equivalent version is available for On Premise before requesting On Demand
upgrade
 Read release notes.
 E.g Note 1485210 - SAP Sourcing 7.0 SP02 On Premise Support Pack Note
 Note 1526147 - Release Information Note for SAP Sourcing Wave 9 SP02
 Download software
 Sourcing Application
 Contract Generation and MS Word
 Application Server
 Database software
Internal
16
Initialization
Provision Hardware and Software
 It is important to align the provisioning and expected
hardware/software arrival dates with the consulting
resource.
 This can lead to unnecessary bench time.
 Typically, this can be a cause for delays so it is good to
understand this process early and ensure the
necessary configuration items are ordered early on.
 Sample landscape and hardware requirements are
available on the SAP Sourcing PAM
[service.sap.com/pam]
Internal
18
Build Sandbox System
 SAP Consulting should be provisioned to help with the installation.
 A baseline database installation should be done at this stage so that
connectivity and configuration can be tested.





SMTP
Buyside/Sellside Login
Load balancing
DNS
Optional services
 SAP consultants will require access to the hardware to assist with the
installation.
 This is good learning stage for the Customer’s Basis resources.
Internal
19
On Demand/Hosted Database Writeback
 A database write back from production to
staging for import to the On Premise
sandbox is required so that initial testing
can be done using recent data.
 This should be initialized with a CSN ticket.
 Expect a 2 week lead time on this request.
Internal
20
On Premise Dry Run Database Preparation
The target Database for the On Premise installation is to be installed on its
own hardware (BEST Practice) and is set up as outlined in the Installation
guide’s Section 3.5.
Identify
Install
Obfuscation Toolkit
Create
Install
servers
Tablespaces
Oracle Text Search (Oracle 10g only)
Create
Oracle Service Account
Gather
Schema connection information
Verify
settings for sourcing.
Copy
JDBC Driver
CREATE USER sourcing70 IDENTIFIED BY password
DEFAULT TABLESPACE SOURCING TEMPORARY TABLESPACE TEMP
PROFILE DEFAULT ACCOUNT UNLOCK;
GRANT CONNECT TO sourcing70;
GRANT RESOURCE TO sourcing70;
GRANT CTXAPP TO sourcing70;
ALTER USER sourcing70 DEFAULT ROLE CONNECT,RESOURCE,CTXAPP
GRANT UNLIMITED TABLESPACE TO sourcing70;
GRANT CREATE VIEW TO sourcing70;
Migrations to SAP Sourcing 7.0 mandate that Oracle 11g is used.
Internal
21
Dbimport Dry Run
Prep
Action
• Establish the transport mechanism [HDD or
FTP]
• Identify DBA
• Disable Scheduled tasks
• Export DB using Datapump
• Encrypt Export
• Transfer or Courier data.
Transport • Ensure secure transport.
Internal
22
On Premise Data Pump import
SAP will provide a Datapump export of the
source database.
 Dump file name = <provided_filename>
 Source Schema Name = <ODschemaName>
 Target Schema Name = <OPschemaName>
 Source Tablespace= <ODtablespaceName>
This is a generic Datapump Import
statement that might be used to restore
the DB on Premise . You will need to
provide the ODschemaName and
ODtablespaceName to complete this task.
 Target Tablespace = <OPtablespaceName>
(SQLPLUS VERSION)
impdp system/<password>
DIRECTORY=DATA_PUMP_DIR DUMPFILE=
<provided_filename>.dmp REMAP_SCHEMA=
<ODschemaName> :
<OPschemaName>REMAP_TABLESPACE=
<ODtablespaceName> : <OPtablespaceName>
Internal
23
Changing Timezone
 If the On Premise installation is in a
different timezone form the hosted
environment (America/New_York), the
time zone offsets need to be fixed for
the new time zone. A customized
version of Convert_DB_TimeZone.xml
will need to be created and executed
also using dbimport.
 When migrating the Database outside
of the New York EST time zone its
timezone should be converted to
whatever the local time of the new
systems is.
 Documentation is available from SAP
Support on this process.
Internal
24
Start Sourcing Sandbox
Run
configure
 Enter Database connection Information
 Add context to match
Undeploy
Deploy
Start
new SCA
application
Check
Login
Note:
old SCA
log
as system user.
guides can be found at https://service.sap.com/eso
Internal
25
Load NW system properties
 In the DB Importer, (DBimport) use the file picker to
browse to and select
fciinstall.jar/scripts/dev/import_netweaver_system_pro
perties.xml
 These properties will require updating to use the fully
qualified hostnames and ports as the system user after
the application has been started.
Internal
26
Deploy app in NW and start app
 Deploy the application using
the JSPM.
 Start the application in NWA.
Internal
27
Remap cluster information
 After the Database is imported bring up the application and login as system to
the System Default cluster using the IP address of the machine as the hostname.
 http://<IPAddress>:50<INST_NO>00/<context>/fssystem/portal/lo
gin
 Navigate to the cluster configuration area and update the active cluster
associated with the context you will be using and update the following.




Hostname
Port
Aliases
Cluster Member
 Save the changes.
Internal
28
Authentication
 The On Demand users are stored in OpenLDAP systems for the purposes of
authentication. This user data can be exported in LDIF or CSV format for import
into an existing Customer LDAP or centralized authentication system.
 Complications exist in the process of migrating passwords as different LDAPs
cannot decrypt each others secured information.
 Having external users or vendors authenticate against an internal LDAP is often
not allowed and so a security exception or new authentication system needs to
be provided.
Internal
29
Other Configuration changes….
Still
as the system user, Update the Directory Configurations as needed.
Update




the System Properties as documented in the dry run, e.g.
SMTP
Optimizer IP
Virus Scanner
Contract Generation
Login
as the Enterprise User
 http://<IPAddress>:50<INST_NO>00/<context>/fsenterprise/portal/login
Update
Save
all changes and restart the instance.
Check
Test
any enterprise level properties / company data as required.
the application logs for errors.
end user access and complete testing checklist.
Internal
30
Document process and adjustments
 The database copied from the SAP On Demand landscape to the On Premise landscape
includes certain host and other information the requires updating.
 These updates should be documented at this point in preparation for the production
migration.
 To be adjusted and documented for production migration:





The installation guide is a good starting point for this
If necessary – update database time zone offsets using the dbimport procedure provided
Import NetWeaver Properties using dbimport
Cluster(s)
Directory configurations
 System Properties:




Contract Gen URL
JNDI host/port
Optimizer host/port
Master time zone, SMTP host, Virus Scan host, etc.
Internal
31
Testing
Testing
 Test user authentication migration
 Dry run of database export / transport / import
 Document database adjustments
 Time zone update
 Test migrated system
 Login as enterprise
Internal
33
Test migrated systems and User Authentication
 SAP uses OpenLDAP for the authentication of users. We have found that
different LDAPs (MSAD) don’t always have compatible password algorithms.
 It may be best for the customer to re-import all active users with the ‘generate
password’ flag set.
 Based on the decision for how this will be done, a test should be performed to
ensure that migration of user accounts to the On Premise deployment will work
correctly.
 The customer should spend time testing the new On Premise landscape to
ensure proper functionality.
Internal
34
Production Prep
Production Installation
 Plan communication to users
 Installation and initial setup of NW
 Installation of ESO
 Import SAP On Demand database
copy into customer database
 Note: Document attached.
Internal
36
Plan communication to Users
 Since URLs will be changing as part of the On
Premise migration, it is good to plan a
communication to the end users regarding the
changes.
 An initial communication alerting the users is a
good idea.
Internal
37
Final Preparations before Migration
 It is Best practice to stop the following prior to
Migration On Premise:
 In general, it would be best to have all RFxs and
Auctions completed prior to the migration.
 There should be no e-mails in the queue when
the Database is exported.
Provide SAP Hosting with a static HTML page to
replace On Demand login page.
Internal
38
Installation and initial setup of NW
Installation steps:
 For SAP Sourcing 7.0 a valid NetWeaver Java stack
needs to be installed and prepared.
 Connected to the System Landscape Directory
 Patches applied
 UME configured to point to central LDAP if applicable.
 NetWeaver CE 7.3 download home on the service
marketplace.
Internal
39
Installation of ESO Production system
 Install requires software components and
connect to prepared target database.
 A baseline database can be created with
dbimport to test that the software is correctly
installed. A decision should be made on whether
you will reuse this schema or if it will be purely
for testing the installs.
Internal
40
Migration
Transport and Continuation
Transport production database to customer:
The
method of transport needs to be agreed upon
by Hosting, consulting , and the customer.
If
a courier outside of consulting is used SAP
cannot be responsible for the data during transit.

If Physical Media is used, a best practice suggest
the media is encrypted. TrueCrypt has been best
practice for this purpose.
If a customer wishes to provide a static HTML page to
hosting stating that the system has moved and
displaying the new URLs, we will stand that page up for
60 days post migration.
Note: Documentation attached.
Internal
42
Import Database
 Using prepared documentation on
import process import the source
database using Oracle Datapump
Import (impdp).
 Time for this to occur can vary but we
have experience of 18Gb’s taking
approximately 8 hours.
 A better understanding of how long
this will take will be established during
the Dry run.
Internal
43
Testing Production
 Use the documentation created from dry run of
database export / transport / import to update the
system.
 Database adjustments per documentation
created
 Test migrated system
Internal
44
Turn on email and enable Scheduled tasks
Under the Daemons tab in System information edit and enable the Daemons.
Review, update, and enable all scheduled tasks within Sourcing that were disabled
prior to migration.
Internal
45
Cutover
Communication
End Users
 New URL
 Reporting issues
 Authentication changes
SAP Sourcing Hosting Team
Internal
47
Go/No Go decision
 Go / No Go decision should be
communicated to all parties involved,
especially SAP Hosting. If No Go decision
is made, SAP hosting will have to bring up
the OD/Hosted system.
 The deadline for Go / No Go decision must
be planned ahead of time and
communicated to SAP hosting.
 This is important in that a no-go decision
could result in the SAP hosted environment
remaining intact.
Internal
48
Other Information
Database choice/conversion
 OD/Hosting databases are all held on Oracle Databases.
 In all cases we recommend that the customer migrates to another Oracle OP
Database.
Internal
50
Multi-tier landscape considerations
Assumptions
SAP
hosting generally operates on a 2-tier system
Standard
SAP Best practices advocate a 3-tier landscape
 Alleviated by planning a DEV tier as the first and testing instance.
 Practice run on QA/Staging
4-tier
landscapes will affect time line
Landscape Architecture
 Staging/QA landscape mirrors Production and that user scalability & performance
has been factored in.
Concurrent
users and expected landscape requirements.
 User activity report can be generated and used to better inform sizing decisions.
Internal
51
ERP Integration Reconfiguration 1/2
•Refer
to the On Premise ERP Integration guide before attempting any of these
steps.
•PI
& ERP Integrations must be reconfigured especially for upgrades.
•Best
considered as its own integration project
•Sourcing
Steps
After application migration to On Premise , Import the PI content of On Premise
version and follow the integration guides configuration steps.
•Master
1.
2.
3.
4.
•
Data integration
Create outbound/inbound directories for data import of materials, vendors, rfx
Create directories - upload, queue, archive for the scheduled tasks
Update the scheduled task parameters - Remove the hosting FTP server information
Update the FTP parameters in Integrated System Configuration
Business Document Integration
1. Update the PI URL in Integrated system configuration . If PI and sourcing on the same
network , Http/https can be used . Update the external host name to the internal
hostname or internal IP.
Internal
52
2. If https is used, install the root/intermediate certificate on sourcing server.
ERP Integration Reconfiguration 2/2
PI configurations
1.
Update PI configuration to send/receive files from the outbound/inbound dir
created in Master Integration Point 1.
2.
Remove the host file entry containing the IP and host name of the hosting FTPs
server.
Network configuration
1.
Disallow the ports 30000-40000 outbound for hosting FTPs data connection in
the firewall
2.
Remove the IP address of the hosting sourcing server from the firewall allowed
for https inbound connection
Internal
53
© SAP AG. All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be
changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft
Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,
System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer,
z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER,
OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP,
RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered
trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or
registered trademarks of Adobe Systems Incorporated in the United States and/or other
countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are
trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World
Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for
technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
StreamWork, and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP AG in Germany and other
countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
mentioned herein as well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Sybase, Inc. Sybase is an SAP company.
All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational purposes only. National
product specifications may vary.
The information in this document is proprietary to SAP. No part of this document may be
reproduced, copied, or transmitted in any form or for any purpose without the express prior
written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any
other agreement with SAP. This document contains only intended strategies, developments,
and functionalities of the SAP® product and is not intended to be binding upon SAP to any
particular course of business, product strategy, and/or development. Please note that this
document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not
warrant the accuracy or completeness of the information, text, graphics, links, or other items
contained within this material. This document is provided without a warranty of any kind,
either express or implied, including but not limited to the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct,
special, indirect, or consequential damages that may result from the use of these materials.
This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no
control over the information that you may access through the use of hot links contained in
these materials and does not endorse your use of third-party Web pages nor provide any
warranty whatsoever relating to third-party Web pages.
Thank You!
Contact information:
Paul Wagner
Software Engineer
SAP Sourcing - Center of Excellence
Cambridge, MA. USA
617 715 7455

SAP AG. All rights reserved

Transcription

Similar documents

High Voltage Maintenance

SAP Enhanced Warehouse Management Project

success in furniture retail

SAP Predictice Analytics Roadmap

Ariba® Sourcing Solution

Where There is no Beer: Arenga pinnata and Sagueir in Sulawesi

New Project Planning - Overview with SAP ECC 6.0 EhP6

SAP Extended Diagnostics by CA Wily

Tsogo Sun Case Study

Hapag-Lloyd Success Story