IBM Express Runtime Version 2.1 README

To install Express Runtime, see the Express Runtime 2.1 InfoCenter, which is accessible from the LaunchPad.

Program Command

Linux LaunchPad LinuxLaunchpad

Linux Installation LinuxSetup

Linux on POWER LaunchPad LinuxPPCLaunchpad

Linux on POWER Installation LinuxPPCSetup

Windows LaunchPad WindowsLaunchpad.exe

Windows Installation WindowsSetup.exe

See the license directory in your installation path for product license and third-party license and notice files.

Program	Command
Linux LaunchPad	LinuxLaunchpad
Linux Installation	LinuxSetup
Linux on POWER LaunchPad	LinuxPPCLaunchpad
Linux on POWER Installation	LinuxPPCSetup
Windows LaunchPad	WindowsLaunchpad.exe
Windows Installation	WindowsSetup.exe

Known development issues
    Log on with administrator authority to install
    Log on with administrator authority to use Launchpad and First Steps links
    Installing as root user on SUSE LINUX
    IBM Installation Agent required for deploying middleware to remote computers
    Linux shortcuts on Application menu
    Deployment wizard cannot connect to a Linux target computer
    Double-byte word wrapping in deployment wizard
    Location of Eclipse .log file
    Solution generation fails with the message, "Can't find file C:\IBM\Runtime21\SolutionEnabler\workspace\Sampledata3\src\?????????.sxml"
    Customized solution license files require lowercased HTML tags
    Migrating wrappers to Express Runtime 2.1
    Schema changes from Version 1.1

Known issues with component software
    IBM HTTP Server port not set to 80
    Ports for WebSphere Application Server and IBM HTTP Server on OS/400 (i5/OS)
    Period in directory name
    Managing multiple IBM HTTP Server installations on one computer running Windows
    Redeployment of WebSphere Application Server - Express fails
    Reinstallation of console module fails
    Exception to message about exceeding DB2 processors
    IBM DB2 UDB post-installation instructions

Documentation issues
    Supported Web browser required for documentation
    Displaying console InfoCenter in simplified Chinese requires "zh-cn" language preference
    Some languages must use browsers configured to use the UTF-8 codepage
    Supported platforms for Linux listed incorrectly
    Incorrect reference to HTTP plugin
    Accessing the Javadoc for the support framework
    Description of supplied wrappers missing from InfoCenter
    IBM Express Runtime information Web site

Messages
    IRU00129
    IRU03026
    IRU10950

Known development issues

Log on with administrator authority to install

To install IBM Express Runtime, you must be logged on to the target computer as a user with administrator authority. The installation fails if you are not logged on as an administrator, and there might not be any error messages logged to IRU_Install.log indicating the problem. If the installation fails and no information is available in the log file, exit the installation, log in as a user with administrator authority, and try the installation again.

Log on with administrator authority to use Launchpad and First Steps links

To use IBM Express Runtime you must log on to the computer with administrator authority. If you are not logged on as an administrator, links from the Launchpad and First Steps dialog will not work. If the links from the Launchpad or First Steps do not work, check that you have administrative authority. No error message displays when you do not have administrative authority.

Installing as root user on SUSE LINUX

A SUSE LINUX user must log in and install Express Runtime program as the root user. If you switch to root after logging in by using the su -root command and then install Express Runtime on SUSE LINUX, some of the files do not install correctly.

IBM Installation Agent required for deploying middleware to remote computers

If you are using Express Runtime to install middleware directly to a computer that is remote to yours, you must first install the IBM Installation Agent on that computer.

With the exception of the localhost, all the target computers that you deploy a solution to must have the IBM Installation Agent installed and running in order for the solution to be successfully deployed.

More information regarding the IBM Installation Agent, including installation directions, is in the IBM Installation Agent InfoCenter.

Linux shortcuts on Application menu

On the Linux platform, the Express Runtime menu shortcuts might also appear under the Application menu.

Deployment wizard cannot connect to a Linux target computer

