Integration of a SAP MaxDB into CCMS of an SAP System : Part 1

[DINESH_S]

In this blog provides detailed instructions on integrating various SAP MAXDB databases (Content Server(DMS) and liveCache) into Computing Center Management System (CCMS) of your SAP system.

Why Integrate with CCMS? 

CMS integration offers several benefits:

1. Solution Manager Monitoring: Include SAP MaxDB and liveCache databases in your Solution Manager monitoring for centralized oversight
2. Scheduled Administrative Tasks: Utilize the DBA planning calendar to schedule and automate administrative tasks for your SAP MaxDB databases.
3. DBA Cockpit Access: Gain access to the DBA Cockpit for these databases. This powerful tool offers various functionalities, including:
4. Database Analyzer: Analyze your database performance and identify potential bottlenecks.
5. Diagnosis Log Files: Access and review diagnosis log files for troubleshooting purposes.
6. Database Statistics: View detailed statistics such as table growth and identify the largest tables in your database.

The following Activities Required for Integration (if the system database is not SAP MaxDB).

1. SAP MaxDB Client Software Installation: Install the SAP MaxDB client software on the SAP application server. This step allows the application server to communicate with the SAP MaxDB database.
   Note: If your system database is already SAP MaxDB, this step is not necessary because the client software is already available on the application servers.
2. System Environment Extension (Optional): For systems other than SAP MaxDB, extend the system environment to include the SAP MaxDB software paths into the system path variables of the operating system user <sid>adm. This ensures the user has access to the necessary SAP MaxDB tools during the integration process.Note: If your system database is SAP MaxDB, this step is likely already configured correctly.
3. Registering SAP MaxDB/liveCache Databases in CCMS: Register your SAP MaxDB and/or liveCache databases in the CCMS. This step enables centralized monitoring and management of these databases within your SAP system.

This revision clarifies the purpose of each activity and emphasizes that some steps are only necessary if the system database isn't SAP MaxDB.

The SAP MaxDB client is not installed by default if you are running the DBACOCKPIT on an SAP system that uses a database other than SAP MaxDB. This client is necessary to connect to and manage SAP MaxDB databases from the application servers (Solution manager system).

How to Check for Client Software Installation:

Here's how to check if the SAP MaxDB client is installed on application servers of your system:

1. Use transaction code SE38 (or SA38 depending on your SAP GUI version).
2. In the program field, enter RSADA_CHECK_SERVERS.
3. Execute the program. It will check for the presence of the SAP MaxDB client on all application servers in the system.                                                                                                                        

The program will display results indicating whether the client is installed or not in the server.

      4. Check the check box checking client software and execute.

Maxdb Client Software not installed in the system, So follow the below steps install and configure CCMS.  

Proceed as follows:

1. Download the SAP MaxDB client software, Client Library and  from the SAP software download center.Follow the path: Databases (Access Downloads) -> Databases and Database Patches -> SAP MaxDB -> Database Patches. Select MaxDB 64-BIT -> MaxDB 7.9 64-BIT and most recent version for your operating system. aslo download SAPCAR XXXX.SAR file for extract Client software and Client library.
   File with name: MAXDBART<XXXX_XX-XXXXXXXX.SAR
   It is sufficient to download the Application Runtime Package.
2. Extract Application runtime package.
   
3. Install it as shown below and run the installation using command ./SDBINST
4. Set group to "sapsys" and owner to "sidadm" and continue. You can also create standard group and user but make sure that sidadm user has access to read client libraries . example If you are using solman system enter "sapsys" as a group and owner as solman "sidadm" user.
   
5. once client software installation completed. Add the environment value of client Software library files location.
   
   Independent Program Path : /sapdb/programs
   Independent Data Path : /sapdb/programs/bin
   
   LD_LIBRARY_PATH=/sapdb/clients/MAXDB/lib
   PATH=/sapdb/Programs/bin 
   
   
6. The environment must be adjusted to make sure that the running SAP system gets knowledge about the installed SAP MaxDB client. Adjust environment path variables OS level. 
   Unix/Linux
   - login as operating system user <sid>adm
   - extend settings for the environment variables PATH and LD_LIBRARY_PATH (LIBPATH, SHLIB_PATH) as follows:
   Linux: extend LD_LIBRARY_PATH with /sapdb/clients/<SID>/lib
   SUN Solaris: extend LD_LIBRARY_PATH with /sapdb/clients/<SID>/lib/lib64
   HPUX: extend SHLIB_PATH with /sapdb/clients/<SID>/lib/lib64
   AIX: extend LIBPATH with /sapdb/clients/<SID>/lib/lib64

7. To change the env move to the directory of "sidadm" user's folder location "/home/sidadm". Inside the folder location find the below files and include the path of the lib and programs/bin for MaxDB client on all application servers. just Logoff and login again from the shell so that the changes can take effect.

   File Name:
   .sapenv_<hostname>.csh
   .sapenv_<hostname>.sh
   

   .sapenv_<hostname>.csh
   setenv LD_LIBRARY_PATH exisiting lib path add maxdb lib path: /sapdb/clients/MAXDB/lib
   set path = ($path /sapdb/programs/bin)

   .sapenv_<hostname>.sh
   export LD_LIBRARY_PATH=existing lib path:/sapdb/clients/MAXDB/lib
   export PATH=$PATH:/sapdb/programs/bin

   
   Microsoft Windows
   - Login as operating system user <sid>adm
   - Open Environment Variables setting (enter in search field of Microsoft Windows search panel ENV and select Edit Environment Variables)
   - Change to the user specific section
   - Select variable Path
   - add following paths: <drive>:\sapdb\clients\<SID>\bin;<drive>:\sapdb\clients\<SID>\pgm;<drive>:\sapdb\programs\bin
   - If system wide variable Path contains any SAP MaxDB paths, remove them all.

8. Download the Maxdb database library ( this is different from Maxdb client libraries) , depending upon your kernel version and Uncar and copy the library dbsdbslib.so to the SAP kernel directory. 
   File with name: lib_dbsl_XXXXX.SAR

   In my case as I am running my sap application on linux environment , so we downloaded the linux compatible library.

   

9. Once the environment variables have been set, and the MaxDB library copied to the SAP kernel, for the changes to take effect, restart the application servers.

10.  Now again check the Client Software status.
    
    

    
11. As of now we are complete the pre requisites of CCMS integration next blog I will complete the remaining steps.
    Check Part to with following URL Integration of a SAP MaxDB into CCMS of an SAP System: Part 2 
    
    
    Thanks!
    DINESH S