command
command
Last unsuccessful login: Fri Oct 1 12:43:23 2021 on ssh from 10.33.146.41
Last login: Tue Jul 12 13:31:55 2022 on ssh from 10.1.13.153
*******************************************************************************
* *
* *
* Welcome to AIX Version 7.1! *
* *
* *
* Please see the README file in /usr/lpp/bos for information pertinent to *
* this release of the AIX Operating System. *
* *
* *
*******************************************************************************
.profile[5]: profile.sh:.:/opt/IBM/EAsmbl_image/iib-10.0.0.6/server/lib:: not
found
MQSI 10.0.0.6
/opt/IBM/EAsmbl_image/iib-10.0.0.6/server
This integration node is stopped; the command you issued cannot be processed when
an integration node is stopped.
A previous command has been issued to stop this integration node, or this
integration node has never been started.
Syntax:
mqsistopmsgflow integrationNodeSpec (-g | -e integrationServerName) [[(-k
applicationName | -z)] [-y staticLibraryName] (-m flowName | -j)] [-w timeoutSecs]
[-v traceFileName] [-f forceMode]
Command options:
'integrationNodeSpec' is one of:
(a) 'integrationNodeName' : Name of a locally defined integration node
(b) '-n integrationNodeFileName' : File containing remote integration node
connection parameters (*.broker)
(c) '[integrationNodeName] -i ipAddress -p port' : hostname and port of a remote
integration node. 'integrationNodeName' optional for validation.
(d) '[integrationNodeName] -i uri' : URI for the remote integration node in the
form tcp://[<user>[:<password>]@]<host>:<port>
If a user name and password are supplied, any URI
Reserved characters in the password must be percent-encoded.
'-g' all integration servers.
'-e integrationServerName' name of the integration server on which to stop message
flows. If this is not specified, all integration servers on the integration node
are stopped.
'-z' stops all applications on the specified integration node or integration
server
'-k applicationName' the name of the application to stop or the name of the
application that contains the message flow.
'-y staticLibraryName' the name of the static library that contains the message
flow.
'-m flowName' the name of the message flow to stop
'-j' stops all message flows on the specified integration node or integration
server but leaves integration server processes running
'-w timeoutSecs' maximum number of seconds to wait for message flows to stop
(default is 60)
'-v traceFileName' send verbose internal trace to the specified file
'-f forceMode' causes the stop to be enforced using the forceMode parameter. A
value of 'normal' causes the stop without forcing any threads to stop and a value
of 'restartExecutionGroup' stops the flow by restarting the integration server
process.
Note: If -e or -g is specified without -m or -j then the stop will only apply to
integration servers. The current run state of the message flow will be saved ready
for restart.
Note: When an integration server is in stopped state it is not possible to start
or stop the message flows within it. An integration server needs to be in running
state to process the start or stop message flow request, and so the only command a
stopped integration server will accept is the request to start the integration
server itself.
$ mqsistopmsgflow CBEBIRRMOTI -e CBEBIRRMOTIT -k CBEBIRR-MOTI-Payment
BIP1193I: Stopping application 'CBEBIRR-MOTI-Payment' on integration server
'CBEBIRRMOTIT'...
BIP1195I: Application 'CBEBIRR-MOTI-Payment' on integration server 'CBEBIRRMOTIT'
is reported as stopped.
BIP8071I: Successful command completion.
$ mqsilist CBEBIRRMOTI -e CBEBIRRMOTIT
BIP1276I: Application 'CBEBIRR-MOTI-Payment' on integration server 'CBEBIRRMOTIT'
is stopped.
BIP1275I: Application 'MB_TeleBirr' on integration server 'CBEBIRRMOTIT' is
running.
BIP1275I: Application 'W2B_KYC' on integration server 'CBEBIRRMOTIT' is running.
BIP1877I: REST API 'int' on integration server 'CBEBIRRMOTIT' is running.
BIP8071I: Successful command completion.
$ mqsistartmsgflow CBEBIRRMOTI -e CBEBIRRMOTIT -k CBEBIRR-MOTI-Payment
BIP1192I: Starting application 'CBEBIRR-MOTI-Payment' on integration server
'CBEBIRRMOTIT'...
BIP1194I: Application 'CBEBIRR-MOTI-Payment' on integration server 'CBEBIRRMOTIT'
is reported as started.
BIP8071I: Successful command completion.
$ mqsilist CBEBIRRMOTI -e CBEBIRRMOTIT
BIP1275I: Application 'CBEBIRR-MOTI-Payment' on integration server 'CBEBIRRMOTIT'
is running.
BIP1276I: Application 'MB_TeleBirr' on integration server 'CBEBIRRMOTIT' is
stopped.
BIP1275I: Application 'W2B_KYC' on integration server 'CBEBIRRMOTIT' is running.
BIP1877I: REST API 'int' on integration server 'CBEBIRRMOTIT' is running.
BIP8071I: Successful command completion.
$ mqsistartmsgflow CBEBIRRMOTI -e CBEBIRRMOTIT -k MB_TeleBirr
BIP1192I: Starting application 'MB_TeleBirr' on integration server
'CBEBIRRMOTIT'...
BIP1194I: Application 'MB_TeleBirr' on integration server 'CBEBIRRMOTIT' is
reported as started.
BIP8071I: Successful command completion.
$ mqsireportproperties CBEBIRRMOTI -e CBEBIRRMOTIT -o httpconnector -r
BIP2087E: Integration node 'CBEBIRRMOTI' was unable to process the internal
configuration message.
The entire internal configuration message failed to be processed successfully.
Use the messages following this message to determine the reasons for the failure.
If the problem cannot be resolved after reviewing these messages, contact your IBM
Support center. Enabling service trace may help determine the cause of the failure.
BIP4041E: Integration server 'CBEBIRRMOTIT' received an administration request that
encountered an exception.
While attempting to process an administration request, an exception was
encountered. No updates have been made to the configuration of the integration
server.
Review related error messages to determine why the administration request failed.
BIP2212E: Invalid configuration message containing action 'Report' which is not
valid for target object 'httpconnector'.
The integration node received a configuration message containing the action
'Report' which is not valid for the target object 'httpconnector'. This can be
caused by a mismatch in levels between the Integration Toolkit and the integration
node, or as a result of a user or third party written user-defined node where the
implementation library installed at the integration node does not match the node
definition held at the Integration Toolkit.
Ensure that the levels of code installed at the Integration Toolkit and integration
node are all consistent. If they are, identify the supplier of the target object
and report the problem to them. If this is IBM, contact your IBM support center.
Command Options:
'integrationNodeName' The name of the integration node.
'-b httplistener' Report properties for the HTTP Listener component.
'-b securitycache' Report properties for the Security Cache component.
'-b servicefederation' Report properties for the Service Federation Management
component.
'-b webadmin' Report properties for the Web Administration component.
'-b cachemanager' Report properties for the Cache Manager component.
'-b pubsub' Report properties for the Publish/Subscribe component.
'-e integrationServerName' The name of the integration server.
'-c ConfigurableService' The type of the configurable service, for example,
JMSProviders. Specify a value of "AllTypes" to list all configurable service types.
'-o ObjectName' The name of the object to report on. Specify a value of
"AllReportableEntityNames" to list all valid object names.
'-n AttributeName' Display the value of the named attribute.
'-a' Display all attribute values (non-recursive).
'-r' Display all attribute values (recursive).
'-p Path/Filename' The name of a file to write the integration node property
settings to. If -n is specified, the attribute name is omitted from the output;
only the value of the attribute is written to the file.
'-f' Allow the command to run when the integration server is stopped. This option
can be used only along with the -e option.
BIP8006E: Flag missing. One of the flags in list (n,a,r) must be specified.
When using this command interface the user should select all required flags.
Correct and reissue the command.
$ mqsireportproperties CBEBIRRMOTI -e CBEBIRRMOTIT -o HTTPConnector -r
HTTPConnector
uuid='HTTPConnector'
userTraceLevel='none'
traceLevel='none'
userTraceFilter='none'
traceFilter='none'
port='7802'
address=''
maxPostSize=''
acceptCount=''
compressableMimeTypes=''
compression=''
connectionLinger=''
connectionTimeout=''
maxHttpHeaderSize=''
maxKeepAliveRequests='0'
maxThreads=''
minSpareThreads=''
noCompressionUserAgents=''
restrictedUserAgents=''
socketBuffer=''
tcpNoDelay='true'
explicitlySetPortNumber='7802'
enableLookups=''
enableMQListener=''
shutdownDelay=''
allowCrossConnectorPolling=''
autoRespondHTTPHEADRequests=''
integratedWindowsAuthentication=''
iwaTimeoutSeconds='300'
serverName=''
corsEnabled='false'
corsAllowOrigins='*'
corsAllowCredentials='false'
corsExposeHeaders='Content-Type'
corsMaxAge='-1'
corsAllowMethods='GET,HEAD,POST,PUT,PATCH,DELETE,OPTIONS'
corsAllowHeaders='Accept,Accept-Language,Content-Language,Content-Type'
Connector
port='7802'
type='Embedded'
URLRegistration
url='/int/v1*'
outstandingRequests='0'
UsedBySOAPNNodes='FALSE'
UsedByHTTPNNodes='TRUE'
nodeLabel='HTTP Input'
flowLabel='gen.int'
URLRegistration
url='/KYCWtoB/Service.asmx'
outstandingRequests='0'
UsedBySOAPNNodes='TRUE'
UsedByHTTPNNodes='FALSE'
nodeLabel='SOAP Input'
flowLabel='W2B_KYC_msg'
URLRegistration
url='/CBEBIRR_MOTI/validationRequest'
outstandingRequests='0'
UsedBySOAPNNodes='TRUE'
UsedByHTTPNNodes='FALSE'
nodeLabel='Validation SOAP Input'
flowLabel='CBEBIRR_MOTI_Payment'
URLRegistration
url='/CBEBIRR_MOTI/confirmationRequest'
outstandingRequests='0'
UsedBySOAPNNodes='TRUE'
UsedByHTTPNNodes='FALSE'
nodeLabel='Confirmation SOAP Input'
flowLabel='CBEBIRR_MOTI_Payment'
URLRegistration
url='/CBEBIRR_MOTI/queryRequest'
outstandingRequests='0'
UsedBySOAPNNodes='TRUE'
UsedByHTTPNNodes='FALSE'
nodeLabel='Query SOAP Input'
flowLabel='CBEBIRR_MOTI_Payment'
URLRegistration
url='/MBTelebirr/request'
outstandingRequests='0'
UsedBySOAPNNodes='TRUE'
UsedByHTTPNNodes='FALSE'
nodeLabel='SOAP Input'
flowLabel='MB_TeleBirr'
URLRegistration
url='/MBTelebirr/result'
outstandingRequests='0'
UsedBySOAPNNodes='TRUE'
UsedByHTTPNNodes='FALSE'
nodeLabel='SOAP Input1'
flowLabel='MB_TeleBirr'
Syntax:
mqsistopmsgflow integrationNodeSpec (-g | -e integrationServerName) [[(-k
applicationName | -z)] [-y staticLibraryName] (-m flowName | -j)] [-w timeoutSecs]
[-v traceFileName] [-f forceMode]
Command options:
'integrationNodeSpec' is one of:
(a) 'integrationNodeName' : Name of a locally defined integration node
(b) '-n integrationNodeFileName' : File containing remote integration node
connection parameters (*.broker)
(c) '[integrationNodeName] -i ipAddress -p port' : hostname and port of a remote
integration node. 'integrationNodeName' optional for validation.
(d) '[integrationNodeName] -i uri' : URI for the remote integration node in the
form tcp://[<user>[:<password>]@]<host>:<port>
If a user name and password are supplied, any URI
Reserved characters in the password must be percent-encoded.
'-g' all integration servers.
'-e integrationServerName' name of the integration server on which to stop message
flows. If this is not specified, all integration servers on the integration node
are stopped.
'-z' stops all applications on the specified integration node or integration
server
'-k applicationName' the name of the application to stop or the name of the
application that contains the message flow.
'-y staticLibraryName' the name of the static library that contains the message
flow.
'-m flowName' the name of the message flow to stop
'-j' stops all message flows on the specified integration node or integration
server but leaves integration server processes running
'-w timeoutSecs' maximum number of seconds to wait for message flows to stop
(default is 60)
'-v traceFileName' send verbose internal trace to the specified file
'-f forceMode' causes the stop to be enforced using the forceMode parameter. A
value of 'normal' causes the stop without forcing any threads to stop and a value
of 'restartExecutionGroup' stops the flow by restarting the integration server
process.
Note: If -e or -g is specified without -m or -j then the stop will only apply to
integration servers. The current run state of the message flow will be saved ready
for restart.
Note: When an integration server is in stopped state it is not possible to start
or stop the message flows within it. An integration server needs to be in running
state to process the start or stop message flow request, and so the only command a
stopped integration server will accept is the request to start the integration
server itself.
$ mqsistartsgflow
ksh: mqsistopmsgflow^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[art: not found
$
$
$