> Installation Guide > Post-Installation Instructions

Installation Guide

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Post-Installation Instructions

This section covers the following post-installation topics:

 

Configure Your Application Server

Your application server may require additional configuration before you can start using the product.

WebLogic Server Installations

The following sections provide post-installation information when using WebLogic Server as your application server.

User ID and Password

If WebLogic Server is selected as the application server, the installer creates a WLS Domain for ALER in PRODUCTION mode with the following default User and Password:

     User: weblogic

     Password: weblogic

For information on how to change the WLS UserID and Password, see Manage users and groups in the WebLogic Server 9.2 Administration Console Online Help.

Set WebLogic Server Environment Parameters

The SERVER_NAME environment variable is not correctly set by installer on WebLogic Server 9.2.1 installations. Remove or properly set the SERVER_NAME environment variable when starting the ALER domain. For example:

For Windows: 

     set SERVER_NAME=alerServer

For Linux/Unix: 

     SERVER_NAME=alerServer
     export SERVER_NAME

WebSphere Installations

The following sections provide information for post-installation procedures required to complete your installation of ALER.

Deploying the ALER Application

Once the BEA installer has completed, you will have a WebSphere directory, such as BEA_HOME/repository30/websphere. This directory contains all of the properties files that configure the ALER instance appropriately once it is deployed, as well as the aler.ear file and a copy of the JDBC Drivers that had been used to generate the database during the install process.

Use the following steps to deploy ALER 3.0 on WebSphere:

  1. Create a BEA_HOME, such as /opt/bea, on the target application server.
  2. As a recommended best practice, copy the JDBC Driver JAR file(s) and all properties files from the BEA_HOME/repository30/websphere directory into the BEA_HOME on the deployment server.
  3. Deploy the aler.ear file in the manner most appropriate for your deployment server.
    4. Note: Do not start the application as there are additional configuration steps that must be performed before the application is considered fully deployed.
  4. Modify the generic JVM parameters.
    1. Open the Servers > Application Servers > myserver > Java and Process Management > Process Definition > Java Virtual Machine page.
    2. Add the following parameters to the Generic JVM Parameters property:
      • Unicode compatibility – be sure to set the default client encoding appropriately. Depending on your locale, this may be reasonable: -Dclient.encoding.override=UTF-8
      • Turn off strict code verification: -Xverify:none
      • To prevent XLST transformations in the diagnostic page and the metadata viewer from failing in your Web browser, add a default implementation for DTMConfiguration:
        -Dorg.apache.xml.dtm.DTMManager=org.apache.xml.dtm.ref.DTMManagerDefault
      • On the Custom Properties page, click Add to add the following properties:

        • Name: Enter BEA_HOME as the name of the variable BEA_HOME

        Value: Enter the absolute path of the BEA_HOME directory. For example /opt//bea.

  5. Modify the ALER application module class load order:
    1. Enter the WebSphere Integrated Solutions Console.
    2. Click Applications > Enterprise Applications.
    3. Click the deployed ALER application.
    4. Click the Manage Modules link.
    5. Click the aler-app.war module.
    6. Change the Class load order to Classes loaded from application class loader first (labeled as “Parent last” in version 6.0 and earlier).
    7. Click Apply.
    8. Click the aler-web.war module.
    9. Change the Class load order to Classes loaded from application class loader first (labeled as “Parent last” in version 6.0 and earlier).
    10. Click Apply.
    11. Click the Save directly to the master configuration link to commit your changes to the master configuration.
  6. Create a shared library from within the ALER application and associate it with the application:
    1. On the Applications > Enterprise Applications > ALER > Shared Library References page, select the aler-app.war module and then click Reference Shared Library.
    2. Click New.
    3. Select a Server Scope for the shared library that includes the Node, Cell, and Server levels.
    4. Assign a meaningful Name to the shared library. Description is optional.
    5. In the classpath field, enter the ALER 3.0 directory, such as BEA_HOME/repository30/Websphere. This directory contains all of the properties files for the ALER instance.
    6. On a separate line within the classpath field, enter the absolute path of each JDBC driver JAR files within the BEA_HOME directory. If you have more than one file, add only one file per line.
    7. Select the new library in the Available list box and use the right-facing arrow >> button to select that library for use with the aler-app.war application.
    8. Click Ok to continue.
    9. Click the Save directly to the master configuration link to commit your changes to the master configuration.
  7. Restart WebSphere.
  8. Restart the ALER application.
  9. After starting up ALER, enable and set the following Systems Setting property to true for SSL support and also to avoid an SSLContext error on the Run Active Diagnostic page.

    10. cmee.ssl.force-sun-provider = true

