IBM App Connect Enterprise, Version 11.0.0.2 Operating Systems: Windows, Linux


mqsicreateconfigurableservice command (deprecated)

Use the mqsicreateconfigurableservice command to migrate configurable services to policies.

Supported platforms

  • Windows.
  • Linux and UNIX systems.

Purpose

You can use this command to create a policy in App Connect Enterprise that is equivalent to a configurable service in your IBM® Integration Bus.

The mqsicreateconfigurableservice command is deprecated in App Connect Enterprise and is provided as a migration aid, so that any use of the command in your IBM Integration Bus scripts continues to work App Connect Enterprise (to create a policy).

Usage notes

  • Before you run this command, ensure that the integration node is running.
  • Not all configurable services have an equivalent policy in App Connect Enterprise.

    For more information about supplied policies, and their properties and values, see Policy properties. The policy properties information gives the names of policies and properties as displayed in the IBM App Connect Enterprise Toolkit. Those display names are expanded forms of the short names used in the mqsicreateconfigurableservice command; for example: an FTP Server policy (FtpServer) has the policy shortname FtpServer and has the property Connection type with the shortname connectionType. The shortnames and values for use with commands are defined by the schema ace_install\common\schemas\Policy\Policy.xsd, with display names and UI help defined by the schema in ace_install\common\schemas\Policy\PolicyUI.xsd.

Syntax

Some parameters have alternative long names; for example: -p and --admin-port are alternative parameter names of the port number for the administration REST API. The long names available are listed in the Parameters section.

Read syntax diagramSkip visual syntax diagram
>>-mqsicreateconfigurableservice--integrationNodeName----------->

>-- -c --policy-type-- -o--policy-name-------------------------->

>--+---------------------------------------------------+-------><
   |      .-,------------.                             |   
   |      V              |                             |   
   '- -n----PropertyName-+--+------------------------+-'   
                            |      .-,-------------. |     
                            |      V               | |     
                            '- -v----PropertyValue-+-'     

Parameters

integrationNodeName
(Required) The name of the integration node to modify. This parameter must be the first parameter.
-c policy-type | configurable-service policy-type
(Required) The type of policy to be created (the policy-type of the configurable service); for example: -c ActivityLog to migrate to an Activity Log policy.

Use the mqsireportproperties command to view the list of valid values.

The valid policy types are listed under Policy properties.

-o policy-name | -object policy-name
(Required) The name of the policy whose properties you want to change.

The policy name can include alphanumeric characters and the underscore character. The name cannot include spaces and must start with a letter.

-n PropertyName | -property PropertyName
(Optional) The name of the property that is being changed. The property name must be a valid XML attribute name; for example, a property name cannot start with a number.
-v PropertyValue | -value PropertyValue
(Optional, but required if the -n parameter is specified) The value that is assigned to the property that is specified by the -n parameter. You can specify more than one property name and corresponding value by using commas as separators; for example, -n Name1,Name2 -v Value1,Value2.

If the property value contains a comma, enclose the value with escaped double quotation marks (\" and \"); for example, -n Name1,Name2 -v Value1,\"Value21,Value22\".

UNIX platformOn UNIX systems, if the -v parameter contains a semi-colon (;), enclose the entire string in quotation marks, as shown in the following example:
mqsicreateconfigurableservice INODE -c JDBCProviders -o DB2EXTRA -n connectionUrlFormat 
-v "jdbc:db2://[serverName]:[portNumber]/[databaseName]:user=[user];password=[password];"

Authorization

For information about platform-specific authorizations, see the following topics: If you have enabled integration node administration security, you must also set up the authority that is detailed in Tasks and authorizations for administration security.

Responses

This command returns the following responses:
  • BIP8011 Unable to create configuration data
  • BIP8012 Unable to connect to system components
  • BIP8014 Component cannot be created
  • BIP8073 Invalid integration node name
  • BIP8983 Configurable service already exists
  • BIP8984 Configurable service was not found
  • BIP1042 Tells the user that the command is deprecated and that they should use policy sets instead
  • BIP8976 Configurable service is not a supported policy

Examples

Create a policy for a migrated Aggregation configurable service that uses a set of queues that is prefixed with SYSTEM.BROKER.AGGR.SET1, and with a timeout of 60 seconds:
mqsicreateconfigurableservice INODE -c Aggregation -o myAggregationService 
-n queuePrefix,timeoutSeconds -v SET1,60 
Create a policy for a migrated CICSConnection configurable service for the CICS® instance that is running at tcp://test.cics.ibm.com port 12345. The integration node is identified by APPLID BRKApp and qualifier BRKQual. The connection timeout is 10 seconds and the request timeout is 5 seconds in this example:
mqsicreateconfigurableservice INODE -c CICSConnection -o myCICSConnectionService
-n cicsServer,clientApplid,clientQualifier,connectionTimeoutSecs,
requestTimeoutSecs -v tcp://test.cics.ibm.com:12345,BRKApp,BRKQual,10,5
Create a policy for a migrated Collector configurable service that uses queues that are prefixed with SYSTEM.BROKER.EDA.SET1, and with a collection expiry of 60 seconds:
mqsicreateconfigurableservice INODE -c Collector -o myCollectorService 
-n queuePrefix,collectionExpirySeconds -v SET1,60 

an37200_.htm | Last updated 2018-11-02 14:46:00