The /etc/hosts file in a Linux distribution must be configured properly to enable RMI. If the Linux target computer is not properly configured, you will encounter the following Java exception when the deployment wizard attempts to connect.


Java.lang.NullPointerException

    	at sun.rmi.transport.tcp.TCPConnection.getOutputStream(TCPConnection.java:83)

    	at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:206)

    	at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:188)

To configure the Linux target computer, modify the /etc/hosts file on the target computer as follows:

Open the /etc/hosts file in an editor.
There should be an entry for the loop back address, similar to 127.0.0.2 localhost.localdomain localhost.
Check to see if the actual hostname of the computer is included in this entry. An entry containing the actual hostname might look similar to 127.0.0.1 testmachine.ibm.com testmachine localhost. localdomain localhost, where testmachine.ibm.com testmachine is the hostname. If the actual hostname is included, remove both the fully-qualified and short name versions of the hostname from the entry. In the example noted, you would remove testmachine.ibm.com testmachine.
If the actual IP address and hostname of the target computer are not included in the hosts file, add them. For example, 9.42.76.1000 testmachine100.ibm.com testmachine100.
Restart the network.

Double-byte word wrapping in deployment wizard

In the deployment wizard, double-byte words may wrap in the middle of the word. If you encounter this behavior, open your double-byte translated application and solution files, locate the translated strings for the following elements, and insert a space in locations where it is acceptable to wrap your sentences.

Application wrappers (<application filename>_<double-byte language>.axml)
- labelText element for all stringVariable, booleanVariable, and passwordVariable elements.
Solution wrapper (<solution filename>_<double-byte language>.sxml)
- description element for all installTask and manualTask elements.

Location of Eclipse .log file

The Eclipse .log file is stored in workspace\.metadata\.log, where workspace is the location where all a user's files and projects are stored.

Solution generation fails with the message, "Can't find file C:\IBM\Runtime21\SolutionEnabler\workspace\Sampledata3\src\?????????.sxml"

Solution generation fails when the generated command line or wrapper file name contains GB18030 characters. The solution is to enter the characters as Unicode or GB2312 characters.

Customized solution license files need lowercased HTML tags

When creating customized license files for a solution that you generate through the export wizard, the HTML tags in the license files must be lowercased. If the tags are uppercased or in mixed case, the user either sees error message IRU08137 or the license acceptance panel is skipped when the solution is launched.

Migrating wrappers to Express Runtime 2.1

This section describes how to migrate applications and solutions created using Integrated Runtime, Version 1.1 to Express Runtime, Version 2.1.

Move project and deployment package files.

If you are moving your projects to another physical system, you can export the projects to a removable media, using File > Export > File system. You do not have to include the bin folder, but include the .classpath and .project files.
Import your Integrated Runtime 1.1 projects to your Express Runtime 2.1 developer workspace using File > Import > Existing project into workspace. This makes the necessary updates to your wrappers, adding new XML tags and updating classpath information. The import wizard does not physically move or copy the imported files. If you prefer to have your imported project's files physically reside under the target workspace folder, ensure that the project to be imported is placed there prior to the import.
If you are migrating an application that was included with Integrated Runtime v1.1, copy the application's deployment package from the Integrated Runtime v1.1 installation directory to the Express Runtime v2.1 installation directory.

Locate the deployment package .jar file in the Integrated Runtime v1.1 installation directory (<INSTALLATION_DIRECTORY>/Runtime/SolutionEnabler/com/ibm/jsdt/webserver/tree). The deployment package filename contains the application ID and an abbreviation of the platform it is intended for (for example, "win" = Windows, "lnx" = Linux).
Copy the application's deployment package to the Express Runtime v2.1 installation directory (<INSTALLATION_DIRECTORY>/Runtime21/SolutionEnabler/com/ibm/jsdt/webserver/tree).
Rename the copy of the deployment package in the Express Runtime v2.1 installation directory, changing the ".en.jar" suffix to ".xx.jar."

Update wrapper files.

