E-Sourcing System Copy [System refresh from Production to existing Development]

Size: px

Start display at page:

Download "E-Sourcing System Copy [System refresh from Production to existing Development]"

Phebe Stone
5 years ago
Views:

1 E-Sourcing System Copy [System refresh from Production to existing Development] Applies to: SAP Netweaver 7.0 and E-Sourcing 5.1/CLM 2.0 Summary This document discusses about the steps to do an E-Sourcing system copy. Author: Thilip Kumar Company: Cognizant Technology Solutions Created on: 2 February 2, 2011 Author Bio I am Thilip Kumar R.B. I am working as BASIS Consultant in Cognizant Technology Solutions and I have around 5 years of experience in Netweaver Administration SAP AG 1

2 Table of Contents Environment... 3 Pre-requisite... 3 Procedure... 3 System Copy Export... 3 System Copy Import Restore ESD_CLM database Configure E-Sourcing application Post-Installation Steps for Netweaver Post-Installation steps for E-Sourcing system Issues faced Resolution Related Content Disclaimer and Liability Notice SAP AG 2

Environment OS AIX 6.1 DB DB2 9.1.5 System copy method Homogeneous system copy Pre-requisite 1) Download brdb6brt tool from the service market place.

3) Take a database and file system copy of the existing development system Procedure Drop the Netweaver AS Java database ( in this case ESD) Command - db2 drop database <database name> Now drop the

3 Environment OS AIX 6.1 DB DB System copy method Homogeneous system copy Pre-requisite 1) Download brdb6brt tool from the service market place. 2) Turn off the functionality of the source system. 3) Take a database and file system copy of the existing development system Procedure Drop the Netweaver AS Java database ( in this case ESD) Command - db2 drop database <database name> Now drop the E-Sourcing database (in this case ESD_CLM) Drop the existing ESD_CLM database System Copy Export Install the latest brdb6brt tool according to SAP Note Run the command mentioned below to export the databases to the path specified. The option BOTH means to export both the database and create scr file in the mentioned path. Export both ESD and ESD_CLM databases 2010 SAP AG 3

4 Run the same command to export Netweaver database 2010 SAP AG 4

5 Now we need to export the Netweaver Application to the backup directory Run sapinst in the E-Sourcing Production server Navigate to System Copy IBM DB2 for Linux, UNIX and Windows Source System Export Central System Based on AS JAVA Database and Central Instance 2010 SAP AG 5

6 2010 SAP AG 6

7 2010 SAP AG 7

8 Check the option to use Database specific tools 2010 SAP AG 8

9 2010 SAP AG 9

Now start the E-Sourcing source system Turn on the e-mails System Copy Import Copy the

10 Now start the E-Sourcing source system Turn on the s System Copy Import Copy the database export from Production to development server Edit the ESP_NODE000.scr 2010 SAP AG 10

between S################ and E############# Save the scr file

11 Change the <SID> and the path according to the source system database structure You should only edit the content contained between S################ and E############# Save the scr file Check the modified ESP_NODE0000.scr file for any errors 2010 SAP AG 11

12 Confirms that the file does not contain any errors Run sapinst on development server to start the import 2010 SAP AG 12

13 2010 SAP AG 13

14 2010 SAP AG 14

15 2010 SAP AG 15

16 2010 SAP AG 16

17 2010 SAP AG 17

18 Now we need to import the database. Leave the dialog box as it is.. Do not click on Ok or Cancel Execute the command mentioned below that will create the database on the target server The restore is completed successfully for ESD database 2010 SAP AG 18

19 Now click Ok on the dialog box to continue the import 2010 SAP AG 19

20 2010 SAP AG 20

21 Restore ESD_CLM database Modify the ESP_CLM_NODE0000.scr file so that it matches the target database ESD_CLM and its structure Check the ESP_CLM_NODE0000.scr file for any errors 2010 SAP AG 21

22 Restore the ESD_CLM ESD_CLM is restored successfully 2010 SAP AG 22

23 Configure E-Sourcing application Run the configure utility in E-Sourcing to configure the E-Sourcing application to the newly imported database 2010 SAP AG 23

24 After this, deploy the fcsourcing.ear file in the visual administrator Copy the fcisystem.properties and password.properties file from the E-Sourcing production to the development server. Login to E-Sourcing with the password of production server SAP AG 24

25 Post-Installation Steps for Netweaver Install new licenses for Netweaver. Delete the old certificate in Visual Administrator and create a new certificate Post-Installation steps for E-Sourcing system Install new license Change the hostname and port number in Cluster configuration 2010 SAP AG 25

Make relevant changes to System Information Enable all the e-mails in the development. Issues faced E-Sourcing system clocks indefinitely.

26 Make relevant changes to System Information Enable all the s in the development. Issues faced E-Sourcing system clocks indefinitely. Error Class definition error Resolution Set the class path mentioned below for Instance node in Config tool./bin/boot/boot.jar;./bin/boot/jaas.jar;./bin/system/bytecode.jar;./usr/sap/esd_clm/lib/endorsed/xalan.jar;/usr/ sap/esd_clm/lib/endorsed/xercesimpl.jar;/usr/sap/esd_clm/lib/endorsed/xmlapis.jar;/usr/sap/esd_clm/lib/jcschart.jar; Look out for parameter java.awt.headless, if it is defined for both the dispatcher as well as server node SAP AG 26

27 For some reason this parameter was not reflecting in server node. Just interchange the position of this parameter in configtool. Restart the instance. Check the parameter definition in name:<port> 2010 SAP AG 27

28 Related Content SAP AG 28

29 Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document SAP AG 29

Config Tool Activities

Config Tool Activities Applies to: This Article applies to Enterprise Portal 7.0. For more information, visit the Portal and Collaboration homepage. Summary This article describes a few of the activities in Config Tool. Author: