Work with OVA instance

After you complete the deployment of a WebSphere® Portal and Web Content Manager patterns on IBM® PureApplication® Systems (PureApp), you can now get started with the system. For more information, see WebSphere Portal and Web Content Manager product documentation.

File system locations
After the deployment is complete, the file system can be found in several locations.
Start and stop WebSphere Portal
You can start and stop WebSphere Portal by using the WebSphere Application Server startServer.sh and stopServer.sh shell scripts. By default WebSphere Portal is started at the end of the deployment. For a cluster of WebSphere Portal instances, it is easier to start and stop instances and manage other resources from the deployment manager's administration console.
Access the deployment manager console
Individual cluster members can be managed centrally in the deployment manager administration console.
Start and stop the HTTP Server
The Open Virtual Archive (OVA) comes pre-configured with the IBM HTTP Server to allow port 80 and 443 access to WebSphere Portal. By default the HTTP Server is started only on cluster patterns with a remote IHS part.
Access the site from a browser
Different versions of the WebSphere Portal product use different ports in WebSphere Application Server for administration and direct access to the portal JVM.
Globalization consideration
Starting a deployment of WebSphere Portal by using PureApplication creates your portal by using a default locale setting of English. However, portal can present the web page in other locales in several ways.

Parent topic: Introduction to Hypervisor Pattern Version 1