For each project you want to migrate, open the solution or application wrapper in the appropriate wrapper editor.
Review the new updates generated by the import to ensure the correct values have been used and to add information to the optional attributes. The new attributes as listed below in the schema changes section.
Optionally remove deprecated tags using the Source tab in the wrapper editor to edit the XML. The deprecated tags are listed in the Problems view in the developer. The wrapper does work in Express Runtime 2.1 if you leave the deprecated tags.

Generate your solution.

Schema changes from Version 1.1

Detailed information about the XML schema is located in the InfoCenter under Express Runtime 2.1 > Reference > XML schemas.

Application wrappers
New elements

installTime: This attribute is found on the General tab of the Application Editor, in the Basic Application Configuration section.
required: This attribute is found on the Variables tab in the Application editor for each variable.

Deprecated elements

builderVersion
debug
responseFileTemplate
installSize
fileSets
operatingSystems value "AIX", "SunOS", "HP-UX"
softwareImageRoot
includeAllFilesInSoftwareImageRoot
alwaysShowDeploymentParameters
deploymentPackagePrompt

Solution wrappers
New elements

welcomeScreenTitle: This attribute is found on the General tab of the Solution editor in the Basic Solution Configuration section.
welcomeScreenText: This attribute is found on the General tab of the Solution editor in the Basic Solution Configuration section.
welcomeScreenImage: This attribute is found on the General tab of the Solution editor in the Basic Solution Configuration section.
taskGroup element: Task groups are created on the Tasks tab of the Solution editor.

Deprecated elements

builderVersion
debug
language (as part of installTask element)

Known issues with component software

IBM HTTP Server port not set to 80

If the IBM HTTP Server is deployed to use a port other than 80, manual steps are required to configure WebSphere and the plug-in so that the HTTP Server can find the Web applications.

First update the Virtual Host port in WebSphere by using the WebSphere Administrative Console. In the WebSphere Administrative Console, perform the following steps:

Select Environment > Virtual Hosts.
Select default_host.
Select Host Aliases.
Select the host name using port 80.
Change the port setting to the port used by the HTTP Server.
Click Ok.
Click Save at the top of the WebSphere Administrative Console.
Click Save on the screen that follows to save the configuration change.

After the Virtual Host port is updated, the plug-in configuration file must be generated and propagated to the IBM HTTP Server system. If your system is not set up to automatically generate and propagate the plug-in configuration file, perform the following steps using the WebSphere Administrative Console:

Select Servers > Web servers.
Select the check box next to your Web server.
Click Generate Plug-in.
Select the check box next to your Web server again.
Click Propagate Plug-in.

Ports for WebSphere Application Server and IBM HTTP Server on OS/400 (i5/OS)

The deployment of the i5/OS Websphere Application Server Express 6.0 server configuration and the i5/OS HTTP server configuration tasks will prompt for port number along with the server name. In the case of WebSphere server configuration, this is the first port in a block of 15 that is used when configuring the application server. For example if a port of 7081 was specified, the WebSphere configuration would use ports 7081 to 7095. The first port is used by the application server and the second port is used to access the Administrative Console. In the case of the HTTP configuration, this is the port that the HTTP server listens to for a request.

Currently the tasks do not detect if these ports are already in use by other processes. If any of the ports in the WebSphere configuration port block are in use, the application server will not start. If the port specified in the HTTP configuration is in use, the HTTP server will attempt to start, but will fail and end abnormally. View the job logs of the server start-up jobs to determine the cause of the problem. To find the job log issue the following CL command "WRKJOB <ihs_server_name>", where <ihs_server_name> is the name of the IHS server that failed to start. For example "WRKJOB irhttp".

Period in directory name

Do not install IBM HTTP Server in a directory that contains a "." in the name.

Managing multiple IBM HTTP Server installations on one computer running Windows

If you install the IBM HTTP Server (IHS) on a system running Windows that already has IHS installed, only the last one installed is manageable by the Express Runtime console.

If you want to manage more than one installation of IBM HTTP Server on the same system, you can do so by defining a service for the additional copies of IBM HTTP Server. This can be accomplished by executing the following command in the directory where the IBM HTTP Server is installed:

