Web applications on a separate computer

Hint

For 250 or more mobile users, the mobile web application must be outsourced to a separate IIS server. Special settings must be made for this: Special settings for Softphone Mobile.

The web applications for XPhone Connect Mobile, Analytics, Web Meeting and UM Settings can be installed on a separate computer (“DMZ”). This chapter describes how to do this.

Installation wizard

Start the XPhone Connect Server setup with the DVD image under \Server -> setup.exe.
The installation wizard opens. If the operating system meets the requirements, the following window appears, otherwise a note.

Click Next.
Select the option No MAPI and click Next.
Select the XPhone Connect as Web Service operating mode and the Custom installation mode and click Next.
Install the following components and click Next each time.

Server setup on a separate computer (DMZ)

The setup for the XPhone Connect as Web Service variant will now start. Click Next.
In the Custom Setup dialog box, all features are preselected or disabled so that only the web services are installed.

Customizations

The server with the outsourced IIS in the DMZ must be able to reach ports 2230 and 2231 of the XPhone Connect server.

Mobile

In order for the Mobile application to access the XPhone Connect Server, the web.config in the directory (DMZ Server) C:\Program Files\C4B\XPhone Connect Server\XPhoneMobile\ must be adjusted.

Open web.config and search for the entry:

<add key="WcfIPEndPoint" value="localhost" />

Change localhost to the XPhone Connect Server IP address or host name.
Enter the externally accessible URL in the Web Administration under System settings > General > Mobile. This is required for the QR code configuration of the XPhone Connect Mobile app.

Analytics

For the Mobile application to be able to access the XPhone Connect Server, web.config must be adapted in the directory C:\Program Files\C4B\XPhone Connect Server\WebStats\.

Open web.config and search for the entry:

<add key="WcfIPEndPoint" value="localhost" />

Change localhost to the XPhone Connect Server IP address or host name.
Furthermore, the identity for the Analytics application pool must be changed to a domain account with access rights on the XPhone Connect Server in the IIS (XPhoneConnectAnalytics) (e.g. the MAPI account can be used for this):

UM Settings

For UM Settings to be able to access the XPhone Connect Server, the web.config configuration file needs to be adapted:

Open the C:Program FilesC4BXPhone Connect ServerUMSUserAdminClient path on the DMZ Server.
Open the web.config file.

Search for the entry:

<add key="WcfIPEndPoint" value="localhost"/>

Replace localhost with the IP address or host name of the XPhone Connect Server.

Web-Meeting

In order for Web-Meeting to access the XPhone Connect Server, the configuration file web.config must be adapted.
Open the path C:\Program Files\C4B\XPhone Connect Server\WebMeeting.API on the DMZ server.
Open the web.config file.

Search for the entry:

<add key="WcfIPEndPoint" value="localhost"/>

Replace localhost with the IP address or host name of the XPhone Connect Server.

Tip

For an overview of the ports used in the web meeting, see also Ports.

Special settings for Softphone Mobile

The server with the outsourced IIS in the DMZ must be able to reach ports 2230 and 2231 of the XPhone Connect server.

Adaptation of the Atlas.xml on the XPhone Server

Open the file Atlas.xml 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>

Modification of the appsettings.json

Open the WebClientApi directory on the computer where the web applications are installed.
- e.g. C:\Program Files\C4B\XPhone Connect Server\WebClientApi
  The installation path can vary individually.
Open the appsettings.json file
- 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 <gRPC ServerHost="127.0.0.1" ServerPort="2231"> setting in the atlas.xml of the XPhone Server.
  
  Attention
  
  Please do not use hostnames, only IP addresses.

Modification of the machine.config

Open the .Net directory on the computer where the web applications are installed.
- e.g. C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config
  The version specification can of course vary.

Open the machine.config file

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 the processModel tag.
Please adopt all values as given.

Restart the entire Windows server.

Have you found a mistake on this page?

Or is something not formulated well or too vague? Then we look forward to receiving an e-mail, preferably with a suggestion for improvement, to doku@c4b.de. Thank you very much!