Change the Server Classloader Order for XLST

To prevent issues with XSLT Transformation, use the following steps to change the classloader order in your WebSphere installation:

  1. Log into the WebSphere Administrative Console.
  2. Click the Server > Application Server > server link
  3. Select the Configuration tab.
  4. Select the option for Parallel start.
  5. Change the Access to internal server classes to: Allow.
  6. Change Server Specific Application Settings > Classloader Policy to Single.
  7. Change the Server Specific Application Settings > Class loading mode to Parent First.
  8. Click the Save directly to the master configuration link to commit your changes to the master configuration.

 

Install Java Web Start

Java Web Start is a browser plug-in that runs files with JNLP extensions. Java Web Start must be available on the client in order to use ALER’s Asset Editor, Type Manager, and the Import/Export utility.

Download and Install Java Web Start

  1. Download Java Web Start from java.sun.com.
  2. When the download is complete, install Java Web Start.
  3. When installation is complete, open the Windows Control Panel.
  4. Open the Java plug-in.
  5. Click the browser tab and check the appropriate browser(s) with which to use the Java Web start application. (Required for proper Asset Editor functionality.)
  6. Click the Advanced tab.
  7. Select the appropriate SUN Java JRE version for use with the installed version of AquaLogic Enterprise Repository.
  8. Close and re-open all instances of the Internet Explorer or FireFox browsers.
  9. Navigate to the ALER instance.
  10. Click Edit/Manage Assets on the ALER Assets screen.

    11. A security warning opens. (This occurs only during the first launch of the Asset Editor.)

  11. Click Start.

    12. Java Web Start installs and the Asset Editor opens.

Troubleshooting Java Web Start

ALER employs a browser MIME-type support checking process that is executed when the Edit/Manage Assets (Assets screen) and Edit (asset detail display) links are generated. This process will inspect the client browser to determine if there is a registered handler for a JNLP file (which should launch Java Web Start). If this process fails or returns no results, the link HREF target will point to the aler-web/web start/launch.htm page.

The browser-supported mime type determines which client installed application will be presented as the target of the Edit/Manage Assets and Edit links. Java Web Start must be properly installed in order to work correctly with the operating system as the handler for JNLP files passed to the client browser.

The process of registering this mime type with the browser is normally handled during installation of the Java Web Start plug-in application. Certain corporate security measures or anti-Spyware applications may block this kind of change to the Windows Registry, as will the improper installation and/or removal of the Java Web Start application, Java Run Time Environment or Java SDK if improperly registered within the Java plug-in applet within the Windows Control Panel.

The following instructions may help to rectify the incorrect MIME type support, assuming that Java Web Start and an appropriate version of the SUN Java JRE are properly installed within the client computer system.

To manually set the file/MIME association within the Windows operating system using the Windows Explorer:

  1. Open the Tools Menu.
  2. Select Folder Options.
  3. Select the File Types tab.
  4. Scroll down to JNLP or create a new JNLP file type.
  5. Associate the Java Web Start Application (located in the correct path if more than one JWS is installed) with the JNLP file extension.
  6. In the Windows Control Panel, add support (check the option) for Internet Explorer within the Java Plug-in console applet. This process should assign the JNLP file type to Java Web Start within the Windows operating system.

 

Start Your Application Server and Log Into the ALER Web-based Console

