Application Server Host Settings

InstallAnywhere 2013 » Advanced Designer » Organization » Hosts

When you add an application server host in the Hosts view of the Organization page, you can customize its settings.

Note: InstallAnywhere supports remote deployment for Geronimo, Sun Application Server, and WebLogic application servers. Using remote deployment, you can create an installer that runs from a machine with no server to deploy software to application servers on connected target systems.

The Application Server customizer includes the following tabs:

General Settings
Optional Settings

General Settings

This tab lists the Server Type, Server Path, and optionally, the Host Name, Port, and Bundle Connection Libraries from Local Server Install controls.

General Settings Tab - Application Server Customizer

Control

Description

Server Type

Identify the type of application server to which you want to deploy. Choose from

Geronimo
WebSphere
JBoss
WebLogic
TomCat
Sun Application Server
Resin

Server Path

Enter the file path to the server.

If Bundle Connection Libraries from Local Server Install is checked, this value is the path to the server install on the build system. (The Server Path value can include source path variables (Access Path Names) to be resolved at build time.)
If Bundle Connection Libraries from Local Server Install is not checked, this value is the path to a server install on the target system. (The Server Path value can include InstallAnywhere variables to be resolved at install time.)
If Server Type is WebSphere, then Server Path is the file path to the active profile.

Note: Only Geronimo, WebLogic, and Sun Application Server support remote WAR/EAR deployment (bundling connection libraries at build time).

Host Name

Enter the host name of the server to which you want to deploy software. The value that you enter must be an IP address or resolvable name—for example, localhost, 127.0.0.1, or mycompany.com.

Note: Host Name is only shown when the Server Type is Geronimo, WebLogic, WebSphere, and Sun Application Server. For WebSphere, Host Name is read-only and set, by default, to localhost.

Port

Enter the port for the application server to which you want to deploy. For example, 1099, 8880, 7001, or 4848.

Note: For WebSphere, the Port text box is active even though InstallAnywhere does not support remote deployment for WebSphere. Interactions with WebSphere require a port number.

Bundle Connection Libraries from Local Server Install

Click to bundle the connection libraries from this server at build time.

Bundling the connection libraries enables your installer to perform a remote deployment of WAR or EAR files to a target machine that does not have an application server already installed. However, bundling connection libraries in the installer can significantly increase installer size.

If Bundle Connection Libraries from Local Server Install is checked, your build system must have access to an installation of the application server at build time. The application server does not need to be running at build time.
If Bundle Connection Libraries from Local Server Install is not checked, the installer looks, at install time, for the libraries based on the path you specified for Server Path. If the connection libraries exist there, the installer uses them to handle the WAR/EAR deployment. The application server does not need to be running at install time.

Optional Settings

This tab shows the authentication controls: Authenticate with Server, Username, and Password.

Optional Settings Tab - Application Server Customizer

Control

Description

Authenticate with Server

This check box enables the server authentication controls on the Optional Settings tab. Click Authenticate with Server if your want your installer to handle authentication tasks.

Username

Provide a user name for an account with sufficient privileges to perform the WAR/EAR deployment tasks your installer requires.

Password

Provide a password for the account specified by Username.

Note: If you enter a password, the password value is automatically encrypted according to the security settings that are specified in the Variables view on the Project page.

Note: For more information about deploying WAR and EAR files to an application server, see the Deploy WAR/EAR Archive action in Install Actions.

See Also