WebSphere Deployment

Initial System Configuration

Database Drivers

Create a directory for the database drivers for your database. Copy the necessary driver .jar files into this directory.
Example: AIX or Linux: /opt/oracle/db_drivers
Windows: C:\oracle\adminconsole\db_drivers

  1. Oracle 12.1 – The necessary driver, ojdbc8-12.2.0.1.jar, is included in the libs directory of the AdminConsole Media Pack.
  2. IBM DB2 – db2jcc4 jar is included with the purchase of the DB2 software. This file is not available for download. Contact your IT department if you need assistance locating these files.
  3. Microsoft SQL - download the sqljdbc4.jar library version 4.0 from https://mvnrepository.com/artifact/com.microsoft.sqlserver/sqljdbc4/4.0

Note: Each version of DB2 requires specific drivers. The files above correspond with DB2 10.5.

AdminConsole Setup

Note: For a WebSphere 9.0.0.4 deployment, the .jar files need to be installed only once. If AdminConsole Is reinstalled, the existing files may be re-used.

  1. Create a directory on the WebSphere server to store various configuration files for AdminConsole(e.g., /opt/oracle/adminconsole/ or C:\oracle\adminconsole).
  2. Create sub-directories inside the directory from Step 4 called conf and libs.

    3. Note: Make a note of the path to the libs directory. It will be used later in the classpath for setting up the AdminConsole Shared Library.

  3. Copy the following files from the installation media into the conf sub-directory:
    1. commons-logging-1.2.jar
  4. Copy the following files from the installation media to the libs sub-directory:
    1. commons-logging-1.2.jar
    2. el-api-2.2.jar
    3. javax.persistence-2.1.1.jar
    4. eclipselink-2.6.4.jar
    5. javax.ws.rs-api-2.0.1.jar
    6. log4j-api-2.9.1.jar
  5. Use a text editor to open the ac.properties file that you just copied to the server.

    6. The ac.properties file contains properties for Oracle, and DB2 database types, with the Oracle settings active by default. The inactive settings are commented out with a '#' character at the start of each line. To change a setting, remove the '#' from the required property setting, and insert it at the beginning of the setting you want to de-activate.

  6. The properties setting must match the type of database being used. The two properties that are used to do this are:
    1. application.databaseType
    2. jpa.databasePlatform
  7. Identify the default locale in the ac.properties file. The locale selected will determine the translation that is loaded in the database for AdminConsole when it launches. The default setting is English.
    1. application.defaultLocale
  8. If using an Oracle database, please skip this step. If using a DB2 database, you will need to modify the ac.properties file to include configuration for case-insensitive searching:

Create and Configure Admin Console

Using a web browser, connect to the Administrative Console using the appropriate server name and 9060 as the default port (Ex: server_name:9060/admin" class="external-link" rel="nofollow">http://server_name:9060/admin).

Create the Admin Console Application Server

  1. Select Servers>New server.
  2. Select server type WebSphere application server.
  3. Enter AdminConsole for the name of the server.
  4. Click Next.
  5. Select the default server template.
  6. Click Next.
  7. Ensure Generate Unique Http Ports is checked.
  8. Confirm the new server by clicking Finish.
  9. After the application has been created, review the messages at the top of the Application servers screen to confirm that the new server has been created successfully.
  10. Navigate to the AdminConsole server by clicking on its name within the list of application servers.
  11. Click the Session management link in the Container Settings section.
  12. Verify that Enable Cookies is checked. This is checked by default.
  13. Click the Enable Cookies link and verify that 'Restrict cookies to HTTPS sessions' is unchecked. (This is unchecked by default.)
  14. Click OK.
  15. Click OK to save the configuration changes.

Note: These instructions assume that a fresh installation of the application server was performed. All configuration settings must use the default settings unless otherwise noted. If the application server has been used for previous deployments, you may want to create a new application server specifically for the deployment of the AdminConsole environment.