Information
Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Configuring a secured channel


This topic describes how to configure a secured channel for the BMC Remedy ITSM - Mobility server. The secure channel communicates sensitive information between the BMC Remedy ITSM - Mobility Incident Management application and the BMC Remedy Action Request System server. 

To configure a secured channel

  1. Configure web server/Tomcat with SSL.
  2. Verify the configuration by ensuring that the link https://<ServerName>:<SecurePort>/ works.
  3. Go to the MobilityServer/WEB-INF/flex folder.
  4. Uncomment the definition for the mobility-secure-amf channel in service-config.xml. The definition for the mobility-secure-amfchannel is:

    <channel-definition id="mobility-secure-amf"
    class="mx.messaging.channels.SecureAMFChannel">
    <endpoint
    url="https://{server.name}:{server.port}/@context.root@/messagebroker/amfsecure"
    class="flex.messaging.endpoints.SecureAMFEndpoint"/>
    <properties>
    <add-no-cache-headers>false</add-no-cache-headers>
    </properties>
    </channel-definition>
         ...
    <channel ref="mobility-secure-amf"/>
  5. In the following files, uncomment the line: <channel ref="mobility-secure-amf"/>:
    • remoting-config.xml
    • messaging-config.xml
    • data-management-config.xml
    • proxy-config.xml
  6. Restart the Apache Tomcat server.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Remedy ITSM - Mobility: Service Desk 7.6.07