Altova MobileTogether Server Advanced Edition

Welcome to MobileTogether Server
Introduction
- MobileTogether Overview
- Using MobileTogether Server
Set Up MobileTogether Server
Server Procedures
Web UI Reference
Command Line

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

- A -

Active Directory
Active directory login
Address of server
Administrator ports
Altova LicenseServer
Altova ServiceController
Assgning a license to MobileTogether Server on Linux
Assgning a license to MobileTogether Server on macOS
Assgning a license to MobileTogether Server on Windows
Authentication settings

- B -

Backing up MobileTogether Server
Browsers
- enabling execution of solutions for

- C -

Cache settings
Caches
- creating
- settings of
Chrome
- limitations of Altova Help in
- Same-Origin Policy (SOP)
Client ports
Client users list
Command line instructions
Command line instructions (CLI)

- D -

Data files to server
- setting size limits of
Database connections on Linux
Database connections on macOS
Database connections on server-side
Deinstallation
Directory Service login

- E -

Email settings
Encryption
Environment settings on Linux
Environment settings on macOS

- F -

File size limits
File system trigger settings

- G -

Google Chrome
- see Chrome

- H -

Host settings
HTTP and HTTPS ports
- for mobile clients
- for server administrators
HTTP trigger settings

- I -

Installation of MobileTogether Server
Installation on Linux
Installation on macOS
Installing LicenseServer on Linux
Installing LicenseServer on macOS
Installing LicenseServer on Windows
Installing on Windows
Installing on Windows Server Core

- J -

JWT authentication

- K -

- L -

LDAP settings
License for MobileTogether Server
LicenseServer
LicenseServer settings
LicenseServer versions
Licensing MobileTogether Server on Linux
Licensing MobileTogether Server on macOS
Licensing MobileTogether Server on Windows
Licensing of MobileTogether Server
Linux
- installation on
- licensing MobileTogether Server on
Log of server actions
Log settings
Logging settings

- M -

Migrating MobileTogether Server to a new machine
Mobile client ports
Mobile clients
- information for
MobileTogether Server
MobileTogether Server overview

- N -

Network connections

- O -

- P -

Password policies
- assigning members to
- creating
Passwords
- enabling domains for
Permissions
Ports
- for mobile clients, http and https
- for server administrators, http and https
Post-Licensing Tasks on Windows
Privileges
- descriptive list of

- Q -

- R -

Register MobileTogether Server with LicenseServer on Linux
Register MobileTogether Server with LicenseServer on macOS
Register MobileTogether Server with LicenseServer on Windows
Reports
- of privileges
- of privileges by user
Restoring MobileTogether Server
Roles

- S -

- T -

Timer trigger settings
TOC expand/collapse
- see note about Chrome's SOP
Triggers for server services

- U -

Uninstalling
Unlicensed server shutdown
Upgrade settings
Upgrading MobileTogether Server on Windows
User authentication
User licenses
- administration of
User login
- and domain-specific passwords
- importing user domains for
Users

- V -

- W -

Web browsers
- enabling execution of solutions for
Windows
Workflow execution setting
Workflow simulation setting
Workflows
Working directory

- X -

- Y -

- Z -

Navigation: Server Procedures

Frequently Asked Questions

Home Prev Top Next

Click to expand/collapse

There are several workflows on our server. A new solution has been added that uses an ADO connection to an IBM DB2 database. We have noticed that from the time a client tries to access this solution, MobileTogether Server crashes. Deleting the workflow does not help. The problem disappears only when the server is re-started. But it reappears every time a client accesses this solution. Do you know anything about this?

Yes, this is a known problem and is related to the databases in question. Workflows that contain ADO connections to IBM DB2 or Informix databases trigger this crash when the workflow asks the server to access the database for the first time. The reason that the problem persists even after deleting the solution appears to be that some connection data is saved in the server's memory. This connection data is deleted only when the server is re-started.

© 2017-2023 Altova GmbH