After configuring your application server, follow these steps to start your application server and log into the ALER Web-based console.

  1. Start your application server:
    • Built-in Tomcat—navigate to the BEA_HOME\repository30\bin directory and, depending on your platform, double-click either the startTomcat.cmd (Windows) or startTomcat.sh (UNIX) file.
    • WebLogic Server—navigate to the BEA_HOME\user_projects\domains\DOMAIN_NAME directory and, depending on your platform, double-click either the startWeblogic.cmd (Windows) or startWeblogc.sh (UNIX) file.
      • Note: For instructions on starting standalone Tomcat and WebSphere application servers, see the documentation for those products.
  2. Point your browser to the ALER application.

    3. For example: http://myserver.domainname.com:7101/aler/

  3. On the login screen, enter admin for the Username and Password. This is the default administrative account installed with ALER. You can change the default password through the Administration tab in ALER at a later time.
    4. Note: If your organization requires a user name and password each time you log into ALER, clear the Enable Automatic Login check box.
  4. Click Login.

    5. The Login Stats dialog box displays a welcome message that includes the date and time of your login.

  5. Click Close.

For more information on using the ALER console, see the “Getting Started” section of the ALER User Guide.

 

Use the ALER Diagnostics Testing Tool

The Diagnostics tool allows testing and troubleshooting of certain aspects of ALER, including testing for:

To launch the Diagnostics tool, navigate to the http://host_name/application_name/diag/index.jsp page of the ALER console. For more information, see “Utilizing the Diagnostics Testing Tool” in the ALER Upgrade Guide.

 

Import ALER Solution Packs and Datapacks

ALER bundles base sample data for users to help you get started using the enterprise repository. Additionally, depending upon the edition of ALER that you purchased, you can also import supplemental datapacks and solution packs, as follows.

Importing the Solution Pack for Working With AquaLogic Assembly Models in Eclipse

The Professional and Advanced Editions of ALER can use the Eclipse plug-in for ALER to compose and visualize composite applications. However, in order to submit AquaLogic projects as assembly models to the repository, you must first import the contents of the ALER30-AquaLogic-Solution-Pack.zip file into ALER. This file is bundled with your installation under the BEA_HOME\repository30\core\tools\solutions folder. For detailed instructions on importing the AquaLogic Solution Pack into ALER, see Using WorkSpace Studio for Repository Access.

Importing the Advanced Edition Data/Solution Packs

If you purchased the ALER 3.0 Advanced Edition, you also have access to supplemental data/solution packs for Policies, Compliance Templates, EA, and Open Source, as well as the documentation for the Advanced Edition features. The Advanced Edition features require a data load to be used, and the Policies also require some ALER system settings to be switched on, as described in the Advanced Edition documentation for those features.

The supplemental data and documentation is delivered in the ALER3.0SupInteg,Doc&Data.zip file, which is available using a separate download link or on the Advanced Edition CD. The supplemental data/solution packs need to be imported into ALER using the Import/Export tool, as described in the ALER Import/Export Guide.

For more information on obtaining the Advanced Edition of ALER 3.0, contact your BEA sales representative.

 

Test the ALER Installation

Testing the ALER installation involves a number of tasks that ensure the proper operation of initial ALER features and functions. These instructions apply to all application servers currently supported by ALER.

Note: To verify the Automated Registration Flow feature in the ALER 3.0 Advanced Edition triggers automatic asset submission and acceptance, refer to the “Getting Started” section of Configuring and Managing Advanced Registration Flows guide in the ALER3.0SupInteg,Doc&Data.zip file.

Submit an Asset

Asset submission is performed on the ALER Assets page.

  1. In the Assets panel, click Submit an Asset.
  2. In the Asset Submission dialog box, complete the following fields:
    • Asset Name
    • Version
    • Type
    • Description
    • URL—enter the file location (for example, http:/www.example.com/repository/)
  3. Click Submit to submit the asset the registrar.
    4. Note: Attempts to save as asset without first completing all required data fields will result in a warning message. A confirmation message indicates the asset was successfully submitted to the ALER registrar.
  4. Click Close.

For more information, see the ALER User Guide.

Accept the Asset

