The Installation Verification Tool, ivt.sh, tests a profile by starting the server if necessary, checking that it opens its ports, and examining the logs for start-up messages. It takes the server name and the profile name as arguments, in the form ivt.sh server_name profile_name, and an optional port argument, -p, for use when the default port differs. To confirm that the deployment manager profile was created successfully, the administrator runs it with the deployment manager's server name, dmgr, followed by the name of the deployment manager profile. Option C has the correct form.
Option A supplies only the custom profile and omits the server name. Option B gives the deployment manager name and the custom profile, which tests the wrong profile, and adds a port number that does not correspond to the deployment manager's default administrative console port. Option D omits the profile and supplies a port that is not the deployment manager's. A custom profile contains no server before federation and customisation, so the tool could not verify it in any case.
The script should be run from the bin directory of the profile being checked. Its results are shown in the console output and written to a log file in the profile's logs directory, which the administrator can read to find the cause if a test fails.
[Reference: Installation Verification Tool (ivt.sh); Verifying profile creation; Deployment manager profile.]
Submit