createMsgRoutingRemote Operation

With createMsgRoutingRemote operation you can create message routing rules on a managed TIBCO LogLogic Appliance from a Management Station.

Request Parameters

authToken, applianceIP, routingName, sourceDevice, destinationIP, destinationPort, routingProtocol, enabled, severity, facility, searchFilterName, compressionEnabled, encryptionEnabled, authenticationEnabled

For more information about each common request parameter, see Common Request Parameters.

Response

msgRoutingResponse (see msgRoutingResponse Type)

Example

SOAP request for createMsgRoutingRemote Operation:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:msg="MsgRoutingService">
   <soapenv:Header/>
   <soapenv:Body>
      <msg:createMsgRoutingRemote>
         <!--Optional:-->
         <msg:authToken>admin/admin123</msg:authToken>
         <!--Optional:-->
         <msg:applianceIP>10.114.66.36</msg:applianceIP>
         <!--Optional:-->
         <msg:routingName>hellomr1</msg:routingName>
         <!--Optional:-->
         <msg:sourceDevice>::ffff:10.114.66.36_logapp</msg:sourceDevice>
         <!--Optional:-->
         <msg:destinationIp>10.114.81.44</msg:destinationIp>
         <!--Optional:-->
         <msg:destinationPort>514</msg:destinationPort>
         <!--Optional:-->
         <msg:routingProtocol>TCP Syslog</msg:routingProtocol>
         <!--Optional:-->
         <msg:enabled>yes</msg:enabled>
         <!--Optional:-->
         <msg:severity>high</msg:severity>
         <!--Optional:-->
         <msg:facility>high</msg:facility>
         <!--Optional:-->
         <msg:searchFilterName></msg:searchFilterName>
         <!--Optional:-->
         <msg:compressionEnabled>no</msg:compressionEnabled>
         <!--Optional:-->
         <msg:encryptionEnabled>no</msg:encryptionEnabled>
         <!--Optional:-->
         <msg:authenticationEnabled>no</msg:authenticationEnabled>
      </msg:createMsgRoutingRemote>
   </soapenv:Body>
</soapenv:Envelope>

SOAP response for createMsgRoutingRemote Operation:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Header/>
   <soapenv:Body>
      <ns:createMsgRoutingRemoteResponse xmlns:ns="MsgRoutingService">
         <ns:return xsi:type="ax219:MsgRoutingResponse" xmlns:ax219="http://msgrouting.services.logapp.loglogic.com/xsd" xmlns:ax220="http://services.logapp.loglogic.com/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <ax220:authToken xsi:nil="true"/>
            <ax220:resultCount>1</ax220:resultCount>
            <ax220:statusCode>2000</ax220:statusCode>
            <ax220:statusMessage>Successful</ax220:statusMessage>
            <ax220:summaryOnly>false</ax220:summaryOnly>
            <ax219:resultSet xsi:type="ax219:MsgRoutingDetail">
               <ax219:authenticationEnabled>no</ax219:authenticationEnabled>
               <ax219:compressionEnabled>no</ax219:compressionEnabled>
               <ax219:compressionLevel xsi:nil="true"/>
               <ax219:destinationIP>10.114.81.44</ax219:destinationIP>
               <ax219:destinationPort>514</ax219:destinationPort>
               <ax219:enabled>yes</ax219:enabled>
               <ax219:encryptionEnabled>no</ax219:encryptionEnabled>
               <ax219:facility/>
               <ax219:matchStatus xsi:nil="true"/>
               <ax219:origAuthEnabled xsi:nil="true"/>
               <ax219:routingName>hellomr1</ax219:routingName>
               <ax219:routingProtocol>UDP Syslog</ax219:routingProtocol>
               <ax219:searchFilterName>None</ax219:searchFilterName>
               <ax219:severity/>
               <ax219:sourceDevice>::ffff:10.114.66.36_logapp</ax219:sourceDevice>
               <ax219:transferStatus xsi:nil="true"/>
               <ax219:tunnelStatus xsi:nil="true"/>
            </ax219:resultSet>
         </ns:return>
      </ns:createMsgRoutingRemoteResponse>
   </soapenv:Body>
</soapenv:Envelope>