The asset acceptance process is performed by the ALER registrar using the Asset Editor. The registrar makes decisions about an asset based on company requirements. To accept and assign an asset means that the registrar accepts the asset and assigns it to another person to shepherd it through the remainder of the registration process.

  1. On the Assets page, click the Edit/Manage Assets option to launch the Asset Editor.
  2. Expand the Submitted folder in the Assets tree.
  3. Expand the Pending folder and open the asset submitted in Submit an Asset.
  4. For the purposes of this exercise, click Accept.

    5. The asset moves to the Under Review folder in the tree, and also appears in each of the workflow folders under the asset. The workflow folders correspond to tabs in the Asset Editor.

For more information, see the ALER Registrar Guide.

Register the Asset

The asset acceptance process is performed by the ALER registrar using the Asset Editor.

  1. On the Overview, Support, Technical, and Tests tabs, complete the remaining information, including the notification email, licensing information, and support contacts as appropriate.
    2. Note: The notification email automatically sends notification to the email address when the asset is downloaded/selected for use. The asset can be moved from its original location to the storage repository on this tab.
  2. Click Approve on a tab.

The tab label changes color and the Approve button changes to Unapprove.

  1. Click the Taxonomy tab.
  2. Assign the asset to the appropriate categories and/or domains.
    3. Note: Categories and domains are configurable. (See the ALER Administration Guide.)
  3. Enter any keywords and classify the asset into one of five categories:
    • Raw—No assurance of quality or completeness.
    • Educational—To be used for educational purposes only. The asset may not be complete in terms of documentation, test results, or other information.
    • Approved—Approved for use by the registrar
    • Recommended—Successfully used on at least one project.
    • Mandated—Must be used whenever the functionality it provides is needed (This is especially relevant for Web services that access customer data, process payments, and so on).
  4. Click Approve.

    5. The tab label changes color, and the Approve button changes to Unapprove.

  5. Click the Documentation tab.
  6. When all of the documentation requirements are met, click Approve.
  7. Continue the approval process for each of the remaining tabs.
  8. On the Administration tab, click Register to complete the registration process, or click Assign to assign the asset to someone else.
  9. Save changes by clicking Save on the File menu.

    10. The asset is moved to the Registered folder and each action (approval of tabs, field value updates, etc.) are also recorded in the Audit log found on the asset’s Administration Tab.

For more information, see the ALER Registrar Guide.

Find the Registered Asset and View Details

Complete the process by searching for the newly registered asset you created.

  1. On the Assets page, use the Search option to locate the asset.

    2. The asset should appear in the list in the upper frame of the main Assets page, indicating that the XML data stored as a BLOB is correctly loaded in the database.

  2. Click the asset to open the asset detail in the lower frame of main page.

 

Start the AquaLogic BPM Process Engine

If you purchased the ALER 3.0 Advanced Edition with the ALBPM component for repository workflows, follow these steps to launch the ALBPM Admin Center and start the Process Engine.

  1. Navigate to the <BEA_HOME>\albpm57\enterprise\bin directory and double-click one of the following files:
    • albpmadmcenter.exe (Windows or UNIX GUI-based)
    • ./startwebconsole.sh (UNIX console-based). Then point your browser to http://<host>:8585/webconsole (e.g., http://localhost:8585/webconsole).
  2. On the Admin Center page, click the Start BPM Web Applications option.
  3. When it becomes available, click the Launch Process Administrator option to launch the Process Administrator.
  4. When prompted to enter the required credentials, enter the BPM admin user name and password that was used on the FDI User Credentials panel during the installation process. The recommended example for these credentials is bpm_admin for the user name and password.
  5. Open the aler_engine Process Engine by clicking the Engine link on the left side of the page.
  6. Start the aler_engine by clicking the Start icon under Engine Actions on the right side of the page. Starting the engine may take several minutes to complete. Make sure that the status of the engine is Ready.

For more information on configuring ALER to use the ALBPM Process Engine, see the Configuring and Managing Advanced Registration Flows guide in the ALER3.0SupInteg,Doc&Data.zip file.

 

Tune SQL Server 2005 Database Performance

ALER 3.0 takes advantage of parallel import performance within SQL Server 2005. To take advantage of this performance enhancement, enable and set the following property within the Admin System Settings page:

     cmee.impexp.lightweight.import.serialize = false


  Back to Top       Previous  Next