When installing samples or managing profiles, the commands
used in native WebSphere Application Server environments are sometimes
different from the commands used in environments that contain IBM
WebSphere Application Server Hypervisor Edition.
Although the IBM HTTP Server is installed as the user
virtuser,
there are some files that belong to the user
root. The list
of files that belong to
root, can be seen using the following
command:
find $IHS_INSTALL_ROOT -user root. This
difference dictates that some commands must be issued as
root instead
of
virtuser.
virtuser@leolpar04:/opt/IBM/HTTPServer/bin> sudo -u root ./adminctl start
virtuser@leolpar04:/opt/IBM/HTTPServer/bin> sudo -u root ./adminctl stop
virtuser@leolpar04:/opt/IBM/HTTPServer/bin> sudo -u root ./apachectl start
virtuser@leolpar04:/opt/IBM/HTTPServer/bin> sudo -u root ./apachectl stop
There are some differences when using the
manageprofiles command.
The sample applications included with WebSphere Application Server
are installed by default in the IBM WebSphere Application Server Hypervisor
Edition version 7.0.x virtual image. When using the native WebSphere
Application Server GUI installer, the sample applications are not
installed by default. If administrative security is enabled and you
create additional profiles using the
manageprofiles.sh script,
include the following options to avoid validation errors.
- If you want the profile to include the samples, use the -samplesPassword
option. For example, ./manageprofiles.sh -create -profileName
profile_name -profilePath profile_path -templatePath template_path
-adminUserName admin_username -adminPassword admin_password -enableAdminSecurity
true -samplesPassword sample_password.
- If you do not want the profile to include the samples, use the
-omitAction samplesInstallAndConfig option. For example, ./manageprofiles.sh
-create -profileName profile_name -profilePath profile_path -templatePath
template_path -adminUserName admin_username -adminPassword admin_password
-enableAdminSecurity true -omitAction samplesInstallAndConfig.
This applies to both 6.1.0.x and 7.0.x virtual images. This problem
does not occur by default for 6.1.0.x virtual images as samples are
not installed by default. But, the behavior for the 6.1.0.x virtual
images is the same if the samples are installed.
The log locations are different for the profile creation and the
augmentation operations. For the virtual images, the logs are located
at profile_root/logs/manageprofiles directory.
This applies to all the profiles and applies to both the Version 6.1.0.x
and the Version 7.0.x releases for WebSphere Hypervisor Edition.
In a native WebSphere Application Server environment, profiles
are stored in the opt/IBM/WebSphere/AppServer/Profiles directory.
IBM WebSphere Application Server Hypervisor Edition uses a different
location. On the virtual images, profiles are stored in the opt/IBM/WebSphere/Profiles directory.
Similarly, the profileRegistry.xml file is stored
in the <profile_root>/properties directory
for the virtual images, but is stored in the <app_server_root>/properties directory for native environments.