First steps console
After installing WSRR and creating a profile, you can use the First steps console to get started with WSRR.
For UNIX and Linux systems, change directory to profile_root/firststeps/wsrr, for example, opt/IBM/WebSphere/ServiceRegistry/profiles/WSRRSrv01/firststeps/wsrr. Enter the command ./launchpad.sh.
For Windows systems, perform one of the following actions:- Change directory to profile_root\firststeps\wsrr, for example, C:\IBM\WebSphere\ServiceRegistry\profiles\WSRRSrv01\firststeps\wsrr. Enter the command launchpad.exe. Or:
- Select
When you start the First steps console the generic WebSphere® Application Server First steps console opens.)
- Verify the installation
- Start the server, managed node, or deployment manager
- Start the administrative console (stand-alone server and deployment manager only)
- Start the WSRR Web UI (stand-alone server only)
- Start the WSRR dashboard (stand-alone server only)
- Load the WSRR governance enablement profile (stand-alone server only)
- Open the WSRR Information Center
- Installation verification
- Starts the installation verification test. The test consists of
starting and monitoring the stand-alone server, managed node, or deployment
manager during its startup.
If this is the first time that you have used the First steps console since creating a stand alone server or deployment manager profile, select Installation verification to verify your installation. The verification process starts the stand alone server or deployment manager.
Note: The Start the server options are unavailable while the Installation Verification Tool (IVT) runs.The IVT provides the following information about the stand alone server or deployment manager:- The name of the server process
- The name of the profile
- The profile path, which is the file path and the name of the profile
- The type of profile
- The cell name
- The node name
- The current encoding
- The port number for the administrative console
- Various informational messages that include the location of the SystemOut.log file and how many errors are listed within the file
- A System Health Report (only for stand-alone servers)
- A completion message
- Start the server
- Toggles to Stop server when the server runs.
After selecting the Start the server option, an output screen is displayed with status messages. The success message informs you that the server is open for e-business. Then the menu item changes to Stop server and the Administrative console, WSRR Web UI, and Load WSRR Governance Enablement Profile options are enabled.
Note: If you select the Start the server option, the Installation verification option is unavailable while the server is starting. - Start the deployment manager
- Toggles to Stop server when the deployment
manager runs.
After selecting the Start the server option, an output screen is displayed with status messages. The success message informs you that the deployment manager is open for e-business. Then the menu item changes to Stop server and the Administrative console option is enabled.
Note: If you select the Start the server option, the Installation verification option is unavailable while the deployment manager is running. - Start the managed node
- Toggles to Stop server when the server
runs.
After selecting the Start the server option, an output screen is displayed with status messages. The success message informs you that the server is open for e-business. Then the menu item changes to Stop server.
Note: If you select the Start the server option, the Installation verification option is unavailable while the server is starting. - Administrative console
- This option is unavailable until you start the stand-alone server
or deployment manager. Use the administrative console to perform administration
tasks at the application server level.
Select the Administrative console option to open the administrative console in your default browser. When you have more than one server on the same workstation, the port varies. The First steps console starts the administrative console that is associated with the same profile as in the First steps console.
- WebSphere Service Registry and Repository Web UI
- This option is unavailable until you start the stand-alone server.
(It is never available for deployment manager or managed node profiles).
Select this option to open the WSRR web UI, that is configured for the profile, in your default browser. Use the WSRR Web UI to use and manage this WSRR instance.
- WebSphere Service Registry and Repository Dashboard
- This option is unavailable until you start the stand-alone server. (It is never available for
deployment manager or managed node profiles).
Select this option to open the WSRR dashboard in your default browser.
- Load WSRR Governance Enablement Profile
- This option is unavailable until you start the stand-alone server. (It is never available for
deployment manager or managed node profiles).
Select this option to load and activate the governance enablement configuration profile into this WSRR instance.
- Profile Management Tool
- Starts the Profile Management Tool. Use the Profile
Management Tool to create a stand-alone server, deployment manager,
or custom (managed node) profile.
A profile consists of files that define the runtime environment for the stand-alone server or deployment manager. Each profile has its own administrative interface. A custom profile is an exception. A custom profile is an empty node that you federate into a deployment manager cell and customize. No default server processes or applications are created for a custom profile.
Each profile has its own First steps console. The location of the command to start the First steps console is within the set of files in the profile. A prompt to start the First steps console that is associated with a profile is displayed on the last panel of the Profile Management Tool.
- Information Center
- Links you to the WSRR Information Center.
- Exit
- Closes the First steps console.