If Access Manager is installed on BEA WebLogic, IBM WebSphere, or Sun ONE Application Server, you must update and redeploy services.war before you can see any changes in the user interface. Once you’ve made changes to the authentication GUI files, regardless of the brand of web container you’re using, it is a good practice to update and redeploy the services.war file. When you update and redeploy services.war, you overwrite the default GUI files with your changes, and the changed files are placed in their proper locations. The section Staging Area for Files to be Customized provides background information on this file.
cd AccessManager-base/SUNWam
This is the directory in which the WARs are kept.
jar -uvf WARfilename.war < path_to_modified_file>
The -uvf option replaces the old file with the newly modified file. For example:
jar -uvf services.war newfile/index.html
replaces the index.html file in console.war with the index.html file located in AccessManager-base/SUNWam/newfile.
rm newfile/index.html
Deletes the modified file.
The services.war will be in the following directory:
AccessManager-base/SUNWam
Depending upon the brand of web container you are using, execute one of the following commands.
java weblogic.deploy -url ServerURL -component {ServerDeployURI}: { WL61 Server} deploy WL61AdminPassword {ServerDeployURI }
{AccessManager-base}/{SUNWam}/services.war
In this example,
ServerURL uses the form protocol:// host:port Example: http://abc.com:58080
ServerDeployURI represents the server Universal Resource Identifier Example: amserver
WL61 Server represents the Weblogic Server nam.e Example: name.com
asadmin deploy -u IAS7Admin -w IAS7AdminPassword -H HostName -p IAS7AdminPort --type web SECURE_FLAG --contextroot
ServerDeployURI --name amserver --instance IAS7Instance {AccessManager-base}/{SUNWam}/services.war
See the deployment documentation that comes with the IBM WebSphere product:
http://www-3.ibm.com/software/webservers/studio/doc/v40/studioguide/ en/html/sdsscenario1.html