SAP-Post DB refresh activities for JAVA instance starting from NW 7.31

Starting from Netweaver 7.31 SAP has removed file system dependent data store for JAVA instance and included all the required apps and configurations inside the database itself.

We can perform normal DB refresh for standalone JAVA instance as like ABAP but still which is not yet officially recommended by SAP.

However technically this scenario is proved working and i am sharing the steps with you all.

Scenario:-

Need to perform DB refresh with latest offline/Online backup taken from Production system to Quality system of standalone JAVA instance.

Note:- In this example i am using DB2 database with DB2 offline backup


1) Shutdown SAP JAVA & DB in target system

2) Perform DB restoration with the below command

                a) Execute the below command in target system to perform restore

                     db2 RESTORE db SID from /sapbackup TAKEN AT 20120205234943

                b) Execute the below command to create script file to change SID for the target system

                   db2 RESTORE db <SID> FROM /SAPBACKUP TAKEN AT 20120205234943                                  REDIRECT GENERATE SCRIPT /db2/db2restorePRD.clp

                c) Modify the target SID in the db2restorePRD.clp and paste it in target system & run the                         below command

                    db2 -tvf /db2/db2restorePRD.clp

3) Once DB is up and running with changed SID, check the list of table spaces in old SID with below command

                   db2 "list tablespaces" | grep Name | awk '{print $3}' | grep "#"

4) Perform the tablespace rename for each using the below command

                   db2 "rename tablespace <SID>#<Tablespace> to <SID>#<Tablespace>"


5) Once all tablespace renamed, use the below command to generate script for subsequent executions

                  db2look -d <SID> -l -o dblook.sql

The command will generate tablespace creation statements and saves in dblook.sql

6) Drop the temporary tablespace & recreate the same

                 db2 drop tablespace SYSTOOLSPACE, SYSTOOLTMPSPACE

Now execute the tablespace creation command from dblook.sql like below & execute it

CREATE LARGE TABLESPACE "SYSTOOLSPACE" IN DATABASE PARTITION GROUP IBMCATGROUP PAGESIZE 16384 MANAGED BY AUTOMATIC STORAGE AUTORESIZE YES INITIALSIZE 32 M MAXSIZE NONE EXTENTSIZE 2 PREFETCHSIZE AUTOMATIC BUFFERPOOL IBMDEFAULTBP OVERHEAD 7.500000 TRANSFERRATE 0.060000 NO FILE SYSTEM CACHING DROPPED TABLE RECOVERY OFF;

CREATE USER TEMPORARY TABLESPACE "SYSTOOLSTMPSPACE" IN DATABASE PARTITION GROUP IBMCATGROUP PAGESIZE 16384 MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 2 PREFETCHSIZE AUTOMATIC BUFFERPOOL IBMDEFAULTBP OVERHEAD 7.500000 TRANSFERRATE 0.060000 FILE SYSTEM CACHING DROPPED TABLE RECOVERY OFF;

7) Provide db admin rights to SAPSID user with below command

                 db2 grant DBADM on database to SAP<SID>

8) Copy the below files from the source system to target system from the location (Optional Step)

Note:- This step must be executed only in case where you don't know the key-phrase of source system or else if you know the key phrase of source system just provide the same without copying 
SecStore.key & SecStoe.properties from source system.

Location:- /sapmnt/<SID>/global/security/data to the same location in target

Files:- SecStore.key & SecStore.proterties

Caution:- Do not forget to edit SID and Host-name connection details of target system, otherwise the data will get updated  to source system.

Open configtool and change the key-phrase to re-encrypt database on target system after STEP 9.


9) Once DB activities completed, open configtool and update connection string first and restart configtool then update schema user (sap<SID>db) and its password in secure store


10) To update UME backend ABAP system need to follow the below steps

              a) Make sure java is down and only DB is up, then open configtool and open configuration                     editor (offline editor)

              b) Goto change mode & expand the tree as follows

              Cluster_config-->system-->custom_global--cfg-->services-->com.security.core.ume.service-               ->Propetysheet.properties

              c) Modify the properties as below

                      Property:- “ume.persistence.data_source_configuration” from value                                                      “dataSourceConfiguration_abap.xml” to “dataSourceConfiguration_database_only.xml”

                     Property:- “ume.superadmin.activated” from value “false” to “true”

                     Property:- “ume.superadmin.password” from value “[secure content]” to “<custom                                                 password>”

               d) Change to display mode and close the configuration editor, the changes will get saved.

               e) Close configtool and start JAVA instance, once JAVA is up, open NWA url and login to                      SAP as SAP* and with custom password which was provided in configtool.

               f)  Goto “Configuration” tab and select “Identity Management” and click button “configuration”, in the Data source tab set data source field to “ABAP System” and Data Source File Name to “dataSourceConfiguration_abap.xml” and in the ABAP system tab click the “UME RFC Destination” link and select “UMEBackendConnection” destination, update the system details of the target host and provide all relevant information.

               

                   g) Exit NWA and shutdown JAVA alone, then open configtool and  open configuration                            editor select change mode and goto
                   
         Cluster_config-->system custom_global-->cfg-->services-->com.sap.security.core.ume.service-           ->Propertysheet properties

                   And modify the property “ume.superadmin.activated” from value “true” to “ flase”

           
                   h) Restart JAVA and now you can see JAVA starting with modified UME backend.

11) Once JAVA is up, open the configuration tab from NWA and maintain the correct target hosts for all properties in “Destinations” (including SLD and other properties)

12) Goto “configuration-->”infrastructure”-->”JCo RFC Provider” and modify the target host  & repository configuration properties, then restart service.

13) Goto “configuration”--> “infrastructure”--> “SLD Data Supplier Configuration” and check the connectivity of SLD by pushing the data.


14) If the JAVA system is SAP EP, then goto url irj/portal, login with administrator/j2ee_admin user id & Select the “System Administration” tab and select “system Landscape” heading.

         Remove the old target host connections and then click on “SLD Actions”-->“Import Systems”, then click “Refresh from SLD” button and select the appropriate backend system and push it to selected systems, then carefully select the system type & SSO Logon Method (in our case its SAPLOGONTICKET) and provide all relevant details, click finish. You can see the target host visible in main page and has the status as trusted.

      15)     In NWA goto “Configuration”à”Security” à”Certificates & Keys”à”TicketKeystore” delete the existing “SAPLogonTicketKeypair” and its certificate then create new certificate manually with all relevant details.

16) In case of additional Add-ons present in JAVA  like ISA etc.. don't forget to change the hostname and instance number in XCM admin settings.

That's all finally restart JAVA instance and start using it.