See examples that use the mqsireportproperties command to display properties that are associated with policies.
Always enter the command on a single line. In some examples, a line break has been added to enhance readability.
The following examples include the -c parameter to specify the type of policy to view and, where needed, the -o parameter to specify the name of the policy.
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 mqsireportproperties 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.
mqsireportproperties INODE -c Aggregation -o AllReportableEntityNames -r
mqsireportproperties INODE -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 INODE -c FtpServer -o TEST1 -r
The
result of this command has the following
format:FtpServer
TEST1
cipher='blowfish-cbc'
accountInfo=''
compression='9'
connectionType='PASSIVE'
remoteDirectory='.'
scanDelay='30'
serverName='winlnx58'
transferMode='BINARY'
securityIdentity='chbatey'
knownHostsFile=''
mac=''
preserveRemoteFileDate='FALSE'
protocol='SFTP'
strictHostKeyChecking='FALSE'
timeoutSec='0'
mqsireportproperties INODE -c FtpServer -o TEST1 -n protocol
mqsireportproperties INODE -c JDBCProviders -o DB2EXTRA -r
The
result of this command has the following
format:JDBCProviders
DB2EXTRA
connectionUrlFormat='jdbc:db2://[serverName]:[portNumber]/[databaseName]:use
r=[user];password=[password];'
connectionUrlFormatAttr1=''
connectionUrlFormatAttr2=''
connectionUrlFormatAttr3=''
connectionUrlFormatAttr4=''
connectionUrlFormatAttr5=''
databaseName=''
databaseSchemaNames='useProvidedSchemaNames'
environmentParms=''
jarsURL='default_Path'
jdbcProviderXASupport='TRUE'
maxConnectionPoolSize='0'
portNumber='0'
securityIdentity='default_User@default_Server'
serverName=''
type4DatasourceClassName=''
type4DriverClassName=''
useDeployedJars='FALSE'
mqsireportproperties INODE -c JMSProviders
-o AllReportableEntityNames -r
mqsireportproperties INODE -c JMSProviders
-o WebSphere_MQ -r
mqsireportproperties INODE -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 INODE -c PolicySets
-o Policy_2 -n ws-security -p policyset.xml
You
can use the output file to move policy sets between integration nodes, and for backup.mqsireportproperties INODE -c PolicySetBindings
-o Bindings_2 -n ws-security -p bindings.xml
This
command writes the Policy Set Bindings file Bindings_2 in integration node INODE to file bindings.xml. You can
use this file to move policy set bindings between integration nodes, and for backup.mqsireportproperties INODE -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 INODE -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'