Skip to end of metadata
Go to start of metadata

To connect to a Sybase database, the Sybase Middleware Client must be installed on the BI platform servers. The following table provides an overview of the steps we used in our pattern along with a checklist you can use to ensure you follow all of the required steps:

Complete these steps for both the lnxpb04 and lnxpb05 machines.

Sybase Middleware Client Configuration Checklist

Create a Sybase user on the server.

(tick)

Copy over the installation media for the Sybase client.

(tick)

Install the Sybase client software.

(tick)

Add required database server info to the Sybase interfaces file.

(tick)

Configure the sapbi user for Sybase client access.

(tick)

Test connectivity to the databases as sapbi.

(tick)

The following sections examine these tasks in more detail.

Creating a Sybase user on the server

In this section, you will create a user called sybase and then copy and extract the Sybase installation media.

  1. Log into lnxpb04 as root.

  2. Run the following commands as the root user to create a user called sybase and set the password to Sybase*123:
    > useradd -s /bin/bash sybase
    > passwd sybase

    Changing password for sybase.
    New Password: Sybase*123
    Reenter New Password: Sybase*123
    Password changed.


  3. Create a directory for the Sybase ASE 15.7 install files:
    > mkdir -p /opt/sybase/ASE15.7/Install

  4. Run the following commands to give sybase reading rights:
    > chown -R sybase /opt/sybase
    > chmod -R 755 /opt/sybase

  5. Copy the Sybase ASE 15.7 installation files to the directory in which you store your media.
    For example,
    > cp /mount/software/Sybase/ASE15.7.gz /opt/sybase/ASE15.7/Install

  6. Extract the installation media to that directory:
    > cd /opt/sybase/ASE15.7/Install
    > gunzip ./ASE15.7.gz

  7. Run the following commands to switch to the sybase user, and change to the Sybase ASE 15.7 install directory:
    > su - sybase
    > cd /opt/sybase/ASE15.7/Install

  8. Repeat steps 1-7 on lnxpb05.

You have now successfully created a user for the Sybase Client installation.

Installing Sybase ASE 15.7

In this section, you will install Sybase ASE on both BI platform servers.

The following steps were used in our pattern. For detailed installation instructions, see the Sybase ASE 15.7 Installation Guide for Linux.

  1. Log into lnxpb04 as root.

  2. Run the following command as the newly created sybase user to launch setup.bin from the Sybase installation directory:
    > ./setup.bin

  3. Press Enter to continue the installation.

  4. Enter the path to which you want to install. In our case, we are installing under /opt/sybase, which is the default. We receive a warning because the /opt/sybase directory already exists.

  5. Press Enter to continue if you are certain it is okay to overwrite the files in this directory.

  6. Choose option 3, then press Enter.
    Since we are using the ASE 15.7 Server Enterprise software installer and we need only the Open Client software installed, we will customize our installation.

  7. Select the options that ensure only the client, JDBC, ODBC, and Interactive SQL software are installed.

  8. Choose the version to install. You will want a full, licensed copy for production environments, but the Developer Edition should suffice for development environments.

  9. Read and accept the license agreement.

  10. Confirm that the selected options are correct and press Enter.

  11. Press Enter again to install.

  12. Choose to enable or disable the option to store ASE passwords, then press Enter.

  13. If you do not need to set up the Unified Agent, deselect it and then enter 0 to finish.

  14. Press Enter to exit the installer.

  15. Repeat steps 1-14 on lnxpb05.

You have successfully installed Sybase ASE.

Adding the Sybase Database Servers to the interfaces file

