IBM InfoSphere Streams Version 4.1.1

streamtool mkresourcepkg

The streamtool mkresourcepkg command generates a resource installation package that you can use to add externally managed resources.

If you are using the default InfoSphere® Streams resource manager, use the streamtool mkhostpkg command instead. It generates a domain host installation package that you can use to add InfoSphere Streams resources to the domain.

Usage


mkresourcepkg

>>-+-----------------+--+-------------+------------------------->
   '- --group--group-'  '-+- -h-----+-'   
                          '- --help-'     

>--+--------------------------+--+------------+----------------->
   '- --install-dir--pathname-'  '- --minimal-'   

>--+-----------------+--+----------------------+---------------->
   '- --owner--owner-'  '- --pkg-dir--pathname-'   

>--+-----------------+--+-----------------------+--------------->
   '- --trace--level-'  '-+- -v--------+--level-'   
                          '- --verbose-'            

>--+-----------------------------+-----------------------------><
   |               .-,---------. |   
   |               V           | |   
   '- --zkconnect----host:port-+-'

Authority

You do not need any authority to run this command.

Description

To generate a resource installation package that contains a smaller subset of InfoSphere Streams files, use the --minimal parameter.

Restriction: If you plan to use IBM® Platform Symphony® to manage the resource, do not use the --minimal parameter. It omits components that are required by that external resource manager.

The resource installation package is generated in the current directory or the directory that you specify in the --pkg-dir parameter. You must copy this package to all of the externally managed resources that you want to add.

The method for deploying the resource installation package depends on the external resource manager that you use. For example, if you use IBM Platform Symphony, you can use the Platform Symphony rsdeploy command to deploy and install the package. Otherwise, you can deploy and extract the contents of the package manually. For example, after you copy the package to an externally managed resource, enter tar -xvf resource-installation-package-name.tar.

The resource installation package contains the following files:

deployment.xml: This file is used by Platform Symphony only. It helps to simplify the installation process when you use the Platform Symphony rsdeploy command.
Installation script files:
- streamsresourceinstall.sh: This script file is used to install the InfoSphere Streams product on the externally managed resources with the same options that you specified on the streamtool mkresourcepkg command.
- streamsresourcesetup.sh: This script file is used to install the InfoSphere Streams product on the externally managed resources if you want to change any options that you specified on the streamtool mkresourcepkg command.
streamsresourceuninstall.sh: This script file is used to uninstall the InfoSphere Streams product on the externally managed resources.

If you specify a path where the product is already installed and you are not installing a new version, fix pack, or interim fix, the installation script stops. It does not reinstall the product.

Options and arguments

--group group

Specifies the group identifier that owns the files that are installed by the InfoSphere Streams product. If you do not specify this option, the command uses the installation owner's group.

-h, --help

Specifies to show the command syntax.

--install-dir pathname

Specifies the path where you want to install the product. The default location is /opt/ibm/InfoSphere_Streams. The path does not need to exist before you run the streamsdomainhostsetup.sh script.

--minimal

Specifies to create a minimal installation package, which does not contain optional components such as the Streams Console.

--owner owner

Specifies the user ID that owns the files that are installed by the InfoSphere Streams product. If you do not specify this option, the command uses the installation owner's user ID.

--pkg-dir pathname

Specifies the path where you want to store the installation package. The default location is the current directory.

--trace level

Specifies the trace setting. The following valid levels are listed in order of increasing verbosity, which is to say that the first level in the list generates the least amount of information:
off

error

warn

info

debug

trace

The default value is off.

-v,--verbose level

Specifies to provide more detailed command output. The vebosity level can be from 0 to 3 where each increment provides more detailed output.

--zkconnect host:port

This option is deprecated and has no effect.

Examples

The following example generates a resource installation package in the current directory:

[streamtool <bsmith@StreamsDomain.StreamsInstance>] mkresourcepkg
CDISA0070I Creating the following installation package:
/home/bsmith/StreamsResourceInstall-4.1.0.0-x86_64-el7.tar.
CDISA0069I The following installation package was successfully created: 
/home/bsmith/StreamsResourceInstall-4.1.0.0-x86_64-el7.tar.