How to use Migration Monitor for Unicode Export/Import

How to use Migration Monitor for Unicode Export/Import

 

1. Introduction to  Migration Monitor
2. Migration Monitor – Basic Configuration
3. How to use Migration monitor
4. Conclusion.

    

1.     Introduction to Migration Monitor

 

Combined upgrade and Unicode conversion (CU&UC) is a preferred method to perform SAP release upgrade and Unicode conversion as one step method. It is quite common while upgrading SAP  R/3 4.6  or 4.7 or ECC 5.0 non-unicode system to the latest ECC 6.0 (with EHPx), you need to perform both upgrade as well as Unicode conversion. In this regard,  you should take the opportunity to perform both upgrade and Unicode conversion as one step approach rather than multi-step approach which will reduce your testing time and overall effort. One of the most important questions regarding CU&UC is the length of the downtime and how you can optimize this. Major chunk of the downtime will be determined by Unicode conversion export/import. SAP provides couple tools to optimize ( or perform ) Unicode conversion export/import; one of these tools is Migration Monitor. The biggest advantage of using Migration Monitor is parallel export/import which will reduce your total conversion time. However Migration Monitor can be used only for ABAP stack or ABAP part of dual stack, not for Java stack. Migration Monitor itself is not an executable or binary, it is consisting of set of scripts and parameter files; which is internally based on SAP tool – R3load (and all other related tools – R3szchk, R3ldctl and R3ta). Migration Monitor can be used as an integrated tool from SAP installer (SAPINST) or it can be used as an independent tool without SAPINST. In this blog I will mostly cover Migration Monitor as independent tool to perform Unicode Export/Import.

 

 

 

2.     Migration Monitor – Basic Configuration

 

     Migration Monitor configuration centers around optimization of scripts and parameter files. In the following section, I will cover Migration Monitor configuration for basic export/import functionality. In this regard, you need to configure primarily “export_monitor_cmd.property “ for export and “import_ monitor_cmd.property” for import specific settings . By configuring these two files along with orderBy.txt file, you can perform export/import.

 

 

Migration Monitor : various files and their purposes

Files / Scripts	Purpose
export_monitor_cmd.properties	Export property file. Set all parameters related to export.
import_ monitor_cmd. properties	Import property file. Set all parameters related to import.
orderBy.txt	Set the order of export / import packages, tables and split chunk of tables.
export_monitor.sh (Unix) export_monitor.bat (Windows)	Executable for export.
import_monitor.sh (Unix) import_monitor.sh (Windows )	Executable for import.

 

 

Example :

 

In the following examples I will cover three different configuration scenarios for parallel export/import For all three scenarios, I will assume the following conditions:

OS : Any unix ( AIX, Linux, Solaris, HPUX) or Windows.

Database : Oracle or IBM DB2 LUW

Export location : /ExportData/PRD  ( NAS or SAN file system attached to source system ). This must be accessible to Target system.

Net exchange Directory : /ExpImp/NetExchange ( A file system accessible to both source and target systems.)

Export Installation Directory ( on Source system ) : /usr/sap/PRD/MM/InstDirExport

Import Installation Directory ( on Target system ) : /usr/sap/PRD/MM/InstDirImport

Migration Monitor Executable Directory : /use/sap/PRD/MM/MMWKDir

 

 

Case 1 : Standard SAP package

 

i)                    Export Configuration : Configure export_monitor_cmd.properties file. Open the file in any editor and set the following properties:

 

            # Export Monitor options

# ----------------Server operating mode --------------------

server

#

# Exchange mode: ftp | net

# Here we are using NFS as net exchange directory, so set to net.

net

#

# List of export directories, separator on Windows ; on UNIX :---

exportDirs=/ExportData/PRD

 

# --------------------------Installation directory-------

# ------ Location of Export log for Migration monitor -----

installDir=/usr/sap/PRD/MM/InstDirExport

 

# Package order: name | file with package names

orderBy=/usr/sap/PRD/MM/MMWKDir/orderBy.txt

 

# ------DDL control file, default is DDL<DB_TYPE>.TPL-------

ddlFile=/usr/sap/PBW/MM/MMWKDir/DDLDB6.TPL

      # -------- For Oracle, TPL file is : DDLORA.TPL -------------

 

# File with mapping between DDL files and package names

ddlMap=

 

# Monitor timeout in seconds

monitorTimeout=180

 

# ---------Generation of task files: yes | no------------

tskFiles=yes

# -------------Code page for Unicode conversion -------------------

dataCodepage=4102

# ---- Based on DB & OS set this to either 4102 or 4101 ---------

 

# Additional R3load arguments for LOAD phase

loadArgs=-stop_on_error

 

# Number of parallel jobs. You can set to as per available CPU and memory

jobNum=10

 

# Network exchange directory

netExchangeDir=/ExpImp/NetExchange

 

 

 

Do not set any other parameter; leave as it is:

 

 

 

ii)                  Import configuration : Configure import_monitor_cmd.properties file. Open the file in any editor and set the following properties:

 

 

# Import Monitor options

# Common options

#

 

# -- List of import directories, separator on Windows ; on UNIX :---

importDirs=/ExportData/PRD

 

#  ------------ Installation directory --------------------------------

installDir=/usr/sap/PRD/MM/InstDirImport

 

# Package order: name | size | file with package names

orderBy=/usr/sap/PRD/MM/MMWKDir/orderBy.txt

      #

# DDL control file, default is DDL<DB_TYPE>.TPL

ddlFile=/usr/sap/PRD/MM/MMWKDir/DDLDB6.TPL

      #

# File with mapping between DDL files and package names

ddlMap=

# Monitor timeout in seconds

monitorTimeout=180

#

# R3load options

# Optional path of R3load executable

r3loadExe=

# Generation of task files: yes | no

tskFiles=yes

      #

# Inclusion of extent files: yes | no

extFiles=no

      #

# DB code page for the target database

dbCodepage=4102

      #

# R3load omit value, can contain only 'DTPIV' letters

omit=

      #

# Additional R3load arguments for TASK phase

taskArgs=

# Additional R3load arguments for LOAD phase

#

loadArgs=-c 1000 -stop_on_error -loadprocedure fast

      #

# Number of parallel import jobs

jobNum=10

      #

# Network exchange directory

netExchangeDir=/ExpImp/NetExchange

 

 

Do not set any other parameter; leave as it is:

 

 

 

iii)    Set the order of export and import : Configure orderBy.txt file.

 

SAP0000

SAPNTAB

SAPAPPL0

SAPAPPL1

SAPAPPL2

SAPCLUST

SAPDDIM

SAPPOOL

SAPSDIC

SAPDFACT

SAPSDOCU

SAPSLDEF

SAPSLEXC

SAPSLOAD

SAPSPROT

SAPSSDEF

SAPSSEXC

SAPUSER

SAPUSER1

SAPSSRC

SAPUSER1

SAPSLDEF

SAPSSDEF

 

These are SAP standard packages and all tables are part of any of these packages. If you like to know more about mapping of table to package, logon to SAP , use the t-code SE11 and enter the table name. Go to technical settings,  it will show you package name for that particular table.

Each package is associated with one or more tablespaces and mapping between package and tablespace can be found in TADB6, IADB6 tables in DB2 and TAORA, IAORA tables in Oracle. Sometime these packages are refer as “TABART” in Oracle and “DataClass” in DB2.

 

 

Case 2 : Move out bigger tables from standard SAP package

 

Move out some large tables from the standard SAP package. The following list of tables we will pull out of the standard package :

 

 

 

                        GLPCA  : Size 80 GB
                        BSIS : Size 70 GB
                        LIPS : Size 60 GB
                        COEP : Size 50 GB
                        LIPS : Size 40 GB
                        VBRP : Size 30 GB
                        VBAP : Size 20 GB

 

 

 

                        ( Pull out all tables bigger than 20 GB )
                       

There will be no changes to export and import config file - “export_monitor_cmd.property “ and “import_ monitor_cmd.property”; main changes will take place in orderBy.txt file.Configure orderBy.txt file as follows:

 

 

GLPCA

                       BSIS
                       LIPS
                       COEP
                       LIPS
                       VBRP
                       VBAP

SAP0000

SAPNTAB

SAPAPPL0

SAPAPPL1

SAPAPPL2

SAPCLUST

SAPDDIM

SAPPOOL

SAPSDIC

SAPDFACT

SAPSDOCU

SAPSLDEF

SAPSLEXC

SAPSLOAD

SAPSPROT

SAPSSDEF

SAPSSEXC

SAPUSER

SAPUSER1

SAPSSRC

SAPUSER1

SAPSLDEF

SAPSSDEF

 

 

That means put each individual pull-out table as an entry in OrderBy.txt file.

 

                       

Case 3 : Table splitting

 

