Question About Configuration Option "Disable-Client-Operation: 6"

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Remedy AR System Server


    APPLIES TO:

    BMC Remedy AR System Server



    QUESTION:

    We would like to understand the "Disable-Client-Operation" configuration setting a little more to potentially use to restrict access to the Remedy production environment.

    Here is the scenario:
    Customer has an approximate 50-50 distribution of users that use the desktop User Tool client versus a browser. There are various users and/or groups that are technically sophisticated enough to understand and make use of the Remedy ODBC driver for purposes other than the User Tool. In most cases, the use of the ODBC is for Crystal Reports or queries in MS Access and MS Excel using MS Query. Other groups have taken the use of the ODBC to a higher degree and have developed dashboards and/or consoles with it.

    We have experimented with the "Disable-Client-Operation" argument in the AR.CONF file setting a value for Tag Number 6 which seems to block access for tools other than the User Tool or Web Access. However, it seems to also block the ability to Remedy to generate Crystal Reports when clicking the "Print" button or to even run other official reports that are setup in a Crystal Enterprise scheduler.

    What we would like to do is prohibit unapproved users from utilizing the ODBC, but still maintain normal Remedy functionality with the User Tool and Crystal Reports.

    Can this be done?

    LP: BMC Remedy AR System Server 7.5.00
    DR: AR System Client 7.5.00

     


    ANSWER:

     

    Legacy ID:KA382618

      

    If we set Disable-Client-Operation: 6 in ar.cfg, ODBC access to the ARServer is turned off.

    We cannot prohibit unapproved users from utilizing the ODBC, but still maintain normal Remedy functionality with the User Tool and Crystal Reports.

    However, the guest user cannot access the form data by using ODBC driver. You can set the appropriate permission on the form level. If the user doesn't have access/permission for that form then he cannot see any data in the report when he tries to connect/access AR ODBC driver.

     


    Article Number:

    000017959


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles