Aperi Home >

Aperi Storage Manager Installation Instructions

Welcome to Aperi Storage Manager. Aperi Storage Manager is open-standards-based storage infrastructure software that can centralize, automate, and simplify the management of complex and heterogeneous storage environments. Aperi Storage Manager can help to improve storage capacity utilization, administrative efficiency, and provide users with greater flexibility in the way they manage their storage environments.

Use the following instructions to learn how to install and initially configure Aperi Storage Manager. See the Aperi Storage Manager User's Guide and online help for information about how to use the product once it is installed.

Contents

1. Plan the deployment

Aperi Storage Manager is an integrated set of software components that provides end-to-end storage management, from the host and application to the target storage device in a heterogeneous platform environment. These components include the following:

User Interface
The user interface enables you to use Aperi Storage Manager to manage your storage environment.
Data Server
This component is the control point for product scheduling functions, configuration, event information, reporting, and GUI support. It coordinates communication and data collection with agents that gather storage demographics and populate the database with results.
Device Server
This component discovers and gathers information for storage subsystems and SAN fabrics. It coordinates communication and data collection from agents that probe SAN fabrics.
Agents
Agents gather host, application, and SAN fabric information and send this information to the Data server or Device server.
Database Repository
A single database instance serves as the repository for data collected by agents. The Aperi database repository can run under either of the following relational database systems:
  • Apache Derby
  • DB2 8 for Linux UNIX and Windows.
Keep in mind the following strategies when installing these components:

The following figure shows a sample configuration of Aperi Storage Manager components:

2. Check install requirements

Platform requirements
You must be running Windows 2000, XP, or 2003 and have approximately 100MB of available disk space. Red Hat Enterprise Linux AS Version 3.0 IBM Eserver xSeries is also supported.

Server requirements (recommended)

Agent requirements (recommended)

Administrative group

The Aperi Storage Manager environment supports role-based security. Operating system groups are associated with predefined roles. When a user ID is authenticated to Aperi through the GUI, membership in an operating system group determines the authorization level. By default, Aperi uses the following groups to determine administrative authority:

If these default administrative groups do not match a group in your environment, or you want to use a different group for the Aperi administrator role, you can edit the adminGroup parameter in the server.config configuration file after a successful installation. Click here for more information about the adminGroup parameter and server.config configuration file.


3. Plan for the database repository

Use this section to determine what relational database to use as the database repository for Aperi. There are two relational databases available for use with Aperi:

Perform the following steps to download and set up DB2 for use with Aperi Storage Manager:

  1. Download DB2. You can download DB2 from here.
  2. Install DB2 using the defaul settings. Note the db2admin password that you choose during the installation.
  3. Use the DB2 Control Center to create a database called 'Aperi'.
  4. Continue to the next section Install the Aperi Storage Manager files.

4. Install the Aperi Storage Manager files

Install the Aperi Storage Manager files on machines:

Perform the following steps to install the server, agent, or GUI on a machine:

  1. Locate the Aperi Storage Manager .zip file.
  2. Place the .zip file in the directory where you want to install the product.
  3. Use an unzipping tool to unzip the file.
  4. Download required components that are not distributed with the Aperi Storage Manager .zip file. Perform the following steps to download these required components:

    • Download JavaHelp 1.1.3.
      1. Go to http://java.sun.com/products/javahelp/download_binary.html.
      2. Click the Download button under the JavaHelp 1.1.3 (Zip) section.
      3. Click Accept License Agreement.
      4. Click the down arrow to download the javahelp-1_1_3.zip file.
      5. Unzip the contents of javahelp-1_1_3.zip.
      6. Locate the \jh1.1.3\javahelp\lib\jh.jar file in the directory where you unzipped javahelp-1_1_3.zip.
      7. Copy jh.jar into each of the following directories:
        • agent\plugins\javax.help_1.0.0
        • datasvr\plugins\javax.help_1.0.0
        • devsvr\plugins\javax.help_1.0.0
        • gui\plugins\javax.help_1.0.0

    • Download Java Enterprise Edition 1.3.
      1. Go to http://java.sun.com/j2ee/1.3/download.html#sdk.
      2. Click Software & Documentation link in the 1.3.1 FCS Release January 31, 2002 section.
      3. Click the Download button under the Download the Software for the Java 2 SDK, Enterprise Edition 1.3.1 section.
      4. Click Accept License Agreement.
      5. Click the down arrow to download the j2sdkee-1_3_1-win.exe.
      6. Run the j2sdkee-1_3_1-win.exe file.
      7. Copy j2ee.jar into each of the following directories:
        • agent\plugins\javax.j2ee_1.0.0
        • datasvr\plugins\javax.j2ee_1.0.0
        • devsvr\plugins\javax.j2ee_1.0.0
        • gui\plugins\javax.j2ee_1.0.0

  5. Download additional required components manually or use the Configurator to perform the download. Skip to the Configure Aperi Storage Manager section to have the Configurator automatically download the required components. If the installation of Aperi is performed behind a firewall, or the ability to automate the download of third-party libraries is prohibited in your environment, perform the following steps to download the files manually:

    • Download Apache Xerces 2.8.0.
      1. Go to http://archive.apache.org/dist/xml/xerces-j/binaries.
      2. Click Xerces-j-bin.2.8.0.jar and download the file.
      3. Unzip the file.
      4. From the unzipped file, copy xercesImpl.jar and xml-apis.jar into
        • agent\plugins\org.apache.xerces_1.0.0
        • datasvr\plugins\org.apache.xerces_1.0.0
        • devsvr\plugins\org.apache.xerces_1.0.0
        • gui\plugins\org.apache.xerces_1.0.0

    • Download SBLIM CIM Client 1.3.
      1. Go to http://sourceforge.net/project/showfiles.php?group_id=128809.
      2. Click Download next to sblim-cim-client and download the sblim-cim-client-1.3-bin.zip file.
      3. Unzip the contents of sblim-cim-client-1.3-bin.zip.
      4. Copy sblimCIMClient.jar into
        • agent\plugins\org.sblim.cim.client_1.0.0
        • datasvr\plugins\org.sblim.cim.client_1.0.0
        • devsvr\plugins\org.sblim.cim.client_1.0.0
        • gui\plugins\org.sblim.cim.client_1.0.0

      5. Copy sblimSLPClient.jar into
        • agent\plugins\org.sblim.slp_1.0.0
        • datasvr\plugins\org.sblim.slp_1.0.0
        • devsvr\plugins\org.sblim.slp_1.0.0
        • gui\plugins\org.sblim.slp_1.0.0

    • Download the SNIA HBA binaries.
      1. Go to http://sourceforge.net/project/downloading.php?group_id=35200&filename=hbaapi-bin.zip.
      2. Save the download (hbaapi-bin.zip) to disk.
      3. Unzip the contents of hbaapi-bin.zip.
      4. Copy hbaapi-bin\sniahbaapi.dll to [aperi_install_directory]\lib\w32-ix86\
      5. Copy hbaapi-bin\libhbaapi.so to [aperi_install_directory]\lib\linux-ix86\

  6. If you plan to use DB2 as the database repository, continue to the next step. If you plan to use Apache Derby as the database repository, continue to the Configure Aperi Storage Manager section for information about how to set up the components you want to run on the machine where you unzipped the files.
  7. Copy the DB2 JDBC driver into the directory where you unzipped the Aperi Storage Manager files. To do this perform the following steps:
    1. Locate the DB2 JDBC driver that was installed during the DB2 installation. On Windows, check C:\Program Files\IBM\SQLLIB\Java. The filenames are db2jcc.jar and db2jcc_license_cu.jar.
    2. Copy the driver files to /plugins/org.eclipse.aperi.db_1.0.0.
    3. Go to /plugins/org.eclipse.aperi.db_1.0.0/MANIFEST.
    4. Delete MANIFEST.MF.
    5. Rename DB2-MANIFEST.MF to MANIFEST.MF.
  8. Continue to the Configure Aperi Storage Manager section for information about how to set up the components you want to run on the machine where you unzipped the files.

5. Configure Aperi Storage Manager

Use the Configurator tool to set up Aperi Storage Manager components on the machine where you unzipped the product. The package that you unzipped contains the run-time files for all of Aperi Storage Manager's main components: a host-based agent, a server, and a GUI. You do not have to configure all the components on each machine; rather, use the Configurator to set up only the components that you want to run on a particular machine.

Note: Keep in mind that you must configure the server on one machine, called the "server host". The server host normally also has the agent and GUI configured on it.