Move out some large tables from the standard SAP package and split these tables using Java splitter or SAPINST. In this example I will split the following list of tables.

 

 

 

                        GLPCA  : Size 100 GB
                        BSIS : Size 80 GB
                        LIPS : Size 60 GB
                        COEP : Size 50 GB
                        LIPS : Size 40 GB
                        VBRP : Size 30 GB

 

 

                        ( Split all tables bigger than 20 GB ).

 

 

 

                        Create another file called : tablesplit.txt as follows :
                       
                        GLPCA %5
                        BSIS %4
                        LIPS %3
                        COEP %3
                        LIPS %2
                        VBRP %2

 

 

 

Pass this file as an input to Java splitter or to SAPINST for table splitting. Also put this file into Migration Monitor executable directory ( /use/sap/PRD/MM/MMWKDir ) in both source and target systems.

 

 

i)                    Export Configuration : There is no changes to export configuration file à export_monitor_cmd.property

ii)                  Import Configuration : Only one change if you database is IBM DB2 LUW.

 

loadArgs=-c 1000 -stop_on_error -loadprocedure fast LOAD

 

 

Because of split table you need to pass an additional argument called “LOAD”  along with “loadprocedure fast”.

 

 

iii)                Export/Import order : orderBy.txt file.

 

Configure the orderBy.txt file as the follows, where you need to mention each chunk of  split table along with standard package.

 

 

[GLPCA]

JobNum=1

GLPCA-1

GLPCA-2

GLPCA-3

GLPCA-4

GLPCA-5

[BSIS]

JobNum=1

BSIS-1

BSIS-2

BSIS-3

BSIS-4

.

.

.

 

            SAP0000

SAPNTAB

SAPAPPL0

SAPAPPL1

SAPAPPL2

SAPCLUST

SAPDDIM

SAPPOOL

SAPSDIC

SAPDFACT

SAPSDOCU

SAPSLDEF

SAPSLEXC

SAPSLOAD

SAPSPROT

SAPSSDEF

SAPSSEXC

SAPUSER

SAPUSER1

SAPSSRC

SAPUSER1

SAPSLDEF

SAPSSDEF

 

 

3.     How to use Migration Monitor

 

In this example I will show you how Migration Monitor can be used in conjunction with SAP installer – SAPINST.

 

 

i)                    Download the correct version of Migration Monitor and configure

 

 

Use the following OSS note and download the MIGMON_<rel>.SAR file from the SAP service market place:

 

               Support pack and Patches --> Additional Components à SYSTEM COPY TOOLS GEN --> SYSTEM COPY TOOLS GEN 1.0 --> # OS independent

 

Note 784118 - System Copy Tools for ABAP Systems

 

-- UNCAR  MIGMON_<rel>.SAR file on both source and target system’s executable directory (/use/sap/PRD/MM/MMWKDir )

-- Configure export and import config files and set the orderBy.txt as per the above configuration. Select any one of the above configuration scenarios ( Case 1, Case 2 or Case 3) as per your requirement.

 

ii)                  Perform export

 

          I am not going to discuss any pre-requisite tasks for export and I assume that system has been upgraded and all the necessary pre-  requisite  steps for      Unicode conversion have been completed. So next step is to start the Unicode export/import.

          Start the SAP installer (SAPINST ) on the source system and select the following options :

 

          

Fig 1 : SAPINST selection for export

               

 

Enter all generic input for SAPINST ( I am not going to show all screen ) and pay attention to the following important selections. When you select the option – “Start Migration Monitor Manually”, SAPINST will prompt you to start Migration Monitor for your Unicode export.

 

          

Fig 2 : Select Migration monitor option

 

You need to cancel SAPINST and start your Migration Monitor for export. Based on the code page mentioned in the export configuration file, export process will convert your data from non-unicode to Unicode .

 

          

Fig 3 : Option to start Migration Monitor Manually

 

 

Goto your Migration Monitor executable directory ( in this example - =/usr/sap/PRD/MM/MMWKDir ) and start the export process by executing export_monitor.sh ( or export_monitor.bat ) executable.

 

          

Fig4 : Start Migration Monitor  for export:

 

After completion of export, start SAPINST on the source system to complete the export process.

 

          

Fig 5 : Start SAPINST after completion of Migration Monitor – export

           
          

Fig 6 : Export completed successfully.

 

