The product code for the Web 2.0 and Mobile Toolkit is installed using IBM® Installation Manager Version 1.5.2 or later.
This copy of the offering must be mounted at this location every time Installation Manager accesses it to install, uninstall, or modify it. This does not have to be the same location at which the offering will be mounted when used in production.
Installation Manager requires that every installed product or group of products have its own installation location.
chown IMADMIN:IMGROUP /usr/lpp/Web2Mobile/V11
chmod 775 /usr/lpp/Web2Mobile/V11
cd /InstallationManager/bin/eclipse/tools
zCreateFileSystem.sh -name WAS.V85.SWEBHFS -type ZFS
-megabytes 150 30 -volume PRV005
-mountpoint /usr/lpp/Web2Mobile/V11
-owner IMADMIN -group IMGROUP
cd /InstallationManager/bin/eclipse/tools
installation_manager_binaries_directory/eclipse/tools/imutilsc saveCredential
-keyring keyring_file
-userName user_ID -userPassword user_password
-url http://www.ibm.com/software/repositorymanager/com.ibm.websphere.W2MTK.v11/repository.xml
where
keyring_file is the path and file name of the keyring to be created,
and user_ID and user_password are the universal IBM
user ID and password that you use to access protected IBM software websites./opt/IBM/InstallationManager/eclipse/tools/imutilsc saveCredential
-keyring /u/jane/IBM.software.keyring
-userName jsmith01 -userPassword 732Ukelele
-url http://www.ibm.com/software/repositorymanager/com.ibm.websphere.W2MTK.v11/repository.xml
Make sure that the keyring file is readable by the Installation Manager user ID.
Starting in Installation Manager Version 1.6.2, the -keyring and -password options that were used to access credentials in a key ring file are deprecated. For Installation Manager Version 1.6.2 and later, use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file.
In Version 1.7, the format of the secure storage file is revised, and is no longer compatible with versions of Installation Manager before version 1.7. Update Installation Manager to version 1.7 or higher and then re-create and replace any secure storage files that you created with earlier versions.
There is no migration path from key ring files to storage files because of the differences in the file structures. You must create a storage file to replace a key ring file. For more information about using the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file, see the Installation Manager Version 1.6 documentation.
imcl listAvailablePackages -repositories list_of_repository_locations
You
should see one or more levels of the Web 2.0 and Mobile Toolkit offering, com.ibm.websphere.W2MTK.v11.The list_of_repository_locations should include the path to the initial product repository and the paths to any additional service repositories. Separate URLs in the list_of_repository_locations with commas.
imcl listAvailablePackages
-repositories /opt/repository/W2MTK
-useServiceRepository
-keyring /u/jane/IBM.software.keyring
Starting in Installation Manager Version 1.6.2, the -keyring and -password options that were used to access credentials in a key ring file are deprecated. For Installation Manager Version 1.6.2 and later, use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file.
In Version 1.7, the format of the secure storage file is revised, and is no longer compatible with versions of Installation Manager before version 1.7. Update Installation Manager to version 1.7 or higher and then re-create and replace any secure storage files that you created with earlier versions.
There is no migration path from key ring files to storage files because of the differences in the file structures. You must create a storage file to replace a key ring file. For more information about using the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file, see the Installation Manager Version 1.6 documentation.
imcl install com.ibm.websphere.W2MTK.v11
-installationDirectory installation_location
-repositories list_of_repository_locations
-sharedResourcesDirectory shared_data_location
-acceptLicense
[-useServiceRepository -keyring keyring_file]
[-installFixes <all | recommended | none> ]
The -sharedResourcesDirectory parameter points to a directory in which Installation Manager will store artifacts from the repository during installation processing. This value is set the first time a product is installed with a particular Installation Manager. You can omit this parameter after the shared resources directory has been set.
If you do not specify the product version to be installed, Installation Manager will install the latest version of the product along with any fixes in the repository locations. You can prevent the installation of fixes by specifying -installFixes none or install only recommended fixes by specifying -installFixes recommended.
If you specify the product version to be installed, any fixes in the repository locations will only be installed if you specify -installFixes recommended or -installFixes all.
By specifying -acceptLicense, you accept the terms of the product license contained in the repository.
Logs for the installation can be found in the logs subdirectory of the Installation Manager runtime data location.