The Configurator will ask you several questions to help you configure Aperi Storage Manager for your environment. In most cases, the questions have default values, which are displayed in square brackets []. To answer a question, type your answer and press Enter. If there is a default answer and you want to accept it, just press Enter.

For example, if the Configurator displays:

Server port [9549]:

Press Enter to accept 9549 as the value for the server port. You can also type a different value, such as:

Server port [9549]: 12345

When answering Yes/No questions, any string starting with "Y" or "y" is interpreted as Yes, and any other non-blank string is interpreted as No.

The following instructions are Windows specific; however, the Configurator does run on Linux. The basic process is the same for both Windows and Linux, although the syntax for changing directories and setting your PATH will be different.

5.1 Start the Configurator

  1. Make sure you have a Java Runtime Environment (JRE) from IBM or Sun 1.5 installed on your machine. To check for Java on a machine, start a command prompt window (Start > Programs > Accessories > Command Prompt) and type java -version from a command line.

    If you see text similar to the following then continue to step 2:

    java version "1.5.0_07"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
    Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode)

    If you see text like the following, download the JRE from the IBM or Sun (http://java.sun.com/j2se/1.5.0/download.jsp) web sites before continuing:

    'java' is not recognized as an internal or external command, operable program or batch file.

  2. Set java into your PATH by typing the following at the command prompt:

    set path=%path%;C:\path_to_java_directory\jdk1.5.0_07\bin

    where     path_to_java_directory represents the directory where the JRE is installed.

    Note: You can also edit the cfgaperi.bat file or the System Path to contain the JRE pathname.

  3. Change to the <aperi_install_directory>\configure subdirectory where you installed the Aperi Storage Manager files. For example, type cd c:\aperi\configure and press Enter.

  4. Determine whether you want to run the Configurator in "easy" or "regular" mode:
    • Easy - the Configurator will choose all the default values for your Aperi installation.
    • Regular - you can review and modify all the configuration options for your Aperi installation.

    To start the Configurator in regular mode, type cfgaperi and press Enter. Continue to the next section Use the Configurator (regular mode).
    Note: run the Configurator in regular mode when using DB2 as the Aperi database repository.

    To start the Configurator in easy mode, type cfgaperi easy and press Enter. Skip to Use the Configurator (easy mode).

    Note: The Java path that you set in step 2 has two purposes: 1) it is used to run the Configurator, and 2 ) it is stored in the Aperi startup scripts and used to run Aperi Storage Manager. This means that if you later uninstall the Java with this path, you won't be able to start Aperi Storage Manager until you reconfigure Aperi.

5.2 Use the Configurator (regular mode)

When the Configurator starts the following message will appear:

Aperi Storage Manager Configuration
This program will ask you a series of questions, then configure Aperi
Default values are displayed in [square brackets].

Checking Java installation...passed.