iii)                Perform Import

 

               To perform import you will have two options, either in-place import or parallel export/import.   Whenever      you      do      not      have      separate            host      for      import,      you      need      to perform export and import on the same host - called in-place import. For in-place (export/) import, once you completed the export part;  uninstall the exiting SAP, build your target system as Unicode enable system and perform import.For parallel export/import you will have separate host for both export and import. In this example I assumed that we will perform parallel export/import.Use SAPINST to install target system and choose the following option .

 

          

Fig 7 : Install Target system for import.

 

 

           Enter all required information for SAPINST. I will not show all screenshots, please pay special attention for the following “Migration Monitor” option.

 

          

Fig 8 : Option for Migration Monitor

 

 

SAPINST will prepare your system for import – it will install SAP kernel and database binary, build the template database and setup database connectivity. At one point of time SAPINST will prompt you to start Migration Monitor manually as the following. Cancel the SAPINST and start Migration Monitor Manually.

 

          

Fig 9 : SAPINST will prompt to start Migration Monitor Manually.

 

Goto your Migration Monitor executable directory ( in this example - =/usr/sap/PRD/MM/MMWKDir ) and start the import process by executing import_monitor.sh ( or import_monitor.bat ) executable.

 

         

Fig 10 : Start Migration Monitor for Import

 

              Parallel export/import :
          
         

Fig 11 : Parallel export/import

 

After completion of import, start SAPINST on the target system to complete Central Instance installation process.

 

          

Fig 12 : Start SAPINST after completion of import

 

          

Fig 13 : Central Instance build completed.

 

 

iv)                Migration monitor Logs

 

 

 

Export logs : Export installation directory. In this example

installDir à /usr/sap/PRD/MM/InstDirExport

 

Import logs : Export installation directory. In this example

installDir à /usr/sap/PRD/MM/InstDirImport

 

 

4. Conclusion

Use Migration Monitor with medium size database ( 500 GB to 1 TB) and when you have option to perform parallel export/import. For large database use Distribution Monitor.

Lock table overflow

In a system when ever a user performs any update on any table for that period of time a lock on that particular field of that table is created so that no other user can update that table as user one is doing update on that table.
And Suppose during the update user session get terminated due to some error then this lock entry remains on that field.

 

lock table overflow

 

A lock table overflow can occur if:

• The lock table is configured too small
• An application sets a large number of locks
• The update process is hanging and this is passing a lot of locks onto the update task.
• Running a  report with improper selection criteria (like very long time periods data pull) which sets so many locks & eventually lock table overflow occurs.

How to identify lock table overflow issue ?

 

 

In SM21 transaction log and ST22 dumps, if you find any error messages like LOCK_TABLE_OVERFLOW, Lock table overflow, Internal lock administration error it means there is a lock table overflow issue.By these dumps we can get the idea .

 

 

What is the parameter to be changed to increase lock table size in SAP ?

 

Parameter enque/table_size to be changed to increase or decrease lock table size using RZ10 transaction. Default value of this parameter is 32768. The min value that can be set is 4096 and max value is 102400. The unit for this parameter is KB.

 

 

How to resolve lock table overflow ?

 

• Increase the size of lock table i.e increase the parameter enque/table_size value using RZ10 transaction.

  To determine the optimal value for this parameter, you can check the maximum locks set so far in the history and the current number of locks set from SM12 -> Extras -> Statistics 

 

• Increase the number of enqueue workprocesses

improve performance of the BW system at database level

Performance of the BW system plays a key role in the business, as it directly impacts the user’s bandwidth. To solve performance issues there should be a standard life cycle maintained in every project at regular intervals to check validate and resolve the performance issues.

Some of the components which you can check to improve your query performance faster are:

At the data base level:

 

1.     1)  Data Model: A data model defines the way the objects are developed for example dimensions in an infocube...

a)      Make sure the dimensions in an infocube are as smaller as possible if you have individual characteristics

                          Example: Try not to include product and customer in a single dimension.

 

2.      2)  Query Definition: The way you define a query in Query designer also impacts the performance of the runtime of the query.

a)      Make sure that most of the calculations are done in transformations at infoprovider level rather than defining them in a query.

b)      Be sure that the InfoCube is compressed if you use non-cumulative key figures.

 

3.     3)   Aggregates: The main use of the aggregates is to fasten the response time of the query by reducing the amount of data which makes it a subset of an infocube.

      a)      Define aggregates for queries that have high data base read times.

      b)      If you have more aggregates the loading time also increases which effects the loading performance as roll up has to take place.

      c)       If the aggregates proposed by you or the system are too large and there is no good enough effect on the performance try using OLAP CACHE.

