Tweet
In order to get a full list of the answers given to a particular OTM / GC3 installation, just open up the <gc3_install_dir>/installer-results.txt file. It looks like:
This file lists all of the variables and values used by the installer. For instance, APP_FQDN is the fully-qualified domain name of the GC3/OTM application server. APP_JVM_MEMORY is the amount of memory that the App server will use (WebLogic or WebSphere). DB_SID is the Oracle SID of the database that GC3/OTM will connect to.
For most purposes, you can ignore variables that look like “lax.nl.*” or “prop.*”. These are just internal variables and environment variables used by or detected by the installer.
In addition, if your installer is OTM / GC3 v5.0 GA2 or newer, you can look at an additional file: <gc3_install_dir>/install/install_variables.txt. This file contains a subset of the information in installer-results.txt and has less extraneous information. It looks like:
While most of the variables are self-explanatory, some of them are a bit cryptic. If you have any questions about them, just post a response here and I’ll help you out.
Code:
... APP_FQDN=testapp02.mavenwire.com ... APP_JVM_MEMORY=1400 ... DB_SID=gc3testdb02 ...
For most purposes, you can ignore variables that look like “lax.nl.*” or “prop.*”. These are just internal variables and environment variables used by or detected by the installer.
In addition, if your installer is OTM / GC3 v5.0 GA2 or newer, you can look at an additional file: <gc3_install_dir>/install/install_variables.txt. This file contains a subset of the information in installer-results.txt and has less extraneous information. It looks like:
Code:
... [APP_FQDN]=testapp02.mavenwire.com ... [APP_JVM_MEMORY]=1400 ... [DB_SID]=gc3testdb02 ...