Skip to Content

Technical Guide – Dual-Stack Split Tool vs Java Export SAPinst #sapadmin

January 16, 2012 | 1,511 Views |
 technology innovation
Follow

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.

To report this post you need to login first.

12 Comments

You must be Logged on to comment or reply to a post.

  1. Former Member
    Nice comparo Nic. Certainly demystifies the splitting of a dual-stack to a pure Java stack, as per SAP best-practice.

    Keep them coming! 🙂

    (0) 
  2. Tom Cenens
    Hello Nicholas

    Nice blog #sapadmin should read this.

    Thanks for the mention. My trick with the XML file was performed before the Dual-Stack Split Tool was available. I wouldn’t really recommend anyone to not use a SAP standard tool that is supported when possible.

    Kind regards

    Tom

    (0) 
  3. Francisco José Cebrián Pedreira

    Hello Nicholas.

    Very usefull blog. Right now I am doing the split procedure for my dual-stack BI system and I want to know if you have prepared the second part of your blog covering Java import and the Remove Java Stack part.

    We want to have two servers, one for abap stack and another for java stack. My question is if wich method cover the connection between them, move java database or keep database method?.

    Thanks again for your first blog and best regards.

    (0) 
    1. Nicholas Chang Post author

      Hi,

      Thanks for reading. I’ve the screenshot with me but got no time to touch up and put in description. For your case, you use move java dataase. you can import the java dump to a new server. and once your java is build up sucessfully, you can proceed to remove the java database from your dual stack system, and hence it’ll become pure abap stack.

      (0) 
      1. Francisco José Cebrián Pedreira

        Thanks so much for your quick response. Ok, I will proceed with move java database.

        Just one more question. My system is non-Unicode, in the Dual-Stack Split Guide version 1.2 it tells that split non-Unicode is not supported, but in the last one (version 1.4) it tells nothing about it. This means that now I can do the split and my abap stack will continue non-Unicode or I need to convert it first to Unicode.

        Best regards.

        (0) 
        1. Nicholas Chang Post author

          Hi Francisco,

          As for as i know, non-unicode is not supported on version 1.2 (during the time this blog was created).. and unsure with current latest version. Perhaps you can give it a try it the guide doesnt specially talk about non-unicode.

          Cheers,

          Nicholas Chang

          (0) 
  4. Former Member

    Hi All

    In my case I’ll use the tool from HP (smoth Transition) to export the ABAP and sapinst to export the java …. anyone ever tried this method?

    Thanks

    Douglas Santos

    (0) 
  5. Former Member

    Hi All,

    We are in process of Migrating our BW Landscape from AIX to Redhat.

    We are splitting the Central system into CI and DB(RAC) ,and have ABAP and JAVA App servers.

    CI – SCS and ASCS

    DB RAC – ABAP DB and Java Schema (MCOD)

    ABAP APP Servers – 4

    Java App Servers – 2

    As part of the project we would like to split DUAL STACK ABAP and JAVA

    Please advise
    a. Location to download the tool====>

    Following location doesnt have the tool. (version 2)

    http://service.sap.com/swdc -> Download -> Support Packages and
    Patches -> A – Z Index -> “S” -> SL TOOLSET.

    b. Migration Procedure in terms of sequence

    a. Global Host Prep. (target)
    b. Use Splitter tool to export Java from AIX to Redhat.
    c. Using splitter tool install Java on Redhat – this will install
    SCS,Java CI(SDM) and DB
    d. Export ABAP DB Instance (its 6 TB – We plan to use Distribution
    Monitor with SAPINST)
    e. Import ABAP DB Instance
    f. Install CI (ABAP) on Target – ————– not sure if it will work or I select ABAP only version

    g. Install ABAP App Servers

    h. Install Java App Servers

    Thanks
    Laxmichand

    (0) 

Leave a Reply