Checking the FCS Deployment

You can check the FCS deployment using the validate fcs MQL command. This command will facilitate FCS deployment checking and shorten the time needed to identify deployment issues.

  1. Start MQL as system administrator.
  2. Run the migration tool as follows: 

    MQL<1>validate fcs [store STORENAME] [location LOCATIONNAME] [certificate] [fcsfile] [sync]

    The operations are:

    Parameter/OperationDescription
    store STORENAME Indicate on which store the validation process must be done, launch also the validation for all the locations of the store
    location LOCATIONNAME Indicate on which location the validation process must be done
    certificate

    Validate the deployment of TLS/SSL of the target:

    • does nothing if target does not have an HTTPS URL
    • print an error in case of failure
    • print a warning and the certificate if the certificate of the target expires in less than 30 days
    • print SUCCEEDED in case of success, print also the certificate in verbose mode.
    fcsfile

    Validate the path of the target by writing a file and reading it after:

    • print SUCCEEDED in case of success: the reading of the file matches the writing (check for bad fcs file filter)
    • print an error in case of failure
    sync

    Validate the communication between locations of a same store for synchronization, test every source-destination combination. Note that it is just a communication test and not a full file replication test. If the OOTB centralized replication trigger is set on the store, the tool does not test the direct communication between remote FCS.

    For each combination print SUCCEEDED in case of success, or an error otherwise

    By default, if none of the three operations are chosen, all operations are performed.

    By default, if no target is specified, all operations are done on all stores and locations.

    If a store is specified, all operations are done on the store and locations attached to that store, all sync tests combination are done.

    If a location is specified, all operations are done on the location, store and others location attached to the store, sync tests are done between the location and the store and between the location and each location attached to the store.

    If a location is not attached to a store, validation does nothing.

    The command does not stop at the first failure; it will perform all the tests whatever the results are.

  3. Check the results.

    Here are some sample results:

    Sample OK:

    MQL<20>validate fcs store plmx ;
Result FS for store plmx : SUCCEEDED
Result Certificate for store plmx :  SUCCEEDED

    Sample KO:

    MQL<35>validate fcs store STORE location loc_India_STORE;
Result Transfer for store STORE to Location loc_India_STORE : com.matrixone.fcs.common.FcsException: java.lang.Exception: url https://ve4aldsy.ux.dsone.3ds.com/internal is not defined in FCS Key Define
Result FS for Location loc_India_STORE : com.matrixone.fcs.common.FcsException: java.lang.Exception: url https://ve4aldsy.ux.dsone.3ds.com/internal is not defined in FCS Key Define
Result Certificate for Location loc_India_STORE : java.net.UnknownHostException: ve4aldsy.ux.dsone.3ds.com
Result Transfer for Location loc_India_STORE to store STORE : com.matrixone.fcs.common.FcsException: java.lang.Exception: url https://ve4aldsy.ux.dsone.3ds.com/internal is not defined in FCS Key Define