Hi Mayank,
You sure can. In fact this is considered a best practice approach - separating the virt engines from the masking engines.
Using the CLI on the virt engine:
MyEngine> maskingjob
MyEngine maskingjob> serviceconfig
MyEngine maskingjob serviceconfig> select 'MASKING_SERVICE_CONFIG-1
MyEngine maskingjob serviceconfig 'MASKING_SERVICE_CONFIG-1'> update
MyEngine maskingjob serviceconfig 'MASKING_SERVICE_CONFIG-1' update *> ls
You'll see a list of all the configurable parameters here. It's "server" you need to update - currently it will be set to localhost. And maybe username and password (of the masking engine).
MyEngine maskingjob serviceconfig 'MASKING_SERVICE_CONFIG-1' update *> set server=
MyEngine maskingjob serviceconfig 'MASKING_SERVICE_CONFIG-1' update *> set credentials.password=
MyEngine maskingjob serviceconfig 'MASKING_SERVICE_CONFIG-1' update *> set username=
MyEngine maskingjob serviceconfig 'MASKING_SERVICE_CONFIG-1' update *> commit
Once you've updated the host, username and password you can check to see if it is working:
MyEngine maskingjob> fetch
MyEngine maskingjob fetch *> commit
MyEngine maskingjob> ls
You should see a list of all available masking jobs.
Cheers
Matt