Develop JACL management scripts for the WebSphere Portal

The WebSphere Portal Server is an important platform for IBM for consolidation and collaboration. WebSphere Portal Server provides three ways for users to manage the Portlet, XML Configuration Interface, and Portal scripting Interface through a web-based approach. Web-based Management Portlet requires users to do a variety of manual operations, not automated management operations, only for simple management operations. XML Configuration Interface requires users to write XML configuration files, but the file is cumbersome to write and lacks process control and flexibility. Portal scripting Interface is introduced from version 5.1 and is refined and enhanced in version 6.0, and the JACL approach to writing management scripts is more flexible than in the first two ways.

Target Audience

The reader should have some experience in using and managing WebSphere Portal, and should have the basic knowledge of writing JACL scripts.

Portal Scripting Interface is a JACL-based scripting interface provided by the IBM WebSphere Portal. This article takes a specific JACL script as an example to show you how to write a WebSphere portal management script through portal scripting Interface.

How to run Portal scripting Interface

Portal Scripting Interface is a JACL-based management program provided by the WebSphere portal Server. Under Wps_home/bin There is a script program Wpscript.bat (non-Windows platform corresponds to wpscript.sh), which is the scripting management interface of the WebSphere Portal. Wpscript.bat need to run at the command line, there are two ways to use the Portal scripting Interface:

Interactive mode: At the command line, one side of the JACL script to explain the operation, more suitable for a number of simple and one-time operations;

Submit scripts: Write the JACL script in advance, and then pass the JACL script file name as a command-line parameter, which is useful for complex operations and actions that need to be performed repeatedly.

The Wpscript.bat method is called as follows:

Listing 1 running Portal Scripting Interface

wpscript.bat　–conntype　<conntype>　-port　<port>　-user　<admin_id>
-password　<password>　-f　<jacl　filename>

Here is a description of the parameters used in the above command:

-conntype: Connection mode, optional parameters, default to SOAP;

-port: The connection port, corresponds to the Wpssoapport attribute value in the wpconfig.properties;

-user and-password: The user name and password used to create the connection;

The pathname of the-f:jacl file, if this argument is omitted by way of interaction.