Note: The Configurator displays a warning message if you are not running Java 1.5.

  1. Indicate which components you want to configure on the machine. If this is your first time, or you wish to do things "normally", accept the defaults and answer Yes (press Enter for each one) to the following questions:

    The Aperi Storage Manager consists of three major components:
    The host-based agent, the server, and the GUI.
    You can configure any or all of these to run on this computer.

    Which components do you want to configure? Answer with Yes or No.

    Agent [Yes]?
    Server [Yes]?
    GUI [Yes]?

    Your answers determine what questions you get asked next, as some questions are agent-, server-, or GUI-specific. You are not asked questions that pertain to components you are not configuring.

    • Continue to the next step if you are configuring all components.
    • Continue to the next step if you are configuring an agent.
    • Skip to step 3 if you are configuring a server only.
    • Skip to step 10 if you are configuring the GUI only.

  2. (agent question) If you are configuring the agent, you are asked to supply port values for the Fabric and Filesystem subagents. The subagents will open sockets on these ports for communication with the server. You may choose any valid port number (0..65535) although, of course, you should not choose ports that are already in use. The only reason to override the defaults for these two questions is when you know the default values are already in use.

    Enter values to configure the agent.

    Fabric subagent port [9570]:
    Filesystem subagent port [9550]:

  3. (server and agent) Configure the Device server.
    • If you answered Yes to the server question in step 1, the following will appear:

      Enter values to configure the device server.

    • If you're configuring the agent but answered No to the server question in step 1, the following will appear:

      Enter values to configure how the agent communicates with the device server.
      These must match how the device server is configured.

    Either way, you will be asked the same set of questions about the Device server. If you are configuring both the server and the agent, your answers will be passed both to the server (to configure itself) and to the agent (to configure how the agent talks to the server). If you are just configuring the agent (because the server is on a different machine), you must enter values that match however you configured that server.

  4. (server and agent) Enter the hostname, port, and password for the Device server.

    Hostname [aperi-srm1]:
    Port [9000]:
    Password:

    Field Name

    Description

    Hostname [aperi-srm1]

    Enter the name of the machine on which the Aperi server is (or will be) running.

    If you are configuring the server on the current machine, enter that machine's name. If you're configuring an agent to talk to a remote server, then enter the name of the remote server's machine.

    The Configurator supplies the current machine's name as a default. There are three reasons to override this default:

    • Use "localhost" as the hostname if you install all Aperi components on a single machine and restrict access so that Aperi components on remote machines cannot connect to this installation. This will prevent the Aperi server and agent from answering the phone for remote connections.
    • If you are configuring an agent or GUI that is remote from its server, you will have to enter the remote server's name here. Enter a name that is resolvable on this host: depending on how your local machine and network are configured, you might be able to use a short name like "server1", or you might need a fully-qualified name like "server1.internal.org".
    • If your machine has multiple network interfaces with different hostnames for each interface and the Aperi Configurator chose the wrong name to use as a default.

    Port [9000]

    Enter the port number that the Device Server will use for communication. If you are configuring the server locally, choose any free port; if you're configuring an agent to connect to a remote server, choose the port number you configured for that server.

    Password

    Enter the "host authentication" password that should be used to protect access to the Device server. Choose any non-blank value. Note that it will be displayed in this command prompt window in plain text, although the Configurator encrypts it before storing it in the configuration files it generates.

  5. (server only) Enter the port and HTTP port for the Data server.

    Enter values to configure the data server.

    Port [9549]:
    HTTP Port [9001]:

    Enter values to configure Derby.

    Port [1527]:

    Field Name

    Description

    Port [9549]

    Enter the port number that the Data server will use for communication. If you are configuring the server locally, choose any free port; if you're configuring an agent to connect to a remote server, choose the port number you configured for that server.

    HTTP Port [9001] Enter a port that can be used by the Data server. Ensure that this port is open and not in use.

    Port [1527]

    Enter the port number that Apache Derby will use for communication. Apache Derby is included with Aperi Storage Manager and acts as the database repository for the data gathered by agents.

  6. Download some of the necessary 3rd party libraries.

    Download third party software [Yes]?

    Please select a mirror for Jetty:
    0. [United States] Indiana University (http)
    1. [United States] OSU Open Source Lab (http)
    2. [United States] Georgia Tech. Software Library (http)
    3. [Israel] NSA Internet & Security Ltd. (http)
    4. [Japan] Japan Advanced Institute of Science and Technology (http)
    5. [Korea, Republic Of] GameVil.com (http)
    6. [Australia] Pacific Internet (http)
    7. [Czech Republic] Sillicon Hill Mirror (http)
    8. [Germany] Innoopract Informationssysteme GmbH (http)
    9. [Germany] University of Applied Sciences Esslingen (http)
    10. [Greece] National Technical University of Athens (http)
    11. [Hungary] Gabriel Consulting (http)
    12. [Italy] GARR/CILEA (http)
    13. [Romania] Romanian Education Network (http)
    14. [Switzerland] SWITCHmirror (http)
    15. [Turkey] Tubitak-Ulakbim (http)
    16. [United Kingdom] UK Mirror Service (http)
    Mirror [0]:

    Please select a mirror for Apache Commons Logging:
    0. [United States] Indiana University (http)
    1. [United States] Georgia Tech. Software Library (http)
    2. [United States] OSU Open Source Lab (http)
    3. [Israel] NSA Internet & Security Ltd. (http)
    4. [Japan] Japan Advanced Institute of Science and Technology (http)
    5. [Korea, Republic Of] GameVil.com (http)
    6. [Australia] Pacific Internet (http)
    7. [Czech Republic] Sillicon Hill Mirror (http)
    8. [Germany] Innoopract Informationssysteme GmbH (http)
    9. [Germany] University of Applied Sciences Esslingen (http)
    10. [Greece] National Technical University of Athens (http)
    11. [Hungary] Gabriel Consulting (http)
    12. [Italy] GARR/CILEA (http)
    13. [Romania] Romanian Education Network (http)
    14. [Switzerland] SWITCHmirror (http)
    15. [Turkey] Tubitak-Ulakbim (http)
    16. [United Kingdom] UK Mirror Service (http)
    Mirror [0]:

    Please select a mirror for Java 2.4 Servlet API:
    0. [United States] Georgia Tech. Software Library (http)
    1. [United States] OSU Open Source Lab (http)
    2. [United States] Indiana University (http)
    3. [Israel] NSA Internet & Security Ltd. (http)
    4. [Japan] Japan Advanced Institute of Science and Technology (http)
    5. [Korea, Republic Of] GameVil.com (http)
    6. [Australia] Pacific Internet (http)
    7. [Czech Republic] Sillicon Hill Mirror (http)
    8. [Germany] Innoopract Informationssysteme GmbH (http)
    9. [Germany] University of Applied Sciences Esslingen (http)
    10. [Greece] National Technical University of Athens (http)
    11. [Hungary] Gabriel Consulting (http)
    12. [Italy] GARR/CILEA (http)
    13. [Romania] Romanian Education Network (http)
    14. [Switzerland] SWITCHmirror (http)
    15. [Turkey] Tubitak-Ulakbim (http)
    16. [United Kingdom] UK Mirror Service (http)
    Mirror [0]:

    Downloading the third party software.
    Downloads complete.

    =======
  7. Indicate whether you want to use Apache Derby as the database repository.

    Do you want to use Derby as the Aperi repository [Yes]?

    Press Enter to select Apache Derby and continue to Complete the configuration. If you want to use DB2 as the database repository, type No, press Enter, and continue to the next step.

  8. Indicate that you want to use DB2 as the database repository. If you plan to use DB2, make sure you complete the steps in Plan for DB2 as the database repository before continuing.

    Do you want to use IBM DB2 as the Aperi repository [Yes]?

    Press Enter to select IBM DB2 and continue to the next step.

  9. Indicate that DB2 is ready for configuration.

    DB2 should installed and running with database created named 'Aperi'.
    You also need to have installed the com.ibm.db2 plugin.
    Is DB2 ready [Yes]?

    Press Enter if DB2 is ready. If DB2 is not ready, perform the steps described in Plan for DB2 as the database repository before continuing.

  10. Enter values to configure DB2.

    Port [50000]: DB2
    username [db2admin]:
    Password:

    Field Name

    Description

    Port [50000]

    Enter the port number that DB2 will use for communication.

    DB2 username [db2admin] Enter the user ID that you indicated in Plan for DB2 as the database repository. db2admin is the default user ID with administrative authority that DB2 creates during its installation.

    Password

    Enter the password for the user ID indicated in the DB2 username prompt.


    Continue to Complete the configuration.

  11. (GUI only) Enter values to configure how the GUI communicates with the Data server. These must match how the Data server is configured.

    Enter values to configure the data server.

    Hostname [aperi-srm1]:
    Port [9549]:

    Field Name

    Description

    Hostname [tpc-d9-int]

    Enter the name of the machine on which the Aperi server is running. The GUI will use this name to connect to the server.

    Port [1527]

    Enter the port number on which the server is listening for requests..


