After you create the WAR file for a console module, you can deploy
the console module to a system where the runtime for Integrated Solutions
Console is installed and then test that the console module works correctly.
Only one instance of a console module can be deployed on an Integrated Solutions
Console installation. This rule applies even if the versions of the console
module are different.
About this task
If you need to update the version of a console module, you must
perform these steps.
- Remove the console module.
- Update the module with the required changes.
- Reissue the deploy command.
To deploy a console module on a system where the runtime for Integrated
Solutions Console is installed, perform the following procedure:
Procedure
- Go to the machine where the Integrated Solutions Console runtime
is installed. You can also use a machine that has remote access to the drive
where the runtime is installed.
- Copy the console module WAR file to the app_server_root/systemApps/isclite.ear directory. As an alternative, you can extract the WAR file into a subdirectory
of this location using the WAR file name for the subdirectory. For example,
you would extract pagelayout.war to the app_server_root/systemApps/isclite.ear/pagelayout.war directory.
Open a command prompt.
If you want to deploy the console module to
an application server profile other than the default, change to the app_server_root/profiles/profile_name/bin directory
and enter the setupCmdLine.[bat|sh] command. If you want to deploy to the
default application server profile, change to the app_server_root/bin directory.
- Start the wsadmin scripting
client. If the server is not running, use the -conntype NONE option
to run in local mode.
- At the wsadmin command prompt, enter the
command syntax. The following example presents the syntax:
$AdminApp update isclite modulefile {
-operation add
-contents path_to_war
-contenturi war_filename
-custom paavalidation=true
-custom containWebServices=true|false
-usedefaultbindings -contextroot /context
-MapWebModToVH {{.* .* admin_host}}
-MapModulesToServers {{.* .*.war,.* WebSphere:cell=cellname,node=nodename,server=servername}}}
Notes:
- The values of the -contents and -contenturi options are case sensitive
and should match the war file name that you are ready to deploy.
- Specifying -custom paavalidation=true causes the deployment
to validate the XML descriptors for the console module package before deployment.
This is optional.
- Set the option -custom containWebServices=true only
if the package contains a Web service. This setting invokes more deployment
processing to locate and setup the Web service. The default for this option
is true. If the package does not contain any Web services, be sure to set
this option to false for more efficient deployment.
- Use the -MapModulesToServers option when deploying to an agent profile.
![[z/OS]](../../ngzos.gif)
As an example, if you were to deploy the
page layout sample to a Windows machine, the command would be as follows.
$AdminApp update isclite modulefile {
-operation add
-contents C://WebSphere//AppServer//systemApps//isclite.ear//pagelayout.war
-contenturi pagelayout.war
-custom paavalidation=true
-custom containWebServices=false
-usedefaultbindings -contextroot /ibm/pagelayout
-MapWebModToVH {{.* .* admin_host}}
-MapModulesToServers {{.* .*.war,.* WebSphere:cell=cell_A,node=node_B,server=server_C}}}
The following messages are displayed if the deployment is successful.
Update of isclite has started.
ADMA5009I: An application archive is extracted at D:\IBM\WebSphere_63\AppServer\
profiles\AppSrv01\wstemp\wstemp\app_10793d84b8e\ext\pagelayout.war
ADMA5064I: FileMergeTask completed successfully for isclite.
ADMA5005I: The application isclite is configured in the WebSphere Application Se
rver repository.
ADMA5005I: The application isclite is configured in the WebSphere Application Se
rver repository.
ADMA5110I: The application isclite is installed as a hidden application and will
not be exposed via administrative interfaces such as GUI client, wsadmin or MBe
an Java API. In order to perform management operations on this application, the
application name must be known.
CWLAA10001I: The Integrated Solutions Console module was deployed successfully.
ADMA5005I: The application isclite is configured in the WebSphere Application Se
rver repository.
ADMA5011I: The cleanup of the temp directory for application isclite is complete
.
Update of isclite has ended.
- After the deployment has completed successfully, save
your work by issuing the following command:
$AdminConfig save
Results
If the deployment is successful, the WAR file contents are extracted
to the
/systemApps/isclite.war directory and the module
metadata is copied to the following directory:
- profile_root/config/cells/cellname/applications/isclite.ear/deployments/isclite
To view your console module, you must log back in to the console.
Make sure the navigation is updated correctly. If so, select the new navigation
nodes verify that the new pages and console modules are rendered correctly.