4.     4)  OLAPCache: It is just a buffer area where the data of the frequently used queries is stored, so whenever you execute or refresh a query instead  of  going to the database and fetching the data the system brings it from the OLAP CACHE.

a)      There are five Cache modes, to find them go to the tcode RSRT

b)      Enter your query name and click on properties tab

c)      After unchecking the infoprovider setting the Cache Mode will be highlighted where you can choose your Cache options.

1) Cache inactive,
2) Memory Cache without swapping
3) Memory Cache with swapping,
4) Cluster/Flatfile Cache per application server,
5) Cluster/Flatfile Cache cross-application server.

 

d) The stored OLAP CACHE data will be updated every time the new data is uploaded to the respective infoprovider also whenever the query is reactivated.

5. Pre-Calculated Web Templates: Pre-calculation is a process where you can distribute the workload of running the report when no one is using it and making it ready to access very fast when the users accesses the report. The main advantage is that it reduces the load on the server which makes the server to act faster to access data.

 

6. Compressing: Compressing an infocube transfer the data from f fact table to E fact table the requests are deleted and the records are aggregated which have the same keys
a) We have to compress all those requests as early as we can which are not likely to be deleted.
b) The same with the aggregates as well, compress them as soon as possible.
c) Compressing improves query performance of InfoCubes containing non-cumulative key figures significantly.

 

7) Indexes: We can define secondary indexes most of the secondary indexes have the negative impact on the data activation performance as they have to be maintained during the load
Example: We drop indexes before loading data into an infocube and rebuild them after loading

 

8. DBStatistics: We have to be certain that data base statistics are definitely maintained in the system with regular updating.
a) As most of the DBMS(database management systems) do not maintain the statistics for newly created infoproviders like infocubes we have to make sure that they are maintained before used for reporting.
b) If you have performance problems when building statistics use the alternate DBMS_STATS method.

I.            Please go through SAP note 351163 (Creating ORACLE DB statistics using DBMS_STATS).

II.            SAP note 129252 (ORACLE DB Statistics for BW tables) for details.

Create & Configure Local SLD on SAP NetWeaver 7.3 AS Java after Installation

This document describes, How to Create a Local System Landscape Directory (SLD) on Netweaver 7.3 Application Server Java, after performing a new installation of SAP Netweaver 7.3 Application Server Java.

 

Basically when you perform the installation of SAP Netweaver 7.3 AS JAVA along with other usage type i.e. EP + DI, you are prompted to choose about System Landscape Directory. You can either register your new SAP system in an existing central SLD or you may opt out of SLD at all.

 

 

But in some usage types, like that of DI (Development Infrastructure), where you need to have a system landscape directory and you do not have a central system landscape directory, what would you do in that situation?

 

You can, opt out of using SLD during the installation and then create a local SLD after finishing installation.

 

This document contains the steps that need to be done to Create a Local SLD in your new SAP System and perform subsequent SLD configuration tasks.

 

Log in to your SAP System's Landscape Directory by launching URL:<protocol>://<AppServer_Hostname>:5xx00/sld

 

As you log in for the first time you will see the below message, "SLD Not Setup. Configure the SLD in Administration first"

 

 

Note: If you also get an error, saying that "No Authorization for SLD", then you need to setup the SLD Authorizations first and assign it to the user with which you have logged in and then continue. You should log in with the J2EE Administrator user, as this user has SLD authorizations by default. Further you can refer SLD Guide for Netweaver 7.3 at the following link:http://help.sap.com/saphelp_nw73/helpdata/en/48/b7b38fecf26745e10000000a421937/content.htm?frameset=/en/48/B682DF96655295E10000000A42189B/frameset.htm to configure SLD User Authorizations.

 

To first configure SLD, click on Administration, next to Home.

 

As you can see above, it says to perform Initial Setup first, so begin by clicking on Initial Setup

 

Enter the desired Object Server Name, for help you can click on Information icon against it.

To keep it fair and simple, i chose to use the application server's hostname as my object server name as per below

 

Now you can click on Start Initial Setup, so that it begin's to set up Local SLD in your app server. Monitor the completion and then click on Administration to check the status of SLD. If SLD has been setup properly you shall be able to see: "SLD Running" as shown below

 

 

Now you can begin to Configure your SLD to mark completion.

 

Configuring SLD Security

 

To configure SLD Security, you need to assign SLD Security Roles and actions to users and user groups.

 

From SLD Home page, navigate to Administration --> Settings and click on tab Server Configuration

 

 

