6.1 Installing WebSphere

6.1.1 Installing a Fix Pack to WebSphere
6.1.2 Installing WebSphere Feature Pack for JPA 2.0
6.1.3 JAVA_HOME and PATH environment variables
6.1.4 Starting WebSphere Base and accessing WebSphere Administrative Console
- 6.1.4.1 Start WebSphere Base
- 6.1.4.2 Access the WebSphere Administrative Console
6.1.5 Starting WebSphere ND and accessing WebSphere Administrative Console
6.1.6 Directory permissions
- 6.1.6.1 Modify the location for the extracted files

You must install WebSphere Application Server for running LiveCycle products. For use with LiveCycle, WebSphere can be installed either as WebSphere Base or as WebSphere ND with one base profile. See the WebSphere documentation to determine which method is best for your system.

6.1.1 Installing a Fix Pack to WebSphere

After you install WebSphere 7.0, you must update to WebSphere 7.0.0.15 and SR 9 before you deploy LiveCycle.

See the WebSphere support website for Fix Pack installation instructions and to access the WebSphere updates.

6.1.2 Installing WebSphere Feature Pack for JPA 2.0

After you install WebSphere 7.0, you must install WebSphere Feature Pack for JPA 2.0. See, WebSphere Support website and search Installing and uninstalling the feature pack to download and install Feature Pack.

6.1.3 JAVA_HOME and PATH environment variables

As part of your WebSphere installation, a Java SDK (JDK) was installed. The JAVA_HOME and PATH environment variables can point to the JDK where LiveCycle will be deployed.

6.1.3.1 Set the JAVA_HOME environment variable (Windows)

Select Start > Control Panel > System.
Click the Advanced tab and click Environment Variables.
In the System Variables area, click New.
Type JAVA_HOME as the variable name and, as its value, specify the directory where the JDK bundled with WebSphere is installed. For example, type the following path:

C:\Program Files\IBM\WebSphere\AppServer\java

6.1.3.2 Set the PATH environment variable (Windows)

Select Start > Control Panel > System.
Click the Advanced tab and click Environment Variables.
In the System Variables area, select Path, click Edit, and then append the following text to the beginning of the variable value:

        %JAVA_HOME%\bin;

6.1.3.3 Set the DISPLAY setting (AIX)

If you are using a Windows machine to access the AIX console, type the following text at the command prompt:
```
        export DISPLAY= <IP Address of the Windows machine telnet, or cygwin to         Linux or Solaris machine>:0.0
```
Note: If the DISPLAY setting is not set correctly, the following error occurs when you start Configuration Manager: "No JRE is found...".

6.1.3.4 Set the JAVA_HOME environment variable (AIX, Linux, and Solaris)

Set the JAVA_HOME variable for Borne and Bash shells as shown in the following example:
```
        JAVA_HOME=/opt/IBM/WebSphere/AppServer/java 
        export JAVA_HOME
```
Note: The specific path varies based on the installation directory you specified and the operating system you are installing on.

6.1.3.5 Set the PATH environment variable (AIX, Linux, and Solaris)

Set the PATH variable for Borne and Bash shells as shown in the following example:
```
        PATH=$JAVA_HOME/bin:$PATH 
        export PATH
```

6.1.3.6 (Windows, AIX, Linux, or Solaris ) Verify JAVA_HOME environment variables

(Optional) Open a command prompt and run the following command:

                java -version

You should receive a response that displays the Java version installed.

6.1.4 Starting WebSphere Base and accessing WebSphere Administrative Console

6.1.4.1 Start WebSphere Base

If the server is not already running, start the WebSphere Administrative Console, from [appserver root]/profiles/<profile_name>/bin, type the appropriate command, replacing server1 with the name of your server instance:

(Windows) startServer.bat server1
(AIX, Linux, and Solaris) ./startServer.sh server1

6.1.4.2 Access the WebSphere Administrative Console

Start the WebSphere Application Server.
In the address bar of a web browser, type the appropriate URL:

http://[host name]:[port]/ibm/console

If you are logged into the server that you are currently using, you can replace [hostname] with localhost. The port value depends on the application server and whether Administrative Security is enabled. The default port value for WebSphere is 9060. If Administrative Security is enabled, the default SSL port value is 9043.

If WebSphere Administrative Security is enabled, type the WebSphere user ID and password in the boxes provided.
Click Log In.

6.1.5 Starting WebSphere ND and accessing WebSphere Administrative Console

Open a command prompt and navigate to [WebSphere ND root]/profiles/Dmgr01/bin.
(Windows) Run startManager.bat.

(AIX, Linux, and Solaris) Run startManager.sh.
Navigate to [WebSphere ND root]/profiles/[profile name]/bin and run startNode.bat.
Once the services have started, connect to the server by typing the URL http://[host name]:[port]/ibm/console in the address bar of a web browser.

If you are logged into the server that you are currently using, you can replace [hostname] with localhost. The port value depends on the application server and whether Administrative Security is enabled. The default port value for WebSphere is 9060. If Administrative Security is enabled, the default SSL port value is 9043.
If WebSphere Administrative Security is enabled, type the WebSphere user ID and password in the boxes provided and click Log In.
In the navigation tree of the WebSphere Administrative Console, click Servers > Server Types > WebSphere application servers.
Select the listed server and click Start. Notice that the server status changes as the server is started.

6.1.6 Directory permissions

The LiveCycle application will extract files to the [appserver root]/installedApps directory. Therefore, it is important that writable permissions be given to that directory. If writable permissions cannot be given, the section below describes how to modify the location for the extracted files.

Note: It is recommended that you modify the location of the extracted files to [appserver root]/profiles/<profile_name>/installedApps.

6.1.6.1 Modify the location for the extracted files

Log in to the WebSphere Administrative Console.
Click Servers > Server Types > WebSphere Application servers and click your server name, such as server1.
Under Server Infrastructure, click Java and Process Management > Process Definition.
Under Additional Properties, click Java Virtual Machine and then click Custom Properties.
Click New and create a custom property named adobeidp.RootDirectory.
Set the value of adobeidp.RootDirectory to the path where Adobe native files should be extracted, such as [appserver root]/profiles/<profile_name>/installedApps.
Click OK or Apply.
In the Messages box, click Save directly to master configuration, and then restart the application server.