Skip to content

IBM WebSphere Portal - Process Steps

Deploy Portal WAR

Deploys a WAR on a WebSphere Portal server

NameTypeDescriptionRequired
Application WAR file nameStringThe name of the application WAR file. If left blank, the name of the component is usedNo
Application context rootStringSpecify the applications context root. If left blank, /wps/${Application display name} is used as the default application context rootNo
Application display nameStringSpecify application display name in the administative console. If left blank, the default display name used is constructed using the uid of the application mentioned in the portlet.xml file in the WAR. The logic to construct the display name is to replace all whitespace characters in the uid by an underscore character _ and prefix PA_ to itNo
Portal Server context rootStringSpecify the portal servers context root. If left blank, /wps is used as the default portal server context rootNo
Use soap.client.props fileBooleanUse soap.client.props file for Portal administrator credentialNo
Virtual Portal contextStringIf deploying the WAR on a virtual portal, specify the virtual portal context rootNo
Virtual Portal hostnameStringIf deploying the WAR on a virtual portal, specify the virtual portal hostnameNo
WebSphere Portal server installation homeStringPortal installation homeNo
WebSphere Portal server profile homeStringPortal server profile homeNo
WebSphere portal server administrator passwordPasswordWebSphere portal server administrator user passwordNo
WebSphere portal server administrator usernameStringWebSphere portal server administrator usernameNo
WebSphere portal server configuration portStringWebSphere portal server configuration portNo

Deploy Theme

Deploys the static contents of a theme along with the related skins on a WebSphere Portal server

NameTypeDescriptionRequired
Portal Server context rootStringSpecify the portal servers context root. If left blank, /wps is used as the default portal server context rootNo
Theme context rootStringThe context root of the web application representing the theme. If left blank, the name of the WAR/ZIP filename containing the theme artifacts is used.No
Theme default skinStringThe uniquename of the skin to be used as the default skin for this theme. If left blank, the first child directory of the themes/skins directory is used.No
Theme layout directoryStringThe directory in the theme WAR/ZIP file under the /themes directory that contains the theme layout detailsNo
Theme resource rootStringThe resource root entry for the theme. If left blank, the name of the WAR/ZIP filename containing the theme artifacts is used.No
Theme static content file nameStringThe name of the file containing the theme static contents. Valid file extensions are .war and .zip. The default extension is .war. If left blank, the name of the component is used.No
Theme template directoryStringThe name of the directory in the theme WAR/ZIP file that contains the theme template. All theme templates are usually placed under the /themes directory in the WAR/ZIP file. If left blank, the first child directory of the /themes directory is used.No
Theme titleStringThe theme title in different locales of choice. Format: LOCALE=TITLE,[LOCALE=TITLE]. Supply the theme title in different locales as a comma separated list of locale title pairs. All leading and trailing whitespace characters in the pairs will be ignored. If left blank, the default locale used is en and title is set to the name of the component.No
Theme unique nameStringThe uniquename for this theme within the Portal server. If left blank, the uniquename is computed as followsthe string com.ibm.urbancode.customTheme. is prefixed to the WAR/ZIP filename containing the theme artifacts.No
Use soap.client.props fileBooleanUse soap.client.props file for Portal administrator credentialNo
Virtual Portal contextStringIf invoking on a virtual portal, specify the virtual portal context rootNo
Virtual Portal hostnameStringIf invoking on a virtual portal, specify the virtual portal hostnameNo
WebSphere Portal server installation homeStringPortal installation homeNo
WebSphere Portal server profile homeStringPortal server profile homeNo
WebSphere portal server administrator passwordPasswordWebSphere portal server administrator user passwordNo
WebSphere portal server administrator usernameStringWebSphere portal server administrator usernameNo
WebSphere portal server configuration portStringWebSphere portal server configuration portNo

Execute ConfigEngine command

Executes the specified ConfigEngine command on a WebSphere Portal server

NameTypeDescriptionRequired
ConfigEngine commandStringThe ConfigEngine command to execute. If left blank, the component name is usedNo
OptionsStringFormat: NAME=VALUE,[NAME=VALUE]. Supply the name value pairs to be used as arguments to the ConfigEngine tool. This argument can be supplied multiple times for all of the additional parameters used by the ConfigEngine. All leading and trailing whitespace characters in the name value will be ignored. Do not specify the WAS and Portal administrator credentials here.No
Use wkplc.properties fileBooleanIf selected, the wkplc.properties file is used to read WAS and Portal administrator passwords fromNo
WebSphere Portal server profile homeStringPortal server profile homeNo
WebSphere application server administrator passwordPasswordWebSphere application server administrator user passwordNo
WebSphere portal server administrator passwordPasswordWebSphere portal server administrator user passwordNo

Install PAA

Installs a portal application archive (.paa) on a WebSphere Portal server

NameTypeDescriptionRequired
Additional CommandLine ArgumentsStringNew line separated list of additional commandline arguments to pass to the deploy-paa command (i.e. -DforceDeploy=true)No
Assembly nameStringName of the portal assembly to deploy. If left blank, the name of the component is usedNo
Create WCM properties fileBooleanIf selected, the WCM properties file is created in the paa/${appName} directoryNo
Maximum time in minutes to wait for node synchronizationStringIf installing on a clustered environment, define this value for the deploy-paa taskNo
Maximum time in minutes to wait for wplc-wait-for-sync-to-complete taskStringIf installing on a clustered environment, define this value for the deploy-paa taskNo
PAA filenameStringName of the .paa file to install. If left blank, the name of the component is usedNo
Use wkplc.properties fileBooleanIf selected, the wkplc.properties file is used to read WAS and Portal administrator passwords fromNo
Virtual Portal contextStringIf installing on a virtual portal, include the virtual portal contextNo
Virtual Portal host nameStringIf installing on a virtual portal, include the virtual portal host nameNo
WebSphere Portal server profile homeStringPortal server profile homeNo
WebSphere application server administrator passwordPasswordWebSphere application server administrator user passwordNo
WebSphere portal server administrator passwordPasswordWebSphere portal server administrator user passwordNo

Invoke XMLAccess script

Executes an XMLAccess script on a WebSphere Portal server

NameTypeDescriptionRequired
Portal Server context rootStringSpecify the portal servers context root. If left blank, /wps is used as the default portal server context rootNo
Use soap.client.props fileBooleanUse soap.client.props file for Portal administrator credentialNo
Virtual Portal contextStringIf invoking on a virtual portal, specify the virtual portal context rootNo
Virtual Portal hostnameStringIf invoking on a virtual portal, specify the virtual portal hostnameNo
WebSphere Portal server profile homeStringPortal server profile homeNo
WebSphere portal server administrator passwordPasswordWebSphere portal server administrator user passwordNo
WebSphere portal server administrator usernameStringWebSphere portal server administrator usernameNo
WebSphere portal server configuration portStringWebSphere portal server configuration portNo
XML script file nameStringThe name of the file containing the XML script for XMLAccess tool. If left blank, the name of the component is used.No