Deploying a console module

About this task

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.

If you need to update the version of a console module, you must perform these steps.
  1. Remove the console module.
  2. Update the module with the required changes.
  3. 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

  1. 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.
  2. 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.
  3. [iSeries] Grant the QEJBSVR profile the authority needed to complete the task. From an i5/OS command prompt, issue this command:
    CHGAUT OBJ('path_to_war') USER(QEJBSVR) DTAAUT(*RWX) OBJAUT(*ALL)
  4. [AIX HP-UX Linux Solaris Windows] [z/OS] Open a command prompt.
  5. [AIX HP-UX Linux Solaris Windows] [z/OS] 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.
  6. Start the wsadmin scripting client. If the server is not running, use the -conntype NONE option to run in local mode.
  7. 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  -usedefaultbindings 
    -contextroot /context 
    -MapWebModToVH {{.* .* admin_host}}}
    
    
    Note: The values of the -contents and -contenturi are case sensitive and should match the war file name that you are ready to deploy. The option custom paavalidation=true is optional.
    [AIX HP-UX Linux Solaris Windows] [z/OS] 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  -usedefaultbindings
    -contextroot /ibm/pagelayout 
    -MapWebModToVH {{.* .* admin_host}}}
    [iSeries] For example:
    $AdminApp update isclite modulefile {
    -operation add 
    -contents app_server_root/systemApps/isclite.ear/pagelayout.war 
    -contenturi pagelayout.war 
    -custom paavalidation=true  -usedefaultbindings
    -contextroot /pagelayout 
    -MapWebModToVH {{.* .* admin_host}}}
    The following messages are displayed if the deployment is successful.[AIX HP-UX Linux Solaris Windows] [z/OS]
    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.
    [iSeries]
    Update of isclite has started.
    ADMA5009I: An application archive is extracted at profile_root/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.
  8. 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:

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.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 4:28:44 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-mp&topic=deploy_comp
File name: deploy_comp.html