This article from InSource show how to configure a remote client PC to run the Remote Development client functions for the Wonderware InBatch product. This would include interactive interfaces like the Process Model, Recipe Editor, Batch Scheduler and so forth. This also applies to custom coding of the InBatch API for the Materials Database and the Recipe Database.
- Author: Chris Selph
- Published: 3/5/2019
- Applies to: InBatch 2014 R3 and above
The InBatch Development Client is installed and licensed
On the InBatch Server Computer
Using the Environment Display perform and Exit and shutdown command (this will disable InBatch!)
Run the Wonderware Configurator
Make sure the “Share InBatch for Remote Development Clients” checkbox is checked. Execute Configure
Start Environment Display to restart InBatch
On the Client Remote PC
Run the configurator – pick any unused drive letter for Folder Drive Mapping – Do NOT map this drive ahead of time – the configurator will map it for you.
Run the Configure
To Test functions:
Run Material Editor and verify you can see materials. If it doesn’t start check the logger for an error about TAF. If there is a message then delete Vista.TAF from the Config_A folder on the server
If you need to run custom Material or Recipe API automation server commands from this remote client node, do the following:
from command prompt, run DCOM configuration utility:
mmc comexp.msc /32
Edit the DCOM configuration of the material server or recipe server:
Configure each tab as follows:
End of article.