warPackager

The Web Application Manager (insweb) uses a warPackager utility to create a WAR file from files in the staging directory and regenerate the application_map.xml, system_preferences.xml, and web.xml files. The following table lists the command flags and options. Flag Option Description -a No option Generates the master application map file (application_map.xml) in the location specified by the -d option. -d staging-area Specifies the staging area path for the Web application. This option is required whenever you run the utility. If -d is the only option passed into the warPackager utility, there must be solutions.dat, webapp.dat, and context_params.dat files in the staging area directory, or the utility errors out. If those files exist, then the utility generates all files (the same as choosing -apxw). -I icd-directory The directory under which the ICD directory is located. -p No option Generates the master system preferences file (system_preferences.xml) in the location specified by the -d option. -t No option Generates template webapp.dat and context_params.dat files in the location specified by the -d option. It is used only in conjunction with the -d option. If the -t option is used with any other option, then the utility errors out. When the -t and -d options are used together, only a solutions.dat file must exist in the staging area. The utility then generates only the webapp.dat and context_params.dat template files. If either of these template files already exist in the staging area, the utility prompts users asking if they want to overwrite these files. -w No option Generates the WAR file in the location specified by the -d option (using the value given in the webapp.dat file for the [WAR_NAME] tag). -x No option Generates the web.xml file in the location specified by the -d option. Optionally, you can run the warPackager utility directly by performing the following steps: Set the CLASSPATH environment variable to include the WEB_ROOT/java/classes directory. Navigate to the WEB_ROOT directory. Enter the following command:1 Copy warPackager -d deployment-directory [-i icd-directory] [-t] | [-apxw] The following examples show how the warPackager utility can be used with its various options: Generate all files into the scratch/webroot/mywebapp directory: Copy warPackager -d /scratch/webroot/mywebapp or Copy warPackager -d /scratch/webroot/mywebapp -apxw Generate template files into the scratch/webroot/mywebapp directory: Copy warPackager -d /scratch/webroot/mywebapp -t Generate only the web.xml file and the WAR file in the /scratch/webroot/mywebapp directory: Copy warPackager -d /scratch/webroot/mywebapp -xw Generate only the master application map and system preferences files in the /scratch/webroot/mywebapp directory: Copy warPackager -d /scratch/webroot/mywebapp -ap Related Topics Teamcenter Installation on Linux Using TEM Teamcenter Installation on Windows Using TEM Teamcenter Rich Client Installation on Linux Using TEM Teamcenter Rich Client Installation on Windows Using TEM 1 Linux systems require you to use an uppercase P when you enter the warPackager command.