Introduction

Many of us had heard about Software Logistics Toolset and one of its features:: Dual-Stack Split Tool. People may misconceived by the name of Dual-Stack Split, their first thought was JAVA engine will be exported, separated and de-installed automatically by running SAPINST-alike tool. In reality, this tool runs in pragmatic way, better than we thought.

In this blog, I’ll talk about the differences between JAVA export with SAPINST & Dual-Stack Split, and how Dual-Stack Split works in stagger manner for export, import and de-installation of Java Stack.

 

Export & Import Java with current SAPINST

Export:

In recent and latest SAPINST, it no longer supports just JAVA schema export in dual-stack system, screen that allow us to select what schema to be exported in previous SAPINST version is gone into wind.

I’ll tried several options in current SAPINST for SAP Netweaver 7.0x, likes system copy -> Oracle -> Source System Export -> Central System -> Based on AS ABAP and AS Java -> Database and Central Instance Export and system copy -> Oracle -> Source System Export -> Central System -> Based on AS Java -> Database and Central Instance Export, deselect “Use Database specific tools”

You can no longer see above screen. As a result , SAPINST will export the whole database (ABAP + JAVA) instead of just JAVA schema and its file system contents. However, this still can be done, with the workaround below:

Ensure “Start Migration Monitor Manually” is checked:

Click “OK” to skip ABAP database export when below message prompts:

JAVA export completed approximately 10-30mins (vary depends on the size of Java schema and packages deployed)

Browse to location of export dump, you’ll see

i. LABELIDX.ASC – Entry consist of “ABAP” and “JAVA”

ii. ABAP – control files, eg: .EXT and .STR (not required for import, can be removed)

iii. JAVA- LABELIDX.ASC, LABEL.ASC, JDMP, SDM, TOOLS, DB, APPS and SOURCE.PROPERTIES.

 

Import 

 Importing Java dump from a double stack system into a Java Only system is not supported by SAPINST. However, you can follow Tom Cenens’ Blog by twisting the control.xml. SAP Netweaver BW 7.0x Dual Stack split using SAPinst export/import method

   

*Big credit to Tom for his contribution. Thanks.

 

Next, we’ll move to Dual-Stack Split Tool where I find it more practicable and feasible than SAPINST, most importantly, is supported by SAP.

 

 

Export, Import, De-Install Java with Dual-Stack Split Tool.

Please read and understand notes below for its use cases, scenarios, supported OS & DB, restrictions and known issues.

Note 855534 – Dual Stack and SAP Business Suite 7

Note 1655335 – Use Cases for Splitting Dual-Stack Systems

Note 1561421 – Dual-Stack Split (2.0) for Systems Based on SAP NetWeaver

 

Download Dual-Stack Split Guide:

http://service.sap.com/sltoolset -> Software Logistics Toolset 1.0 -> Dual-Stack Split

 

Download Dual-Stack Split tool:

Extract and run ./sapinst

 

Here, you can see all the functionalities provided by Dual-Stack Split.

   

i) Move Java Database – Java engine will be export along with its schema and file system contents,  remove from Dual-Stack system once it imported to target host successfully.

 

ii) Keep Database – Only Java engine and its file system contents are exported, where Java Schema remain intact. This is for MCOD.

 

Let’s focus on option “Move Java Database – Export Java Stack” in this blog.

 

Jload was called to perform DB export. You can monitor the progress with jload.log and Export.SDA.

Below files generated in export directory after export completed.

 

LABELIDX.ASC – entry with “ABAP” and “JAVA”

ABAP – empty folder

JAVA – LABELIDX.ASC, LABEL.ASC, JDMP, SDM, TOOLS, DB, APPS, SOURCE.PROPERTIES, with addition LUP and EXE.

 

In my next blog, I’ll cover Java import with SAPINST and Dual-Stack Split tool. FYI, “Remove Java Stack from Dual-Stack System” is basically the “Uninstall” function in SAPINST.

 

Conclusion:

 SAPINST and Dual-Stack Split tool are using the same method, basically, SAP just removed Java Schema Export features from SAPINST and incorporated to Dual-Stack Split. In addition, Dual-Stack Split tool officially supports import java database from dual-stack database into a Java only system.

 

With Dual-Stack Split tool, system copy for Java can easily perform with “Move Database” option without execute “Remove Java Stack from Dual-Stack system”. The advantages are Dual-Stack Split allows you to export, import to target host and perform the split only (not required for system copy purpose) after post-import verification tested successfully.