Click on Perform Role Mapping, and you should receive a confirmation as shown below

 

Confirm the action and SLD roles will be mapped to corresponding groups

 

 

Check the Write Protection Setting for SLD, by clicking on Configure in front of Write Protection.

 

Keep the default write protection: None

 

Performing Initial Data Import

The SLD server implements the Common Information Model (CIM). The SAP CIM model and SAP Component Information (CR_Content.zip) are automatically imported when the SLD is started for the first time during installation. However, since the CR_Content.zip file contains all SAP Components that are available, the content of this file increases over time to include information about new components, such as new releases and support packages. So you must update the latest content in SLD. You can download the most up-to-date files on SAP Service Market Place. Refer SAP Note 669669 for downloading the latest CR Content Files from SAP Service Market Place.

 

To download the appropriate files, you will also need to check your SLD's Data Model and CR Version. To do so, navigate from SLD Home to Administration --> Details then select tab stripe Data

 

 

As per the above screen shot, this is my SLD version after a new Installation.

• CIM Model Version => 1.6.34
• CR Content Version => SAP_CR 8,8 (Released 2012-12-10)

 

Since then, the SLD components have been updated so, I will import the latest CIM Model and CR Content from SAP Service Market Place.

 

As per the SAP Note 669669, for my above CIM Model Version and CR Content Version, I have downloaded the following CR Delta files:

1. CRDelta81611_0-20009730.ZIP
2. CRDelta81612_0-20009730.ZIP
3. CRDelta91601_0-20010858.ZIP
4. CRDelta91602_0-20010858.ZIP

 

And the latest CIM Model, which is located under SAP CR CONTENT UP TO ... (the highest available year) and has the file name cimsap....zip.

If there are several of these files, use the latest one. I selected cimsap91602 0-20010858.zip (SP02 for SAP CR CONTENT UP TO 2013)

 

So, now you can download all the files i.e. CR Delta Files and the latest CIM Model.

 

To begin import, you first need to import the Model i.e. cimsap....zip

 

To import, navigate from SLD Home to Administration --> Import

 

 

Click on Choose File and select the downloaded latest CIM Model and click on Import

 

 

 

Well, as you may see above your SLD's CIM Model will be upgraded from version 1.6.34 to 1.6.36. Click on Continue Import. You will see the progress in the status bar. Once the import is completed, you shall receive a confirmation as per below.

 

 

 

Your CIM Model version has been successfully updated now, you can check back by navigating to Administration --> Details --> Data.

 

 

Next, you can import the CR Content Update Delta files sequentially, one after other:

 

1. CRDelta81611_0-20009730.ZIP
2. CRDelta81612_0-20009730.ZIP
3. CRDelta91601_0-20010858.ZIP
4. CRDelta91602_0-20010858.ZIP

 

Importing CRDelta81611_0-20009730.ZIP

 

 

 

Click on Continue Import and once the import completes, you can check back the new version of your CR Content

 

Similarly, import the remaining delta CR Updates to upgrade it to the latest level, and check back the latest CR Content version in your SLD.

 

As per above, your CIM Model version is updated to latest CIM Model 1.6.36 & CR Content has been update to 9.2,being the latest.

 

You have now successfully completed the Import Data step.

 

Now, you need to do one final step i.e. Automated Java Functional Configuration

 

Java Functional Configuration

 

You use the functional unit configuration tool to perform the initial setup of Java Functional Units.

 

To call the Java Functional Unit tool, launch URL http://<host>:<httpport>/sld/fun and log in with appropriate Administrator user.

 

From the list of installed functional units, select those you want to configure. If the configuration of a functional unit requires additional functional units, the tool selects them automatically. You can select multiple functional units by pressing Ctrl or Shift.

 

You can performing Automated configuration, if at least one automated configuration task is available in your selection of functional units i.e. Enable Automatically button is available.

 

Select the required functional units and click on Enable Automatically (Note: The initial status is shown disabled)

 

 

A pop up configuration wizard screen appears. Follow the configuration wizard. The tool makes the necessary settings and sets the configuration task to status enabled after it has finished successfully.

 

 

Provide the required inputs and follow the wizard, it will automatically do all the necesarry configurations.

 

 

Once the configuration completes successfully, you can refresh the Main Functional Unit Configuration Window to check the status. The status should be Enabled now.

 

 

With this, you have successfully completed the Installation & Configuration of Local SLD on SAP Netweaver 7.3 Application Server Java after a new installation.