Deploy the idp1.war
Case 1: Access Manager is installed on Sun Java System Web Server
a. Before you can deploy a web application manually, you must make
sure that the server_root/bin/https/httpadmin/bin
directory is in
your path and that the IWS_SERVER_HOME
environment variable is set to
your server_root
directory.
b. Enter the following command
wdeploy deploy -u uri_path -i instance -v vs_id [-d directory]
war_file
where
* uri_path is the URI prefix for the web application.
* instance is the server instance name.
* vs_id is the virtual server ID.
* directory is the directory to which the application is deployed,
or from which the application is deleted. If not specified for
deployment, the application is deployed to the document root
directory.
* war_file is the WAR file name.
For example:
wdeploy deploy -u /idp1 -i www.idp1.com -v https-www.idp1.com
-d <begin_dir>/web-apps/idp1 idp1.war
c. Restart web server.
Case 2: Access Manager is installed on Sun Java System Application Server
a. Use the asadmin
deploy command to deploy the WAR
module. The syntax
is as follows:
asadmin deploy --user admin_user [--password admin_password]
[--passwordfile password_file] --host hostname
--port adminport [--secure | -s] [--virtualservers virtual_servers]
[--type aplication|ejb|web|connector] [--contextroot contextroot]
[--force=true] [--precompilejsp=false] [--verify=false]
[--name component_name] [--upload=true] [--retrieve local_dirpath]
[--instance instance_name] filepath
For example, the following command deploys a web application as an
individual module:
asadmin deploy --user admin --password pswd1234
--host www.idp1.com --port 4848 --type web --contextroot idp1
--instance server1 idp1.war
b. Restart Application Server
Case 3: Access Manager is installed on BEA Web logic
a. Set up your development environment so that WebLogic
Server classes
are in your system CLASSPATH
and the JDK
is available. You
can use the setEnv
script located in the config/mydomain
directory to
set your environment.
b. Enter the following command:
java weblogic.deploy -port port_number -host host_name
-component application:target deploy password application source
where:
host_name is the name of the machine hosting WebLogic Server
port_number is the port number where WebLogic Server is listening
for requests
application is the name you want to assign to this Web Application.
target is the name of a server, cluster or virtual host to be
targeted by this Web Application. You can enter multiple targets,
separated by a comma.
password is your system administration password
source is the full pathname of the WAR file you want to deploy, or
the full pathname of a directory containing a Web Application in
exploded directory format.
For example:
java weblogic.deploy -port 7001 -host www.idp1.com
-component idp1:myserver deploy pswd1234 idp1 idp1.war
c. Restart WebLogic Server.
Case 4: Access Manager is installed on IBM Web Sphere
a. Open admin client
<WEBSPHERE_INSTALL_DIR>/WebSphere/AppServer/bin/adminclient.sh
b. Right click on "Enterprise Applications" and select
"install Enterprise Application"
c. Select install stand-alone module
d. Specify path for idp1.war
e. Specify IDP1
as Application Name
f. Specify /idp1
as Context root for web module
g. Keep selecting Next until you get Finish and then select Finish
h. Right click on your node name and select "Regen Webserver Plugin"
i. Restart web server
/opt/IBMHTTPD/bin/apachectl start
j. Restart application server
<WEBSPHERE_INSTALL_DIR>/WebSphere/AppServer/bin/startupServer.sh
Note:
If you want to have customized version of all the JSPs available in
<begin_dir>/web-apps/services/config/federation/default/
, you can
create a sub folder under <begin_dir>/web-apps/services/config/federation/
with the
IDP1
's meta alias name (In given idp1MetaData.xml
it is entered as
www.idp1.com
). Then copy all these JSPs in this newly created sub folder
and modify them for the desired look and feel.