|
The planning, preparation, installation and implementation of the ixi-UMS MDS in many respects depends on whether a new ixi-UMS structure is established or an available ixi-UMS environment is enhanced.
| · | In either case, a share has to be set up at the ixi-UMS Kernel Server. The access is possible by UNC or by WebDav (recommended). |
| · | If the ixi-UMS Kernel Render Connector at the locations is not required, it has to be disabled. For more informationen please refer the How To. |
| · | If the ixi-UMS MDS is installed on a server on that there is already an ixi-UMS Kernel and/or a ixi-UMS Render Connector, the available ixi-UMS Render Connector must be used. In this case the transfer directories have to be configured. |
| · | If the ixi-UMS connectors are already installed on the server, the new transfer directories configured. |
| · | If the WebDav access shall be realized by HTTPS, the Apache servers must be prepared accordingly. |
| · | If the WebDav accesses shall be via the FQDN, these have to be entered in the Apache server. |
| · | Monitoring of the single components must be planned (e.g. by deploying the IXI-Inspector). |
| · | Availability and performance of additonal features like remote inquiry, sender identification, print incoming, user look-up must be taken into account and checked. |
| · | In many cases, a "number conversion" is necessary. This feature is with costs and must be considered with the planning. |
|