5.3 Use the Configurator (easy mode)

When the Configurator starts the following message will appear:

Aperi Storage Manager Configuration
This program will ask you a series of questions, then configure Aperi
Default values are displayed in [square brackets].

Checking Java installation...passed.

If you chose to run the Configurator in easy mode, then default values are chosen for you for all the configuration questions. The Configurator will assume you are configuring all three components on the local machine. The hostname as determined by the Configurator will be used. Port number defaults are:

See 4.2 Use the Configurator (regular mode) for an explanation of these configuration questions.

5.4 Complete the configuration

After answering the configuration questions in regular mode or running in easy mode, the Configurator performs the actual configuration of the Aperi components. This involves setting values in properties files as well as generating startup scripts for the various components. The names of the properties files and the startup scripts are displayed for you in the command prompt window. Only information about the components you chose to configure will appear in the messages. 

Ready to configure. 
   
   Configuring the agent... 
   ../agent/configuration/setup.properties 
   ../agent/configuration/agent.config 
   ../agent/agent.bat 
   
   Configuring database_name... 
   ../db/aperi-schema.bat OR
   ../derby/aperi-schema.bat 

   Configuring the device server... 
   devsvr/configuration/setup.properties 
   devsvr/configuration/tsnmdbparms.properties 
   ../devsvr/devsvr.bat 
   
   Configuring the data server... 
    datasvr/configuration/server.config 
    ../datasvr/datasvr.bat 
   
   Configuring the gui... 
   ../gui/gui.bat 
   
   Generating start script... 
   aperi.bat