\bin\apache -k install -n

The console then allows the designation of this IBM HTTP Server as a manageable Web server.

Redeployment of WebSphere Application Server - Express fails

After uninstalling WebSphere Application Server - Express, you must remove the AppServer directory from the target computer before attempting to redeploy WebSphere Application Server - Express.

Reinstallation of console module fails

When you uninstall a console module (for example, DB2 UDB Express) and reinstall it using the Express Runtime deployment wizard, it might fail; the log message indicates a return code from the Integrated Solution Console. These return codes, and their meanings, are summarized in the following tables. If you get a return code of 104, verify that you have the user ID and password specified correctly, and restart the task. For all other return codes, contact your IBM Support Center representative.

ISCDeploy (INSTALL)

Return code	Explanation
0	The Integrated Solutions Console component was deployed successfully (IscDeploy) or the prerequisite check was successful (IscPrereqChk).
1	A syntax error occurred.
2	The specified WAR file was not found. Specify the correct file path and filename.
3	The protocol or the context URL that you specified is not correct. Verify that the URL includes the correct protocol (http:// or https://). Specify deploy/deploy as the context URL.
4	The host name you specified is not valid or the Integrated Solutions Console server is not running. Verify that the URL includes the correct host name. Start the server before you issue the deploy command.
10	The correct parameters were not specified.
70	The process (deployment or prerequisite check) completed successfully.
71	The process (deployment or prerequisite check) did not complete successfully. This message usually indicates a problem with a portlet in the component WAR file. See your_isc_root\PortalServer\log\wps_date_time.log for messages that were logged before this return code was displayed. Use the time stamps in the file to locate those messages.
81	An error occurred while deploying the help files for the component. The attempt to copy the help files to the system has failed.
100	This component cannot be deployed, because it has been deployed already. If you want to deploy the component again, you can use IscReplace to update the component.
101	This component cannot be deployed, because it has a prerequisite component and the prerequisite has not been deployed. Deploy the prerequisite component and then deploy this component.
102	This component has a prerequisite component, but the wrong version of the prerequisite is deployed. Deploy the correct version of the prerequisite component and then deploy this component.
104	The Integrated Solutions Console administrator user ID, password, or both are not correct. Specify the correct values.
105	An internal error has occurred. A server-side file was not found. Be sure to specify the fully-qualified or relative file path and the WAR filename. Contact your service representative if the problem persists.
106	The component.xml file in the WAR file is not valid. Correct the file and repackage the WAR file.
108	An internal error has occurred. Contact your service representative.

ISCRemove (UNINSTALL)

Return code	Explanation
0	The Integrated Solutions Console component was deployed successfully (IscRemove) or the prerequisite check was successful (IscDependencyChk).
1	A syntax error occurred.
3	The protocol or the context URL that you specified is not correct. Verify that the URL includes the correct protocol (http:// or https://). Specify deploy/deploy as the context URL.
4	The host name you specified is not valid or the Integrated Solutions Console server is not running. Verify that the URL includes the correct host name. Start the server before you issue the remove command.
84	An error occurred while removing the help plug-ins for this component. No action is required.
200	The component cannot be removed, because it is not deployed. Specify the component UID for a component that is deployed.
201	This component cannot be removed, because it is a prerequisite component for one or more components. Remove the dependent components before you remove this component.

ISCReplace (REINSTALL)

Return code	Explanation
0	The Integrated Solutions Console component was replaced successfully.
1	A syntax error occurred.
2	The specified WAR file was not found. Specify the correct file path and filename.
3	The protocol or the context URL that you specified is not correct. Verify that the URL includes the correct protocol (http:// or https://). Specify deploy/deploy as the context URL.
4	The host name you specified is not valid or the Integrated Solutions Console server is not running. Verify that the URL includes the correct host name. Start the server before you issue the deploy command.
10	The correct parameters were not specified.
70	The replacement process completed successfully.
71	The replacement process did not complete successfully. This message usually indicates a problem with a portlet in the component WAR file. See the log file wps_date_time.log for messages that were logged before this return code was displayed. Use the time stamps in the file to locate those messages.
81	An error occurred while deploying the help files for the component. The attempt to copy the help files to the system has failed.
102	This component has a prerequisite component, but the wrong version of the prerequisite is deployed. Deploy the correct version of the prerequisite component and then deploy this component.
104	The Integrated Solutions Console administrator user ID, password, or both are not correct. Specify the correct values.
105	An internal error has occurred. A server-side file was not found. Be sure to specify the fully-qualified or relative file path and the WAR filename. Contact your service representative if the problem persists.
106	The component.xml file in the WAR file is not valid. Correct the file and repackage the WAR file.
108	An internal error has occurred. Contact your service representative.
200	The component cannot be replaced, because a component with the same component UID is not already deployed. Specify a WAR file for a component that is already deployed or use IscDeploy to deploy this component for the first time.

Exception to message about exceeding DB2 processors

If you are running IBM DB2 UDB Express with other components of Express Runtime, then up to four processors are permitted by the Express Runtime license. If you are entitled to IBM Express Runtime Plus and running IBM DB2 UDB Express on a machine with 3 or 4 processors, ignore warning messages that the number of processors is exceeded.

IBM DB2 UDB post-installation instructions

If you installed IBM DB2 UDB Version 8, you must perform some post-installation configuration steps. These steps are explained in the following sections.

Enabling the DB2 Remote Command Service
If you installed a partitioned DB2 server on Windows 2000, Windows Server 2003, or Windows XP, you must enable the DB2 Remote Command Service to protect your data and resources. To be fully secure, you need to enable either the computer, if the service is running under the context of the LocalSystem account, or a user for delegation, if the service is being run under the logon context of a user.

To enable the DB2 Remote Command Service, perform the following steps:

Open the Active Directory Users and Computers window, click Start and select Programs > Administrative tools > Active Directory Users and Computers.
In the right window panel, right-click the computer or user you want to enable and select Properties.
Click the General tab and select the Trust computer for delegation check box. For user setting, click the Account tab and check the Account is trusted for delegation check box in the Account option group. Ensure that the Account is sensitive and cannot be delegated box has not been checked.
Click OK to enable the computer or user for delegation.

Repeat these steps for each computer or user that needs to be enabled. You must restart your computer for the security change to take effect.

You can disable the DB2 Remote Command Service security features and return the environment to its previous state using the DB2RCMD_LEGACY_MODE registry variable.

To disable the DB2 Remote Command Service security features, enter the following command:

db2set DB2RCMD_LEGACY_MODE=ON

Note: This registry variable requires Boolean values as arguments. The values YES, 1, TRUE, and ON are all equivalent and the values NO, 0, FALSE, and OFF are also equivalent. You can specify any of the appropriate equivalent values.

Re-binding bind files
You need to bind your DB2 utilities against all your databases after the installation. This step is necessary for the fixes to become effective. The binding procedure, which follows, needs to be performed only once per database.

Re-binding to DB2 UDB databases
After applying fixes, execute the following commands:

db2 terminate db2 CONNECT TO <dbname> db2 BIND $DB2DIR\BND\@db2ubind.lst GRANT PUBLIC db2 BIND $DB2DIR\BND\@db2cli.lst GRANT PUBLIC db2 terminate

where <dbname> represents the name of a database to which the utilities should be bound and $DB2DIR represents the directory where you have installed DB2. db2ubind.lst and db2cli.lst contain lists of required bind files used by DB2 UDB Version 8.

Re-binding host databases
If you are connecting to host databases, you need to bind the new bind files to the host. Use the DB2 Command Line Processor to connect to the host database and bind the utilities as follows:

HOST COMMAND ===== =================================================================== MVS BIND $DB2DIR\BND\@ddcsmvs.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC VM BIND $DB2DIR\BND\@ddcsvm.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC VSE BIND $DB2DIR\BND\@ddcsvse.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC OS400 BIND $DB2DIR\BND\@ddcs400.lst BLOCKING ALL SQLERROR CONTINUE GRANT PUBLIC

Re-binding specific packages
If you want to bind only the specific .bnd files to the database, issue the following commands for each database.

db2 terminate db2 CONNECT TO <dbname> db2 BIND $DB2DIR\BND\<bind_file> BLOCKING ALL GRANT PUBLIC sqlerror continue db2 terminate

where <bind_file> represents the name of the bind file, and <dbname> represents the name of your database.

Bind db2schema.bnd to existing databases
For installations on the server, an additional bind file needs to be bound to existing databases. This requirement does not apply to clients.

To bind db2schema.bnd on the server, execute one of these commands sequences:

At a command prompt:

db2 terminate db2 CONNECT TO <dbname> db2 BIND $DB2DIR\BND\db2schema.bnd BLOCKING ALL GRANT PUBLIC sqlerror continue db2 terminate

or, at the DB2 command line:

TERMINATE CONNECT TO <dbname> BIND $DB2DIR\BND\db2schema.bnd BLOCKING ALL GRANT PUBLIC sqlerror continue TERMINATE

where <dbname> represents the name of a database to which the utilities should be bound and $DB2DIR represents the directory where you have installed DB2.

Rebinding after FixPak or patch installation
If you have existing spatial-enabled databases, you must rebind the list file db2gse.lst after you install a DB2 FixPak or patch. The db2gse.lst file contains the names of the bind files for the stored procedures that DB2 Spatial Extender provides.

To bind the db2gse.lst file, you must have one of the following authorities:

    *  sysadm or dbadm authority
    *  ALTERIN privilege on the schema
    *  BIND privilege on the package

To rebind the db2gse.lst file, perform the following steps:

Change to the instance directory where the bind files are located. Open a DB2 command window and enter the following command:
cd %DB2PATH%\bnd
Connect to the database and execute the BIND command. For example, enter:
db2 connect to dbname db2 bind /home/instance/sqllib/bnd/@db2gse.lst db2 terminate

You can use the DB2RBIND command with the ALL option instead of the BIND command. For syntax and options for the BIND and DB2RBIND commands, refer to the DB2 Command Reference.

Documentation issues

Supported Web browser required for documentation

A Web browser is required to view the documentation for this product. If no Web browser is available, the online documentation is not accessible.

Displaying console InfoCenter in simplified Chinese requires "zh-cn" language preference

If you are viewing the InfoCenter, set your browser language preference to "zh-cn" instead of "zh" to ensure the document displays in simplified Chinese. You set this by clicking Tools > Internet Options on the Internet Explorer menu and clicking Languages.

Some languages must use browsers configured to use the UTF-8 codepage

Browsers must be configured to use the UTF-8 codepage to view the program help files and InfoCenter in the following languages:

Simplified Chinese
Traditional Chinese
Japanese
Korean
Brazilian Portuguese

Supported platforms for Linux listed incorrectly

The following platforms are not supported in Express Runtime, Version 2.1:

Red Hat Desktop 3.0
SUSE LINUX Desktop 8.0
Novell Linux Desktop 9.0

SUSE LINUX Enterprise Server 8.0 is supported for deployment only.

Incorrect reference to HTTP plugin

Throughout the documentation, "WebSphere Express Plugin for IBM HTTP Server" should be the "IBM HTTP Plug-in for WebSphere Application Server."

Accessing the Javadoc for the support framework

The Javadoc for the support framework lists the function calls included in the Express Runtime wrappers. To read the Javadoc for the support framework, open Runtime21/SolutionEnabler/Support_Framework/index.html.

Description of supplied wrappers missing from InfoCenter

The files for the following extensions are not included in the InfoCenter:
    Sample application for Windows
    Sample application for Linux
    Sample application for OS/400 (i5/OS)
    Console management extension for IBM WebSphere Application Server - Express for Linux on IBM POWER

Sample application for Windows
Use this application wrapper to deploy the sample application to computers running Windows. You can also edit this wrapper using Express Runtime developer to create a wrapper for deploying your custom applications to computers running Windows. For more information on using the Express Runtime developer, see Using the Express Runtime developer in the InfoCenter. Depending on your selection and configuration, you might need to provide values for some or all of the following fields.

Application ID: IRU2_1SampleWin

Exposed variables
Field	Explanation	Default value	Validation requirements
Document Directory	Required. The directory where the application documents are installed.	C:\RuntimeDocs	Must start with drive letter, colon (:), then forward slash (\) Invalid characters: asterisk (*), question mark (?), quotation marks ("), pipe (\|), backslash (/), semicolon (;), tilde (~), brackets ([]), less than or greater than symbols (< >)
Database Name	Required. The name of the database used by this application.	DOCMGTD7	Must 1 to 8 characters in length. Must begin with an alphabetic character, at symbol (@), number sign (#), or dollar sign ($) Valid characters: A - Z, a - z, 0 - 9, dollar sign ($), number sign (#), at symbol (@). underscore (_)
DB2 Administrator User ID	Required. The administrator ID used to connect to DB2.	db2inst	Valid characters: A - Z, a - z, 0 - 9, dollar sign ($), number sign (#), at symbol (@), or underscore (_) Must be from 2 to 30 characters in length. Invalid prefix: IBM, SQL, SYS, underscore (_) Invalid values: ADMINS, GUESTS, USERS, PUBLIC, LOCAL, and SQL-reserved words
DB2 Administrator Password	Required. The password used with the DB2 Administrator User ID specified to connect to DB2.		Valid characters: A - Z, a - z, 0 - 9, dollar sign ($), number sign (#), at symbol (@), or underscore (_). Must be from 6 to 127 characters in length.

Sample application for Linux
Use this application wrapper to deploy the sample application to computers running Linux. You can also edit this wrapper using Express Runtime developer to create a wrapper for deploying your custom applications to computers running Linux. For more information on using the Express Runtime developer, see Using the Express Runtime developer in the InfoCenter. Depending on your selection and configuration, you might need to provide values for some or all of the following fields.

Application ID: IRU2_1SampleLnx

Exposed variables
Field	Explanation	Default value	Validation requirements
Document Directory	Required. The directory where the application documents are installed.	/opt/IBM/RuntimeDocs	Must start with backslash (/)
Database Name	Required. The name of the database to be created and used by this application.	DOCMGTD7	Must 1 to 8 characters in length. Must begin with an alphabetic character, at symbol (@), number sign (#), or dollar sign ($) Valid characters: A - Z, a - z, 0 - 9, dollar sign ($), number sign (#), at symbol (@). underscore (_)
DB2 instance owner user name	Required. The DB2 instance owner user ID used to connect to DB2.	db2inst	Valid characters: A - Z, a - z, 0 - 9, dollar sign ($), number sign (#), at symbol (@), or underscore (_) Must be from 2 to 30 characters in length. Invalid prefix: IBM, SQL, SYS, underscore (_) Invalid values: ADMINS, GUESTS, USERS, PUBLIC, LOCAL, and SQL-reserved words
DB2 instance owner password	Required. The password for the DB2 instance user ID.		Valid characters: A - Z, a - z, 0 - 9, dollar sign ($), number sign (#), at symbol (@), or underscore (_). Must be from 6 to 127 characters in length.

Sample application for OS/400 (i5/OS)
Use this application wrapper to deploy the sample application to computers running OS/400 (i5/OS). You can also edit this wrapper using Express Runtime developer to create a wrapper for deploying your custom applications to computers running OS/400 (i5/OS). For more information on using the Express Runtime developer, see Using the Express Runtime developer in the InfoCenter. Depending on your selection and configuration, you might need to provide values for some or all of the following fields.

Application ID: IRU2_1SampleI5OS

Exposed variables
Field	Explanation	Default value	Validation requirements
Document Directory	Required. The directory where the application documents are installed.	/opt/IBM/RuntimeDoc	Must start with a forward slash (/) Valid characters: A - Z, a - z, 0 - 9, hyphen (-), underscore (_), period (.)
Database Name	The name of the database that is created and used by this application. If the database already exists, it is to be dropped.
DB2 Administrator User ID	Required. The administrator user ID used to connect to DB2.	db2inst	Must begin with an alphabetic character. Valid characters: A - Z, a - z, 0 - 9, dollar sign ($), pound sign (#), or at symbol (@). Must be from 2 to 10 characters in length. Invalid prefix: IBM, SQL, SYS, numeric characters, underscore (_) Invalid values: ADMINS, GUESTS, USERS, PUBLIC, LOCAL, and SQL-reserved words
DB2 Administrator Password	Conditional. The password used with the administrator user ID specified to connect to DB2.		Valid characters: A - Z, a - z, 0 - 9, dollar sign ($), pound sign (#), at symbol (@), or underscore (_). Must be from 2 to 10 characters in length.
HTTP Server Name	Specify the name of the IBM HTTP Server.		Must start with an alphabetic character. Must be from 1 to 10 characters in length.
Application server name	Specify a unique name for the application server.

Console management extension for IBM WebSphere Application Server - Express for Linux on IBM POWER
Use this wrapper to install the console's management extension for IBM WebSphere(R) Application Server - Express on a target computer running Linux(TM)on IBM POWER(TM). Depending on your selection and configuration, you might need to provide values for some or all of the following fields.

Application ID: IRU2_1WASExpressMgmtExt6_0LnxOnPwr

Exposed variables
Field	Explanation	Default value	Validation requirements
WebSphere Management Extension Installation Location	Required. The fully qualified path name to the directory where you want to install the WebSphere Application Server - Express management extension. If the management extension is already installed, that directory will be used.	c:\Program Files\IBM	Must not contain /
Target WebSphere Location	Required. The fully qualified path name to the directory of the WebSphere Application Server to be administered.	c:\Program Files\IBM\WebSphere\AppServer	Must not contain /
WebSphere Username	Optional. The user name required for administering the WebSphere Application Server.		Must be 1 - 20 characters Must not contain / * + , : ; ? \| < = > [\]
WebSphere Password	Optional. The password required for administering the WebSphere Application Server		Must be no more than 14 characters Can contain only lowercase characters a-z, numbers 0 to 9 @ # $ and _
Console Agent Port	Required. The communication port to be used by Console Agent. If Console Agent is already installed, this value is ignored.	7044	Port number 1 - 65535
Enable Reinstall	Specify whether to enable reinstallation if the management extension is already installed on the target computer.	false	Boolean
Console Agent Runlevels	Required. The run level that Console Agent will run under.		A string containing integers 1 - 5 and commas.

IBM Express Runtime information Web site

For more information about IBM Express Runtime products, see http://www.ibm.com/partnerworld/isv/go/expressruntime.

Messages

The following messages are new or have been modified since the release of the Express Runtime 2.1 InfoCenter.

IRU00129: The user {0} must possess the special authorities ALLOBJ, SAVSYS, JOBCTL, SERVICE, SPLCTL, SECADM, AUDIT, IOSYSCFG to perform this task.

Explanation: The user attempted a task for which he does not have sufficient authority.
User Response: Update the user profile to include the special authorities noted in the message.

IRU03026: The target computer cannot find the deployment package {0}.

Explanation: The deployment wizard cannot find the specified file or there is not enough space on the target computer for the installation JAR file. This file is necessary for the software installation.
User Response: Free up some disk space on the target computer. Restart the deployment wizard on the staging server and IBM Installation Agent on the target computer, and then start the installation again. If the problem persists, print the log file and contact your solution provider.

IRU10950: The uninstallation of the {0} plug-in failed. Run {1} to uninstall the plug-in.

Explanation: The uninstallation of an Express Runtime console plug-in failed. Failure might be caused by any number of problems, including network problems, a corrupted installation registry, an incorrect user ID or password, or other reasons.
User Response: Manually run the uninstallation program that is listed in the message.

IBM Express Runtime Version 2.1 README

Table of Contents

Schema changes from Version 1.1