Configuring a secured channel

This topic provides information about how to configure a secured channel for the the BMC Remedy ITSM 7.6.05: Mobility server to communicate sensitive information to and from the BMC Remedy ITSM 7.6.05 - Mobility Incident Management application and the BMC Remedy ARserver.

To configure a secured channel

To configure a secured channel, use the following procedures:

1. Edit the services-config.xml in the following directory: MobilityServer/WEB-INF/flex.

2. Remove the server mobility-nio-server and add the following server: secure-nio-server. Fill in the path to the key store file and key store password.

   <servers>
   
      <!--
   
       <server id="mobility-nio-server"
   
         class="flex.messaging.socketserver.SocketServer">
   
       </server>
   
       -->
   
      <server id="secure-nio-server" class="flex.messaging.socketserver.SocketServer">
   
          <properties>
   
              <keystore-file>path to mobility.keystore</keystore-file>
   
              <keystore-password>password of the keystore</keystore-password>
   
          </properties>
   
      </server>
   
    </servers>
   </channel-definition>
   

3. In the channel configuration, replace channel definition to mobility-nio-amfto the following:

   <channel-definition id="mobility-nio-amf" class="mx.messaging.channels.SecureAMFChannel">
   
        <endpoint url="https://{server.name}:443/nioamf" class="flex.messaging.endpoints.SecureNIOAMFEndpoint"/>
   
          <server ref="secure-nio-server"/>
   
          <properties>
   
              <polling-enabled>false</polling-enabled>
   
          </properties>
   
      </channel-definition>
   
4. The secured BMC Remedy ITSM - Mobility server port used here is 443. You can update it to a port that is available on your system. 
5. Restart the Tomcat server. 
6. Inform users that they should connect to the BMC Remedy ITSM - Mobility server port you configured in step 4.