The Configurator then generates a GUID (or UUID) for your host and stores it in guid.txt in the root directory of your installation. The GUID is also displayed:

Generating GUID for this host... 
GUID is 2a185e9d-07ed-40c9-a120-87b9a789143f 
Storing in c:\aperi\guid.txt

Next, the Configurator creates the Aperi schema. If you are using Derby for the database repository, the Configurator will start the Apache Derby server and run the aperi-schema script it created in the <aperi_install_directory>\derby subdirectory. This script creates the schema specified by 'Alter' files in the <aperi_install_directory>\derby\schema directory. The output from aperi-schema is displayed for you to inspect; again, you will have to look and see if it seems to have succeeded.

The following shows a successful database installation:

 Running .\aperi-schema.bat
 ---- 
   Database installation successful. 
 ---- 
   The output above should indicate that the schema was created 
   successfully on your system. If there was an error, 
   Aperi will not function correctly. Consult the installation 
   documentation for more information.

Note that Derby stores the database in a subdirectory of the derby directory. Keep this in mind if you want to back it up, copy it, or delete it. Deleting the database directory is the Derby equivalent of DROP DATABASE. Also, the Configurator generates derby\aperi-ij.bat, which you can run in a Command Prompt window to enter interactive SQL statements against the Derby server.

If the schema already exists, the Configurator will exit with an error message. If you wish, you can delete derby\Aperi and rerun the Configurator.

Upon completing the configuration of all the selected components, the following message is displayed:

   To bring up the Aperi server and agent, run aperi.bat. 
   To start the GUI, run gui/gui.bat. 
   Aperi configuration is complete.

5.5 Edit configuration files

Use a text editor to edit configuration files to further customize Aperi Storage Manager according to the standards at your site. These files reside in subdirectories under the \aperi_install_directory\ directory, where aperi_install_directory represents the directory where you installed Aperi. Use the information in the following table to learn about the parameters that you can edit in these configuration files:

Configuration file

Location and parameter descriptions

server.config

Edit this file to configure the Data server in your environment.

Location of file: \aperi_install_directory\datasvr\configuration\

[controller]

  • name: the name of the Data server (host computer name).
  • port: Port on which the server listens for requests (9549).
  • maxConnections: Maximum number of concurrent sockets that the server will open (500).
  • routerThreads: Number of threads redirect incoming requests to the appropriate service provider (1).
  • serviceThreads: Number of threads to allocate for the Server internal service provider (2).
  • agentErrorLimit: Number of consecutive attempts to reach an agent before the agent is displayed as DOWN. When an agent is in this state, no attempts to connect are made until either the agent contacts the Server or the agent status is manually changed to UP (3).
  • adminGroup: Name of the group a user must be a member of in order to perform administrative functions from the Graphic User Interface. The default administrative groups are:
    • Windows: Administrator
    • UNIX/Linux: adm
    If the default administrative group in this parameter does not match a group in your environment, or you want to use a different group, you can:
    • create a group in your environment that matches the one defined in this parameter
    • change the value in this parameter to match an existing group in your environment
  • commEncrypted: Switch that secures communication between the Server/Agent and the Server/GUI by encrypting the data stream:
    • 0 = Off. Do not encrypt the data stream.
    • 1 = On. Encrypt the data steam.

[logging]

  • logsKept: Number of server logs to keep (5).
  • messagesPerLog: Maximum number of messages in a log, when this number is reached the log is closed and a new log is created (100,000).

[repository]

  • driver: Name of the JDBC driver to use, normally:
    • DB2: com.ibm.db2.jcc.DB2Driver
    • Cloudscape: com.ibm.db2j.jdbc.DB2jDriver
  • url: URL used to connect to the database, normally: "jdbc:db2://machine_name:50000/Aperi".
  • user: User name that Aperi uses to connect to its database repository.
  • schema: Name of the Aperi schema in the database repository.
  • connectionPool: Number of database connections in a pool of reusable open connections (10).

