Configuring Mobile Client 9.3 for Split Deployment Non-Domain

Jacob_Eastman

Out of the box the 9.3 mobile client does not work without a domain and will throw an error (Contact your administrator) when opening a form though logins will work correctly and todo/watch lists will display. This is due to WCF Windows authentication being used on the new attachment endpoint. The following steps can be used to disable Windows auth and allow forms to open properly.

 

Add the following:

<security mode="None"> <transport clientCredentialType="None"></transport> </security>

in the ~\BPM\Engine\application.config as shown below:

<netTcpBinding> <binding name="NetTcpBinding_Attachments" transferMode="Streamed" maxReceivedMessageSize="2147483647"> <readerQuotas maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" maxDepth="2147483647"/> <security mode="None"> <transport clientCredentialType="None"></transport> </security> </binding>

In the ~\BPM\Mobile.Service\web.config, add the same as shown below:

<netTcpBinding> <-- Do not change this name. It is used to interaction with engine attachments --> <binding name="AttachmentOperations" transferMode="Streamed" maxReceivedMessageSize="2147483647"> <readerQuotas maxArrayLength="2147483647"></readerQuotas> <security mode="None"> <transport clientCredentialType="None"></transport> </security> </binding> </netTcpBinding> </bindings>

In the same web.config, update the endpoint address with your engine server as shown below (my_engine_server used as a placeholder):

<client> <endpoint address="net.tcp://my_engine_server:9002/Engine/Attachments" binding="netTcpBinding" bindingConfiguration="AttachmentOperations" contract="EngineAttachments.IAttachmentOperations" name="AttachmentOperations"></endpoint> </client>

In the following registry key on the engine server, set ActivateCallerID to zero (0):

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Metastorm\e-work\Engine

 

Restart the engine and IIS on both servers for the changes to take effect.

 

Note that because ActivateCallerID must be set to zero, the engine server cannot also be used for SSO.