One alternative to local installation is to install WebSphere® Application Server Network Deployment for IBM® i from a Windows® workstation graphical user interface (GUI).
Prepare for the installation before using this procedure. See Preparing the operating system for installation on IBM i for more information.
When you run the GUI installation tool, you specify installation options interactively during the installation process.
Use this procedure to install WebSphere Application Server Network Deployment for IBM i with the GUI installation program:
STRHOSTSVR SERVER(*ALL)
You also must enter a valid user ID and password for the server. Your profile must have *ALLOBJ and *SECADM special authorities for this step.
Click Next to continue.
Installs the samples applications for learning and demonstration environments. The samples are not recommended for installation on production environments.
Installs all the non-English language files for using the administrative console from machines with non-English locales. If you do not select this option then only the English language pack is installed.
Installs all the non-English language files that support the application server runtime environment such as the wsadmin tool and logging. If you do not select this option then only the English language pack is installed.
If you choose not to install a feature at this time, then you can run the installer later and add features to this installation. Select the features you want to install and click Next.
The product installation root directory for WebSphere Application Server Network Deployment for IBM i contains the core product files. It is referred to in many information center examples as the app_server_root.
The default profile location for WebSphere Application Server Network Deployment for IBM i contains the configurable files for the profile. This directory is referred to in many information center examples as the user_data_root. The default profile location is the directory under which the profile registry and profiles directory are created. The default profile is created under user_data_root/profiles/default. The profile registry is created under user_data_root/profileRegistry.
The product library is often spelled out in information center examples, but it might also be referred to as the product_library
Profile Type | Description |
---|---|
Cell | Create a cell with two profiles: a deployment manager and an application server node that is already federated into the deployment manager cell. This is useful for development environments. |
Management | Create a management profile that provides
the servers and services necessary to manage your WebSphere environment. You can select one
of the following management profile types on the following panel:
|
Application server | Create a standalone application server profile. |
Custom | Create a custom profile which belongs to a deployment manager cell, to make applications available to the Internet or to an intranet under the management of the deployment manager. You must federate this node to use it. |
Secure proxy | Create a secure proxy server to take requests from the internet and forward them to application servers. The secure proxy server resides in the DMZ. |
None | Do not create a profile during installation. However, if you do not create a profile during installation, then you must create a profile after installation to have an operational product. |
The user ID and password do not need to be a system user ID and password or an LDAP user ID and password. The ID-and-password pair specified are stored in the user registry and used for administrative security for the default profile.
The InstallShield program displays messages that indicate the status of the installation and a status bar to show the progress of the installation.
After the installation runs, the Configuration Manager progress panel is displayed. The configuration manager performs post-installation tasks and creates the default profile.
After the installation process is complete, the summary panel displays the results of the installation process and links to additional information about the product.
This procedure results in installing WebSphere Application Server Network Deployment for IBM i from a Windows workstation GUI, which can take up to 120 minutes to complete.
Go to Installing the WebSphere Application Server group PTF on IBM i to continue the installation.
In this information ... | IBM Redbooks, demos, education, and more(Index) Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience. This feature requires Internet access. Most of the following links will take you to information that is not part of the formal product documentation and is provided "as is." Some of these links go to non-IBM Web sites and are provided for your convenience only and do not in any manner serve as an endorsement by IBM of those Web sites, the material thereon, or the owner thereof. |