In this section, you will add database connection information to the interfaces file.

  1. Log into lnxpb04 as sybase.

  2. Navigate to the installation directory of the Sybase client. In our example, we run the following command:
    > cd /opt/sybase

  3. Run the following command to create or modify a file called interfaces:
    > vi ./interfaces

  4. Add the connection information for the CMS, Auditing, and Reporting Database Servers:
    CMS/Auditing Database Server

    cms57u05
         master tcp ether cmsdb05 5001
         query  tcp ether cmsdb05 5001

    Note that the information for the CMS Database Server connection is the same as the Auditing Database Server. You need to enter the above information only once for the two databases. Each database server still has its own users/schemas setup.


    Reporting Database Server
    Add the following lines below the CMS/Auditing Database Server entry.

    fun57u03
         master tcp ether repdb03 5000
         query tcp ether repdb03 5000

    In our pattern, we used cmsdb05 and repdb03 as our internal server names for the CMS/Auditing and Reporting Databases. Replace these values with your own internal server names for these databases.


    Save and close this file.

  5. Run the following command:
    > export LC_ALL=en_US.UTF-8

  6. Source the SYBASE.sh file for your shell instance to set up the proper environment variables to use isql. Run the following command:
    > . /opt/sybase/SYBASE.sh

  7. Test connectivity to the CMS/Auditing database by running the following command:
    > isql -S cms57u05 -U SAPCMS

  8. Enter the password when prompted, and then type the following:
    1> select @@version
    2> go

    You will see output similar to the following:

    ---------------------------------------------------------------------
    Adaptive Server Enterprise/15.7.0/EBF 19495 SMP /P/x86_64/Enterprise Linux/ase157/2820/64-bit/FBO/Fri Sep 16 00:54:35 2011
    (1 row affected)


  9. Test the same workflow with the Reporting database using fun57u03 instead of cms57u05:
    > isql -S fun57u05 -U SAPREPORTING

  10. Enter the password when prompted, and then type the following:
    1> select @@version
    2> go

    You will see output similar to the following:

    ---------------------------------------------------------------------
    Adaptive Server Enterprise/15.7.0/EBF 19495 SMP /P/x86_64/Enterprise Linux/ase157/2820/64-bit/FBO/Fri Sep 16 00:54:35 2011
    (1 row affected)


  11. Add any other databases into this interfaces file, such as additional reporting databases.

  12. Repeat steps 1-11 on lnxpb05.

You have successfully added the Sybase Database Servers to the interfaces file.

Configuring the sapbi user for Sybase Client access

In this section, you will modify the .bash_profile file to configure sapbi for Sybase Client access.

For more information on prerequisites for the Sybase Database, see section 3.2.2 Extra requirements for Sybase of the UNIX Business Intelligence Platform Installation Guide.

  1. Log into lnxpb04 as sapbi.

  2. Run the following command to edit the .bash_profile file:
    > vi ~/.bash_profile

  3. Add the following line to the end of the file:
    . /opt/sybase/SYBASE.sh
    

  4. Log off and log back in as sapbi to reload the profile.

  5. Run the following command to ensure that the SYBASE environment variables are now sourced upon logging in:
    > env |grep SYBASE

    You will see output similar to the following:

    SYBASE_JRE6_64=/opt/sybase/shared/JRE-6_0_24_64BIT
    SYBASE_JRE6_32=/opt/sybase/shared/JRE-6_0_24_32BIT
    SYBASE_JRE6=/opt/sybase/shared/JRE-6_0_24_64BIT
    SYBASE_UA=/opt/sybase/UAF-2_5
    SYBASE_OCS=OCS-15_0
    SYBASE=/opt/sybase
    SYBASE_PLATFORM=linux


  6. Repeat steps 1-5 on lnxpb05.

You have successfully configured the sapbi user for Sybase Client access.

Testing connectivity to the Sybase servers

In this section, you will verify connectivity to the databases.

  1. Log into lnxpb04 as sapbi.

  2. Run the following command to test that the sapbi user has connectivity to the CMS/Auditing database:
    > isql -S cms57u05 -U SAPCMS

  3. Enter the password when prompted, and then type the following:
    1> select @@version
    2> go

    You will see output similar to the following:

    ---------------------------------------------------------------------
    Adaptive Server Enterprise/15.7.0/EBF 19495 SMP /P/x86_64/Enterprise Linux/ase157/2820/64-bit/FBO/Fri Sep 16 00:54:35 2011
    (1 row affected)


  4. Run the following command to test that the sapbi user has connectivity to the Reporting database:
    > isql -S fun57u03 -U SAPREPORTING

  5. Enter the password when prompted, and then type the following:
    1> select @@version
    2> go

    You will see output similar to the following:

    ---------------------------------------------------------------------
    Adaptive Server Enterprise/15.7.0/EBF 19495 SMP /P/x86_64/Enterprise Linux/ase157/2820/64-bit/FBO/Fri Sep 16 00:54:35 2011
    (1 row affected)


  6. Repeat steps 1-5 on lnxpb05.
    If you see something similar to the above, then you have proper connectivity to the databases.

You have successfully tested connectivity to the Sybase servers and set up the Sybase middleware.

  • No labels