...
Choose the WAR file created in Step 1, then click on Next button.
...
In the next couple of steps of installing the application on the server, keep the default settings and keep clicking Next button.
In Step 4 of the installation, we need to specify the Context Root. Go back to the Nexaweb Studio, and open the project Properties window. On the left navigation panel, scroll all the way down and select Web Project Settings, as shown below.
...
Copy this Context root name and paste it in Step 4 of installation on WAS server, after the '/', as shown below.
...
Click on Next button to come to Step 5, which is summary. Click Finish button.
After the application is installed successfully, you may hit Save where it mentions in the instructions. See below.
...
Now click on the Manage Application link as shown in the picture above. Alternatively, go to the left navigation panel → Applications → Application Types → WebSphere enterprise applications. Now in the main panel, you will see a list of applications installed on the server. Click on the checkbox against your application and then click on the “Start” button at the top.
...
On the left side navigation panel, go to Servers → Server Types → WebSphere application servers .
...
When you click on your server, the main panel will show the details. On the main panel, under the “Communications” section, expand “Ports”. You will see a list of ports that the application uses and various listeners. We need the port number against the listener “WC_defaulthost” because we are using HTTP. If we use HTTPS, then we need the port number against the listener “WC_defaulthost_secure”. You can run your application on either HTTP or HTTPS.
...
Now to launch the application on the server, open your browser and type the following in the address bar - http://localhost:<port-number>/<Context-type-name-entered-in-Step-4>
The application should run now, and for reference, see the screenshot below.
...
Conclusion
We saw how to install and run a Nexaweb application on the WAS server 8.5.5.16. Please note that this method is recommended over running the WAS server through Nexaweb Studio.
...