scheduler.config

Edit this file to configure the Data server scheduler in your environment. The scheduler deploys all monitoring activities and controls when monitoring jobs are run by agents.

Location of file: \aperi_install_directory\datasvr\configuration\

[concurrency]

  • maxSubmitThreads: Number of threads to create that handle the submission of jobs (3).
  • maxCompleteThreads: Maximum Number of threads to create to handle job completions. Initially will create a pool of 1/2 the number that can grow to the maximum (3).

[jobs]

  • minutesAdvanced: Number of minutes in advance of scheduled time to begin the scheduling process. This allows for the overhead time involved in scheduling a job so that the job will actually start close to the scheduled time (1) .

Aperi.config

Edit this file to configure the user interface and how it processes requests.

Location of file: \aperi_install_directory\datasvr\configuration\

[server]

  • threadPoolSize: Number of initial threads to create for handling requests (3).
  • maxThreads: Maximum number of threads allowed for handling requests (8).
  • pingReceiveTimeout: Number of seconds to wait before indicating that a ping has failed (10).

[gui]

  • threadPoolSize: Number of initial threads to create for handling user interface requests (3).
  • maxThreads: Maximum number of threads allowed for handling user interface requests (10).
  • reportRowLimit: Maximum number of rows that will be sent at a time to the user interface. If this number is exceeded, a More button will be displayed above the table, along with a warning message (5000).
  • keepCachedReport: Number of minutes to retain incomplete reports in the server's tmp directory (120).
nas.config

Location of file: \aperi_install_directory\datasvr\configuration\

Edit this file to configure Aperi for use with NAS:

  • On each line not beginning with #, the first blank-delimited field must contain the SNMP Enterprise code of a NAS filer that the agent should discover, probe, or scan.
  • The second field contains identifying information about the filer..

Any remote host that cannot be reached by SNMP or whose enterprise code does not match one of these values will be ignored.

agent.config

Edit the agent.config file to configure the agents in your environment. This file appears in the agent install directory on every machine where an agent is installed.

 

Location of file: \aperi_agent_install_directory\agent\configuration\

  • messagesPerLog: Maximum number of messages in a log, when this number is reached the log is closed and a new log is created (100,000).
  • serverPort: Port on which the Data server listens for requests (9549).
  • logFilesKept: Number of agent logs to keep (5).
  • uptimePoll: How often (in seconds) should agent check to ensure it is up (20).
  • sendFailWait: How many seconds to wait before attempting to resend a message to the server (30).
  • agentPort: Port on which the agent listens for requests (9550).
  • maxBacklog: Maximum number of uncompleted jobs to allow in the agent. Any requests for additional jobs to be run will result in an error (500).
  • honorSentScripts: If this parameter is set to '1', 't', 'T', 'y', or 'Y', the agent can run scripts sent from server. Otherwise, only existing scripts in the agent's scripts directory can be run.
  • agent.port
  • installLocation: The directory where Aperi is installed.
  • maxIdleThreads: Maximum number of idle threads to retain for reuse by future jobs (10).
  • serverHost: Host computer on which the Data server resides.

6. Start Aperi Storage Manager

This section describes how to start Aperi Storage Manager's user interface, server, and agent components. Make sure you have run the Configurator before performing the steps in this section.

6.1 Start the Aperi Storage Manager Server, Agent, and Database Repository

Perform the following steps to start the Aperi Storage Manager server, agent, and database repository components at the same time.

Note: You can also use the steps described here to start up an agent or server on a machine where other Aperi Storage Manager are not installed. For example, you can perform these steps to start up an agent on a machine where only an agent is installed.

  1. Start a command line session on the machine where Aperi Storage Manager components are installed.
  2. Change to the directory where you unzipped Aperi Storage Manager. For example: c:\aperi.
  3. Type the following in the command line: aperi
    The aperi script was created by the configurator and saved to the top level of the Aperi Storage Manager installation directory. When you run the aperi script, the following components will be started:
    1. Apache Derby (this step is not run if you are using DB2 for the repository)
    2. Device server
    3. Data server
    4. local agent
    A prompt will appear in the command line session after each component is started. Components not installed on the machine where you run the startup will be skipped.
  4. Press Enter in the command line session after each component starts.

