Preparing WebSphere Application Server for base deployment

Set up IBM® WebSphere® Application Server for base deployment.

About this task

If you are planning to use a base deployment, IBM Installation Manager creates a IBM WebSphere Application Server profile named server1. If you choose to use this profile, you do not have to create one before installation.

Important: Do not register server1 as a Microsoft Windows service. If you do, then IBM Installation Manager cannot restart server1 during the process of installing the InfoSphere® MDM deployment modules.

This procedure assumes that you have the application server already installed.

Procedure

Set the default Java™ SDK version to 1.8.0:
- On Microsoft Windows operating systems, run the command
```
WAS_INSTALL_HOME\bin\managesdk.bat -setNewProfileDefault -sdkname 1.8.0_64
```
- On UNIX or Linux® operating systems, run the command
```
WAS_INSTALL_HOME/bin/managesdk.sh -setNewProfileDefault -sdkname 1.8.0_64
```
Create the IBM WebSphere Application Server base profile:
- To create the base profile using the profile management tool:
  1. Go to the WAS_INSTALL_HOME/bin/ProfileManagement directory and run the profile management tool.
    - For Microsoft Windows, run pmt.bat
    - For Linux and UNIX, run pmt.sh
  2. On the Environment Selection panel, click Application Server and click Next.
  3. On the Profile Creation Options panel, select Typical profile creation and click Next.
    Tip: Optionally, if you do not want to use the default configuration, select Advanced profile creation and provide your configuration details. This procedure assumes a typical profile creation.
  4. On the Administrative Security panel, make sure the Enable administrative security option is selected. Add a user name and password, and then click Next.
  5. Review the summary and click Create. The profile management tool will create a base profile.
- To create the base profile using the command line, run the following command:
  Note: Substitute the correct values for WAS_INSTALL_HOME, was_user, and was_password.
  - For UNIX and Linux systems:
```
WAS_INSTALL_HOME/bin/manageprofiles.sh -create -templatePath WAS_INSTALL_HOME/profileTemplates/default -enableAdminSecurity true -adminUserName was_user -adminPassword was_password
```
  - For Windows systems:
```
WAS_INSTALL_HOME\bin\manageprofiles.bat -create -templatePath WAS_INSTALL_HOME\profileTemplates\default -enableAdminSecurity true -adminUserName was_user -adminPassword was_password
```
  Note: The following optional parameters enable you to provide more detail in the profile creation command:
  - If you do not want to use the default profile path, you can add -profilePath profile_path into the command.
  - If you do not want to use the default profile name, you can add -profileName profile_name into the command.
Ensure that the application server's Start components as needed option is not enabled:
1. From the Integrated Solutions Console, navigate to Servers > Server Types > WebSphere Application Servers.
2. Click on the server where InfoSphere MDM will be deployed.
3. In the Configuration panel, ensure that the Start components as needed option is not selected.
  
  Note: If this option is enabled, you will encounter exceptions when the server starts after installing the InfoSphere MDM Enterprise Business Application .
Start the server. You can use the First Steps console or a command line.
For example: /opt/IBM/WebSphere/AppServerBASE/profiles/AppSrv01/bin/startServer.sh server1