Outsourcing web applications#
The web applications for XPhone Connect Mobile, Analytics, Meeting and UM Settings can be installed on a separate computer (DMZ). This chapter explains the steps required for setup.
Installation wizard#
Download the software from the C4B homepage <https://www.xphone-connect.com/en/service/software-download/>.
Unzip the compressed file and start the XPhone Connect Server Setup from the directory:
\XPhoneConnect_V10_X_XXX\Software\Server\setup.exe
If the operating system meets the requirements, the Installation Wizard appears, otherwise a message appears.
Select the option No MAPI and click Next.
Select the XPhone Connect as web service operating mode.
Click on Complete or Custom and click Next.
If you selected Custom in the previous dialog, you must install all components manually in the following dialogs.
Server setup#
The setup for the XPhone Connect as Web Service variant will now start. Click Next.
In the Customized Setup dialog box, all features are preselected or deactivated so that only the web services are installed.
Configuration#
The server with the outsourced IIS in the DMZ must be able to reach the ports 2230 and 2231 of the XPhone Connect Server.
WebClientAPI
The WebClientAPI is used by the Mobile App and the Meeting WebApp.
Caution
This setting is made on the Web application server.
Open the WebClientApi directory on the computer on which the web applications are installed:
C:\Program Files\C4B\XPhone Connect Server\WebClientApi
The installation path may differ.
Open the appsettings.json file and search for the following entry:
"XPhoneServerHost":"", "XPhoneServerUnifiedPort": "",
Enter the XPhone Connect Server IP and optionally the port:
"XPhoneServerHost":"10.60.0.120", "XPhoneServerUnifiedPort": "",
Caution
If you do not change the XPhoneServerUnifiedPort, the default port 2231 will be used. The XPhoneServerUnifiedPort must match the setting <gRPC ServerHost="127.0.0.1" ServerPort="2231"> in the atlas.xml of the XPhone Server.
Attention
Please do not use a host name, only IP addresses.
Mobile
Warning
After the upgrade, the XPhone Connect 9 Mobile app is intended for migration purposes only. Please make sure that all users switch to the XPhone Connect 10 Mobile App. The development of the XPhone Connect 9 Mobile App will not be continued.
These settings are only required if you want to use the XPhone Connect 9 Mobile app.
You can omit this configuration for the XPhone Connect 10 Mobile app.
To enable the Mobile Web application to access the XPhone Connect Server, edit the web.config file. On the DMZ server, navigate to:
C:\Program Files\C4B\XPhone Connect Server\XPhoneMobile\
Open the
web.configand search for the entry:<add key="WcfIPEndPoint" value="localhost" />
Replace
localhostwith the IP address or the host name of the XPhone Connect server.
Hint
Here you can find out how to configure the Mobile feature.
Atlas.xml
Caution
This setting is made on the XPhone Server.
Open the Atlas.xml file via the XPhone Connect Server Manager.
The attribute
MaxPoolSize="1000"must be included for the ConnectionStrings Main and VDir.<Databases> <Main type="MSSQL" connection="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=XPDATA;Data Source=DBSERVER\XPCONNECT" autoLockDown="5" organisationDN="ou=Organisation" configurationDN="ou=Configuration" MaxPoolSize="1000" /> <Stats type="MSSQL" connection="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=XPSTATS;Data Source=DBSERVER\XPANALYTICS" autoLockDown="5" /> <VDir type="MSSQL" connection="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=XPVDIR;Data Source=DBSERVER\XPCONNECT" autoLockDown="5" MaxPoolSize="1000" /> </Databases>
machine.config
Caution
This setting is made on the Web application server.
Open the .Net directory on the computer on which the web applications are installed (the version information may vary):
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config
Open the file machine.config and search for the following tag:
<processModel autoConfig="true"/>
Change the tag as follows:
<processModel enable="true" timeout="Infinite" idleTimeout="Infinite" shutdownTimeout="00:00:05" requestLimit="Infinite" requestQueueLimit="5000" restartQueueLimit="10" memoryLimit="60" webGarden="false" cpuMask="0xffffffff" userName="machine" password="AutoGenerate" logLevel="Errors" clientConnectedCheck="00:00:05" comAuthenticationLevel="Connect" comImpersonationLevel="Impersonate" responseDeadlockInterval="00:03:00" responseRestartDeadlockInterval="00:03:00" autoConfig="false" maxWorkerThreads="200" maxIoThreads="100" minWorkerThreads="200" minIoThreads="1" serverErrorMessageFile="" pingFrequency="Infinite" pingTimeout="Infinite" maxAppDomains="2000" />
Attention
With the new setting,
autoConfig="true"must no longer appear in theprocessModeltag.Please adopt all values exactly as they are given.
Important
After making these settings, restart the entire Windows server.
Analytics
To enable the Analytics web application to access the XPhone Connect Server, edit the web.config file. On the DMZ server, navigate to:
C:\Program Files\C4B\XPhone Connect Server\WebStats\
Open the web.config and search for the entry:
<add key="WcfIPEndPoint" value="localhost" />
Replace
localhostwith the IP address or the host name of the XPhone Connect server.In addition, the identity for the Analytics application pool in the IIS (XPhoneConnectAnalytics) must be changed to a domain account with access rights to the XPhone Connect Server (e.g. the MAPI account can be used for this):

UM Settings
To enable UM Settings to access the XPhone Connect Server, edit the web.config file. On the DMZ server, navigate to:
C:\Program Files\C4B\XPhone Connect Server\UMSUserAdminClient
Open the web.config file.
Search for the entry:
<add key="WcfIPEndPoint" value="localhost"/>
Replace
localhostwith the IP address or the host name of the XPhone Connect server.