Alternatively, perform the following steps to start the server, agent, and database repository individually instead of at the same time.

  1. Start a command line session on the machine where an Aperi Storage Manager component is installed. You must start a separate command-line session for each component you want to start.
  2. Change to the directory where you unzipped the Aperi Storage Manager.
  3. Perform the following from different command line sessions depending on what components you want to start:

    • To start the database repository (Derby): Change to the \aperi_install_directory\derby directory, type derby.bat, and press Enter.
    • To start the database repository (DB2): Use the DB2 Control Center.
    • To start the Device server: Change to the \aperi_install_directory\devsvr directory, type devsvr.bat, and press Enter.
    • To start the Data server: Change to the \aperi_install_directory\datasvr directory, type datasvr.bat, and press Enter.
    • To start the local agent: Change to the \aperi_install_directory\agent directory, type agent.bat, and press Enter.
      where \aperi_install_directory\ represents the directory where you installed the Aperi files.

6.2 Start the Aperi Storage Manager User Interface

Perform the following steps to start the Aperi Storage Manager user interface. You must start up the other components first as described in Starting the Aperi Storage Manager Server, Agent, and Database Repository before you can use the user interface. To start the user interface:

  1. Start a command line session on the machine where you want to start the user interface.
  2. Change to the directory where you unzipped the Aperi Storage Manager. For example: c:\aperi
  3. Change to the \gui directory.
  4. Type gui in the command line and press Enter.

7. Shut Down Aperi Storage Manager

To shut down an Aperi Storage Manager component you can:

We recommend shutting down components in the following order:

  1. user interface
  2. local agent
  3. Device server
  4. Data server
  5. database repository (Apache Derby or DB2)

8. Uninstall Aperi Storage Manager

To uninstall Aperi:

  1. Shut down any Aperi components that are running. See Shut Down Aperi Storage Manager for instructions on how to shut down Aperi components.
  2. Delete the Aperi installation directory.

9. Apache Derby security

Aperi Storage Manager does not currently implement all the security features in Derby for an enterprise-wide management application. Most notably, the Aperi Configurator does not configure any user authentication for the Derby RDBMS.This means that anyone will be able to connect to and use the installation of Derby that comes with Aperi.

10. Granting local administrative privileges to a domain account

For Windows users, the user account which the Data server runs under requires local administrative rights. Because these rights are not necessarily guaranteed for domain users in a Windows domain environment, this topic provides information on how to grant local administrative rights for domain users. Using this procedure, you do not have to manually process each machine in the domain.

To use Group Policy to grant local administrative privileges to a domain account, complete the following steps:

  1. On the domain controller, go to Administrative Tools > Active Directory Users and Computers (you must be running with Domain Administrator privileges).
  2. Right-click on the Organizational Unit (OU) upon which you want to apply the Group Policy. Click Properties.
  3. The Group Policy Properties panel is displayed. Select the Group Policy tab and click New to create a new Group Policy.
  4. Designate a name for the new Group Policy. Select the new Group Policy and click Edit.
  5. The Group Policy Object Editor panel is displayed. Go to New Group Policy Object > Computer Configuration > Windows Settings > Security Settings > Restricted Groups. Right-click on Restricted Groups. Click Add Group.
  6. For example, name the new group "Administrators." Under "Properties", add the user "Administrator", and the domain accounts or groups upon which you want the Group Policy in effect for. For example, you can add "APERI apeadmin", "APERI apegroup", and "APERI\TestGroup". Click OK.
  7. Add these user rights to the domain account:
    • Act as part of the operating system
    • Log on as a service
    In the Group Policy Object Editor, go to New Group Policy Object > Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignments. In the right pane, select "Log on as a service" and double-click. Add the domain user for whom you are granting the user right for and click OK. Repeat this step for "Act as part of the operating system."
  8. The group policy is now enforced for the Organizational Unit to include the domain accounts and groups specified under the local Administrators group on each computer in the Organizational Unit. In addition, the domain user has been granted the necessary rights. To verify this, log into a domain computer and open the Computer Management console. Select Groups, double-click on the Administrators group, and verify the membership of the domain users.

Notices

Aperi Storage Manager (C) Copyright IBM Corp. 2007. All Rights Reserved
All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html.