Use the mqsireportproperties command to display properties that relate to a broker, an integration server, or a configurable service.
You can also use the IBM® Integration Explorer to create and view configurable services. See Using the IBM Integration Explorer to work with configurable services for more information.
Use the mqsireportproperties command to examine the values of properties or broker resources that are set by using the mqsichangeproperties command, or created by using the mqsicreateconfigurableservice command.
>>-mqsireportproperties--BrokerName-----------------------------> >--+------------------------------+-- -o --ObjectName-----------> +- -b --ComponentName----------+ +- -e --IntegrationServerLabel-+ '- -c --ConfigurableService----' >--+- -n --PropertyName-+--+----------------+--+-----+--------->< +- -a----------------+ '- -p --FileName-' '- -f-' '- -r----------------'
For a list of supplied configurable services, and their properties and values, see Configurable services properties.
You must also specify -b, -e, or -c after -o, except if you specify the object name BrokerRegistry.
You can set a parameter to disable or enable the broker-wide listener for HTTP and SOAP nodes; by default, this listener is active and is used for HTTP nodes. SOAP nodes use the integration server (embedded) listener by default.
You can configure the integration server such that all HTTP nodes use the embedded listener instead of the broker-wide listener. You can also configure the integration server so that SOAP nodes use the broker-wide listener. For more information, see HTTP listeners.
Specify a value of AllReportableEntityNames to return a list of all valid object names.
You must select only one option from -n, -a, and -r.
Note, that this option does not show all the possible values for AllReportableEntityNames. Furthermore, not all entities support this parameter.
You can use this parameter only when the integration server is in the stopped state, and you must also specify -e and -o.
If you specify this parameter for other configurable services or components, an error is generated.
For more information about objects, properties, and values, and valid combinations of these parameters, see mqsichangeproperties command.
For the httplistener component, the mqsireportproperties command does not report those properties that have not been explicitly set with the mqsichangeproperties command, even if those properties have a default setting.
For example, the default HTTPSConnector port that is used (unless it has been changed) is 7083. However, this value is not reported by the mqsireportproperties command unless you have changed it from this default by using the mqsichangeproperties command. To see the default values for all properties that the mqsireportproperties command can report, see the mqsichangeproperties command description.
Always enter the command on a single line; in some examples, a line break has been added to enhance readability.
Displaying properties associated with broker components
The following examples include the -b parameter to specify the component to view.
mqsireportproperties IB9NODE -b httplistener -o HTTPListener -n startListener
mqsireportproperties IB9NODE -b cachemanager -o CacheManager -r
mqsireportproperties IB9NODE -b httplistener -o HTTPListener -a
mqsireportproperties IB9NODE -b httplistener -o HTTPSConnector -n port
mqsireportproperties IB9NODE -b webadmin -o HTTPSConnector -r
Displaying properties associated with configurable services
The following examples include the -c parameter to specify the configurable service to view. For a list of supplied configurable services, and their properties and values, see Configurable services properties.
mqsireportproperties IB9NODE -c Aggregation -o AllReportableEntityNames -r
mqsireportproperties IB9NODE -c CDServer -o AllReportableEntityNames -r
The
result of this command has the following format:CDServer
Default
hostname='localhost'
port='1363'
brokerPathToStagingDir=''
cdPathToStagingDir=''
brokerPathToInputDir=''
cdPathToInputDir=''
queuePrefix= ''
securityIdentity=”Default”
mqsireportproperties IB9NODE -c FtpServer -o TEST1 -r
mqsireportproperties IB9NODE -c FtpServer -o TEST1 -n protocol
mqsireportproperties IB9NODE -c JDBCProviders -o Oracle -r
mqsireportproperties IB9NODE -c JMSProviders
-o AllReportableEntityNames -r
mqsireportproperties IB9NODE -c JMSProviders
-o WebSphere_MQ -r
mqsireportproperties IB9NODE -c JMSProviders
-o BEA_WebLogic –r
The result of this command has the following format:ReportableEntityName=''
JMSProviders
BEA_Weblogic=''
jarsURL='default_Path'
nativeLibs='default_Path'
proprietaryAPIAttr1='weblogic.jndi.WLInitialContextFactory'
proprietaryAPIAttr2='t3://9.20.94.16:7001'
proprietaryAPIAttr3='BEAServerName'
proprietaryAPIAttr4='default_none'
proprietaryAPIAttr5='default_none'proprietaryAPIHandler='BEAWebLogicAPIHandler.jar'
mqsireportproperties IB9NODE -c PolicySets
-o Policy_2 -n ws-security -p policyset.xml
You can
use the output file to move policy sets between brokers, and for backup.mqsireportproperties IB9NODE -c PolicySetBindings
-o Bindings_2 -n ws-security -p bindings.xml
This
command writes the Policy Set Bindings file Bindings_2 in broker IB9NODE to file bindings.xml.
You can use this file to move policy set bindings between brokers,
and for backup.mqsireportproperties IB9NODE -c SecurityProfiles
-o AllReportableEntityNames -r
The result of this
command has the following format:ReportableEntityName=''
SecurityProfiles
Default_Propagation=''
authentication = 'NONE'
authenticationConfig = ''
authorization = 'NONE'
authorizationConfig = ''
idToPropagateToTransport = 'Message ID'
keyStore = 'Reserved for future use'
mapping = 'NONE'
mappingConfig = ''
passwordValue = 'PLAIN'
propagation = 'TRUE'
rejectBlankpassword = 'FALSE'
transportPropagationConfig = ''
trustStore = 'Reserved for future use'
mqsireportproperties IB9NODE -c SecurityProfiles
-o MyFirstSecurityProfile -r
The result of this command
has the following format:ReportableEntityName=''
SecurityProfiles
MyFirstSecurityProfile=''
authentication = 'LDAP'
authenticationConfig = 'ldap://localhost:389/ou=users,o=ibm'
authorization = 'NONE'
authorizationConfig = ''
idToPropagateToTransport = 'Message ID'
keyStore = 'Reserved for future use'
mapping = 'TFIM'
mappingConfig = 'http://tfimhost1:80'
passwordValue = 'PLAIN'
propagation = 'TRUE'
rejectBlankpassword = 'FALSE'
transportPropagationConfig = ''
trustStore = 'Reserved for future use'