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.
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 8.5 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:
The log locations are different for the profile creation and the augmentation operations. For the virtual images, the logs are located in the profile_root/logs/manageprofiles directory. This applies to all profiles.
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.