You can install the Application Client using Installation Manager response files.
You can install Installation Manager using the product media, using a file obtained from the Passport Advantage® site, or using a file containing the most current version of Installation Manager from the IBM® Installation Manager download website.
You can install Installation Manager using the product media, using a file obtained from the Passport Advantage site, or using a file containing the most current version of Installation Manager from the IBM Installation Manager download website.
You can install Installation Manager using the product media, using a file obtained from the Passport Advantage site, or using a file containing the most current version of Installation Manager from the IBM Installation Manager download website.
http://www.ibm.com/software/repositorymanager/com.ibm.websphere.APPCLIENT.v85
Whenever possible, you should use the remote web-based repositories so that you are accessing the most up-to-date installation files.
You can access the product repositories on the product media. Use Installation Manager to install the product from the product repositories on the media.
http://www.ibm.com/software/repositorymanager/com.ibm.websphere.APPCLIENT.v85
Whenever possible, you should use the remote web-based repositories so that you are accessing the most up-to-date installation files.
Using Installation Manager, you can work with response files to install the Application Client in a variety of ways. You can record a response file using the GUI as described in the following procedure, or you can generate a new response file by hand or by taking an example and modifying it.
IBMIM.exe -skipInstall "C:\temp\imRegistry"
-record C:\temp\install_response_file.xml
./IBMIM -skipInstall /var/temp/imRegistry
-record /var/temp/install_response_file.xml
./IBMIM -skipInstall user_home/var/temp/imRegistry
-record user_home/var/temp/install_response_file.xml
The -skipInstall operation should not be used on the actual agent data location used by Installation Manager. This is unsupported. Use a clean writable location, and re-use that location for future recording sessions.
For more information, read the IBM Installation Manager Version 1.6 Information Center or the IBM Installation Manager Version 1.5 Information Center.
https://downloads.mycorp.com:8080/WAS_85_repository
orhttp://www.ibm.com/software/repositorymanager/com.ibm.websphere.APPCLIENT.v85
Installation Manager searches its defined repositories for available packages.
If you already have the Application Client installed on your system, a message displays indicating that the Application Client is already installed. For a given Installation Manager, you can install only one Application Client.
The panel also displays the shared resources directory and disk-space information.
Symbolic links are not supported.
The Application Client cannot install properly if the target directory includes a semicolon.
A semicolon is the character
used to construct the class path on Windows systems.
This option installs the IBM Developer Kit, Java 2 Technology Edition.
This feature includes a development kit and a runtime-environment package. The runtime-environment package is always installed with the Java EE and Java thin application client feature even if this feature is not installed.
This option installs the Java 2 runtime environment.
This feature includes the Java 2 runtime environment of IBM Developer Kit, Java 2 Technology Edition.
This option installs the developer kit.
This feature includes the developer kit of IBM Developer Kit, Java 2 Technology Edition.
This option installs executable and source-code examples of programming in both Java EE and non-Java EE client environments.
IBM thin clients and resource adapters provide a set of clients and resource adapters for a variety of technologies, such as JAX-WS, JAX-RPC, JAX-RS, XML, EJB, JPA, JMS, and more. An embeddable container runs in a standalone Java Platform, Standard Edition environment. For example, you can use the embeddable EJB container to run enterprise beans outside the application server.
This option installs the runtime for standalone thin clients.
This option installs the embeddable EJB container.
The embeddable EJB container is a Java Archive (JAR) file that you can use to run enterprise beans in a standalone Java Platform, Standard Edition environment. You can run enterprise beans using this embeddable container outside the application server. The embeddable EJB container is a part of the EJB 3.1 specification and is primarily used for unit testing enterprise beans business logic.
IBMIM.exe -skipInstall "C:\temp\imRegistry"
-keyring C:\IM\im.keyring
-record C:\temp\keyring_response_file.xml
./IBMIM -skipInstall /var/temp/imRegistry
-keyring /var/IM/im.keyring
-record /var/temp/keyring_response_file.xml
./IBMIM -skipInstall user_home/var/temp/imRegistry
-keyring user_home/var/IM/im.keyring
-record user_home/var/temp/keyring_response_file.xml
For more information, read the IBM Installation Manager Version 1.6 Information Center or the IBM Installation Manager Version 1.5 Information Center.
There is no migration path from keyring files to storage files because of the differences in the file structures. You must create a storage file to replace a keyring file.
For more information on using the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file, see the Installation Manager Version 1.6 Information Center.
imcl.exe -acceptLicense
input C:\temp\keyring_response_file.xml
-log C:\temp\keyring_log.xml
./imcl -acceptLicense
input /var/temp/keyring_response_file.xml
-log /var/temp/keyring_log.xml
./imcl -acceptLicense
input user_home/var/temp/keyring_response_file.xml
-log user_home/var/temp/keyring_log.xml
There is no migration path from keyring files to storage files because of the differences in the file structures. You must create a storage file to replace a keyring file.
For more information on using the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file, see the Installation Manager Version 1.6 Information Center.
imcl.exe -acceptLicense
input C:\temp\install_response_file.xml
-log C:\temp\install_log.xml
-keyring C:\IM\im.keyring
./imcl -acceptLicense
input /var/temp/install_response_file.xml
-log /var/temp/install_log.xml
-keyring /var/IM/im.keyring
./imcl -acceptLicense
input user_home/var/temp/install_response_file.xml
-log user_home/var/temp/install_log.xml
-keyring user_home/var/IM/im.keyring
Read the IBM Installation Manager Version 1.6 Information Center or the IBM Installation Manager Version 1.5 Information Center for more information.
<?xml version="1.0" encoding="UTF-8"?>
<agent-input clean="true" temporary="true">
<server>
<repository location="http://www.ibm.com/software/repositorymanager/com.ibm.websphere.APPCLIENT.v85" />
</server>
<install modify='false'>
<offering id='com.ibm.websphere.APPCLIENT.v85'
profile='Application Client for IBM WebSphere Application Server V8.5'
features='javaee.thinclient.core.feature,javaruntime,developerkit,embeddablecontainer' installFixes='none'/>
</install>
<profile id='Application Client for IBM WebSphere Application Server V8.5'
installLocation='C:\Program Files\IBM\WebSphere\AppClient'>
<data key='eclipseLocation' value='C:\Program Files\IBM\WebSphere\AppClient'/>
<data key='user.import.profile' value='false'/>
<data key='user.select.64bit.image,com.ibm.websphere.APPCLIENT.v85' value='false'/>
<data key='user.appclient.serverHostname' value='localhost'/>
<data key='user.appclient.serverPort' value='2809'/>
<data key='cic.selector.nl' value='en'/>
</profile>
</agent-input>