Home

Altova MobileTogether Server

1. lt array gt lt string gt usr local Altova MobileTogetherServer2 0 bin MobileTogetherServer lt string gt lt string gt debug lt string gt lt array gt lt key gt KeepAlive lt key gt lt true gt lt key gt UserName lt key gt lt string gt _altovamobiletogetherserver lt string gt lt key gt EnvironmentVariables lt key gt LdrictS lt key gt CLASSPATH lt key gt lt string gt usr local jdbc oracle ojdbc jar usr local jdbc oracle xdb jar usr local jdbc oracle xmlparserv2 jar usr local jdbc postgre postgresql 9 0 801 jdbc4 jar usr local jdbc mssql sqljdbc4 jar usr local jdbc iseries lib jt400 jar usr local jdbc mysql mysql connector java Syl lGS bana cian sia locall sjeloe soilikeeis ciliknen doce Oona cia uer Localyajcbcy Informix_JDBC_Driver lib ifxjdbc jar usr local jdbc sybase jconn7 jconn4 jar usr local jdbc db2 db2jcc jar usr local jdbc db2 dipe cm eicouscmeUnmcuaemy lt string gt 4 dict gt lt dict gt lt folist gt 2015 Altova GmbH Altova MobileTogether Server 38 3 4 Setting Up MobileTogether Server Setting Up SSL Encryption Setting Up SSL Encryption If you require that communications between your MobileTogether Server and MobileTogether Client devices are encrypted using the SSL protocol you will need to e Generate an SSL private key and create an SSL public key certificate file e Set up MobileTogether Server for SSL communication The steps to
2. 4 Define basic settings Basic settings include administrator and client ports and other communication settings and security settings 5 Set up user accounts MobileTogether Server is always accessed via a user account so user accounts have to be set up appropriately There are two types of access e Administrator access Administrator access is via the Web UI and is used to carry out administrative tasks Administrative actions include defining communication settings security settings and managing user accounts e End user access End user access is via a mobile device and is used to download MobileTogether solutions to the client Access to solutions on the 2015 Altova GmbH Altova MobileTogether Server 10 Introduction Using MobileTogether Server server is determined by the user account the client logs in with 6 Deploy MobileTogether solutions to MobileTogether Server MobileTogether solutions are deployed from within the MobileTogether Designer application See the MobileTogether Designer user manual 7 Configure MobileTogether Client apps to access MobileTogether Server MobileTogether Client apps on mobile devices must be configured to connect to MobileTogether Server The MobileTogether Server information that is required for configuring MobileTogether Client apps is listed in the section Information for Clients Also see the MobileTogether Client app user manual Server IP address and network firewall setting
3. See the section Licensing on Windows for more information about how to register and license MobileTogether Server with Altova LicenseServer v LicenseServer versions e Altova server products must be licensed either with the version of LicenseServer that is appropriate to the installed MobileTogether Server version or with a later version of LicenseServer Altova MobileTogether Server 2015 Altova GmbH Setting Up MobileTogether Server Setup on Windows 15 The LicenseServer version that is appropriate for a particular version of MobileTogether Server is displayed during the installation of MobileTogether Server You can install this version of LicenseServer along with MobileTogether Server or you can install LicenseServer separately Before installing a newer version of LicenseServer any older one must be de installed The LicenseServer installer will do this automatically if it detects an older version LicenseServer versions are backwards compatible They will work with older versions of MobileTogether Server If you install a new version of MobileTogether Server and if your installed LicenseServer version is older than the appropriate LicenseSereer install the latest version available on the Altova website At the time of LicenseServer de installation all registration and licensing information held in the older version of LicenseServer will be saved to a database on your server machine This data will be imported automaticall
4. For this kind of license the maximum number of users that can access the server at any one time is listed see screenshot below J4MW2YA AMLAU8J 8MWLMDY 757H9MA 04L6MDA 8 i Max licensed users 8 One client machine under different names If a client machine is registered more than once with LicenseServer it might appear in the Server Management tab under multiple names that is with multiple entries This could happen for Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer Configuration Page Reference 177 example if a machine is re registered with the host name given in a different form To ensure that additional licenses are not redundantly assigned to the same machine under its different names you should unregister redundant client machine entries by clicking the Unregister server and all products button of these machines Note While the client machines are considered for the purposes of this documentation to be clients of LicenseServer they are in effect servers of their own products Also if the same license is assigned multiple times to the same machine under its different names licensing conflicts could arise So to avoid these two situations redundant licensing and multiple assignments of a single license it is recommended that redundant entries of a single client machine be unregistered Given below are forms a machine name might take in the Server Management tab e Host name wth domain name
5. HTML HTML browsers for any other mobile devices Altova MobileTogether Server 2015 Altova GmbH Introduction Using MobileTogether Server 9 2 2 Using MobileTogether Server To set up MobileTogether Server for use with MobileTogether clients e Install and configure MobileTogether Server e Deploy MobileTogether solutions from MobileTogether Designer to MobileTogether Server e Configure MobileTogether Client apps on mobile devices to access solutions on a MobileTogether Server The steps in more detail 1 Install MobileTogether Server MobileTogether Server runs on Windows Linux and Mac OS Xsystems Before installing a new version of MobileTogether Server de install any previous version See Installation on Windows Installation on Linux and Installation on Mac OS X 2 License MobileTogether Server In order to license MobileTogether Server it must be able to connect to a LicenseServer on your network Start MobileTogether Server register MobileTogether Server with LicenseServer and assign a license to MobileTogether Server from LicenseServer See Licensing on Windows Licensing on Linux and Licensing on Mac OS X 3 Set up SSL encryption If you wish to encrypt server client communication you can set up SSL encryption for MobileTogether Server see Setting Up SSL Encryption Additionally you will need to configure MobileTogether Client apps to communicate via SSL See the MobileTogether Client app user manual
6. You can install this version of LicenseServer along with MobileTogether Server or you can install LicenseServer separately Before installing a newer version of LicenseServer any older one must be de installed The LicenseServer installer will do this automatically if it detects an older version LicenseServer versions are backwards compatible They will work with older versions of MobileTogether Server If you install a new version of MobileTogether Server and if your installed LicenseServer version is older than the appropriate LicenseSerer install the latest version available on the Altova website At the time of LicenseServer de installation all registration and licensing information held in the older version of LicenseServer will be saved to a database on your server machine This data will be imported automatically into the newer version when the newer version is installed The version number of the currently installed LicenseServer is given at the bottom of the LicenseServer configuration page all tabs Current version 1 23 v Trial license During the installation process you will be given the option of requesting a 30 day trial license for MobileTogether Server After submitting the request a trial license will be sent to the email address you registered Altova MobileTogether Server 2015 Altova GmbH Setting Up MobileTogether Server Setup on Mac OSX 33 Licensing on Mac OS X MobileTogether Server must be licen
7. e The CPU Cores or for MobileTogether Server users column indicates for how many CPU cores or MobileTogether Clients a license is valid e If you wish to make modifications to the license pool for example to upload activate deactivate or delete a license click the Go to License Pool button Select the license you wish to assign The license s check box will be checked Also the total number of CPU cores licensed for that product on that client is listed near the top left of the dialog as Max licensed CPU cores see screenshot above You can select more licenses if you wish to increase the number of licensed CPU cores for that product on that client The Max licensed CPU cores in this case will be the sum of the CPU cores of all the selected licenses After selecting the license s click Apply Changes The license s will be assigned to that product and displayed in the Server Management tab see screenshot below The screenshot below shows that a 2 CPU core license for Altova FlowForce Server has been assigned to the client machine Doc altova com This server has 2 CPU core s Licenses for 2 CPU core s are required BUMO9M6 X5XJW9A 8U999H5 9H6XL75 5L2AA11 85F8WM1 16 i Limit to single thread execution Max licensed CPU cores 16 Unregistering products Each Altova product registered with LicenseServer is listed in the Server Management tab under Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer
8. Altova LicenseServer 127 About this documentation This documentation is organized into the following parts e Introductory information about network requirements installation on Windows Linux and Mac OS X and Altova ServiceController e How to Assign Licenses which describes in a step by step way how to assign licenses with Altova LicenseServer e Configuration Page Reference A description of the administrator s interface with LicenseServer Last updated 09 November 2015 2015 Altova GmbH Altova MobileTogether Server 128 Altova LicenseServer Network Information 7 1 Network Information Altova LicenseServer must be installed on a server machine that is accessible by all clients running Altova products that require a license Any firewall on both the client and server must allow the network traffic to and from the LicenseServer that is necessary for the LicenseServer to operate correctly On the LicenseServer machine port 35355 is used to distribute licenses and therefore it must be open for network traffic with client machines The following are the default networking parameters and requirements of LicenseServer e For LicenseServer license distribution Either one or both of IPv4 TCP connection on port 35355 IPv6 TCP connection on port 35355 For administrative tasks the LicenseServer is accessed by a web interface that uses port 8088 The port used can be configured to suit your requirements Connection to the M
9. and it has no initial password v About Privileges A privilege is an activity that a user is allowed to carry out There is a fixed number of MobileTogether Server privileges and a user can be assigned zero to all of the available privileges It is however good practice to assign privileges via roles see next section rather than to assign privileges directly to the user The assigning of privileges and roles to a user is done by a user that has been assigned this privilege Initially it is root user that has this Altova MobileTogether Server 2015 Altova GmbH Server Procedures Users and Roles 57 privilege The screenshot below shows all the available privileges Privileges W Maintain users roles and privileges V Set own password V Override security Y Allow to use stored password on client do not require authentication on application start V View unfiltered log V View cache overview V View user licenses overview V Read users and roles 7 Manage server settings L Trace workflow Enables detailed workflow execution logging to files including working XML files when the Logging to File option ts enabled V Read global resources W Write global resources Open workflow from designer M Save workflow from designer W Run server simulation The tab Users and Roles Reports Privileges Report provides a list of all privileges with each privilege being listed together with
10. information for 63 MobileTogether Server 3 installing 12 licensing 12 setting up 12 starting 47 using 9 MobileTogether Server overview 7 Index N Network information 128 Network settings 180 P Password default at startup 138 Password policies assigning members to 87 creating 87 Passwords enabling domains for 96 Permissions 70 Ports for mobile clients http and https 96 for server administrators http and https 96 Privileges 56 descriptive list of 59 R Registering HowForce Server with LicenseServer 150 Registering MapForce Server with LicenseServer 155 Registering StyleVision Server with LicenseServer 157 Reports of privileges 89 of privileges by user 89 Restoring MobileTogether Server 64 Roles 56 assigning members to 83 creating 83 defining privileges for 83 S Server actions log of 92 Server address 96 2015 Altova GmbH Index Server administrator ports 96 Working directory 96 Server folders management of 70 structure of 70 Server Management tab 162 174 Server Monitoring tab 179 Server session timeouts 96 Server side solution s working directory 96 ServiceController 134 setdeflang command 119 Seitings 96 180 Setup on Linux 20 on Mac OS X 29 on Windows 13 Simulation settings 96 Solutions directory on server 96 SSL certificates 96 SSL encryption 38 49 StyleVision Server registering with LicenseServer 157 U Upl
11. possesses this privilege Override security Any user having this privilege can change permissions in the container hierarchy without needing write security permission This allows MobileTogether administrators to regain access to resources accidentally rendered inaccessible This is an administrative privilege and should only be assigned to MobileTogether administrators By default only root 2015 Altova GmbH Altova MobileTogether Server 60 Server Procedures Available Privileges possesses this privilege Allow use of stored password on client Allows the user to use the password stored on the client User does not need authentication View unfiltered log By default users can only see log entries related to Configurations they have read access to By granting this privilege a user can read all log entries including those not associated with a specific configuration By default only root possesses this privilege View cache overview Allows the user to view the cache overview on the server View user licenses overview Allows the user to see the licenses overview on the server Read users and roles By default users will only see their own user account and any roles they are member of By granting this privilege a user can read all defined users and roles By default only root possesses this privilege Manage server settings Allows the user to edit server settings Trace work flow Allows detailed workflow
12. the fully qualified domain name FQDN such as Win80 x64_1 my domain com or Doc3 my domain com This happens when the host name of the machine with or without the domain information is passed as the argument of the licenseserver CLI command that is used to register the server product with LicenseServer For example lt AltovaServerProduct gt licenseserver Doc3 This produces an FQDN such as Doc3 my domain com An FQDN is also produced when localhost is supplied on Windows 7 systems as the host name e Host name without domain name For example win80 x64_1 or Doc3 This happens on Windows 8 systems when localhost is given as the machine name e localhost In some cases localhost is also displayed as a machine name Note If during installation of the Altova server product on Windows machines the machine is automatically registered with LicenseServer localhost is used by the installer as the machine name Requesting an evaluation license You can obtain a 30 day free evaluation license for each of a client s installed Altova products that have been registered with LicenseServer Click the Request Evaluation Licenses button near the bottom of the Server Management tab A dialog pops up containing a list of the Altova server products on that client machine which have been registered with LicenseServer Make sure that the products for which you want an evaluation license are checked then fill in the registration fields and s
13. while the mobile client ports are those the mobile client device uses to connect to the services of MobileTogether Server Set the administrator ports The administrator ports provide access for the following purposes e To connect to the server s Web UI and perform administrative functions such as setting up Users and Roles e To deploy MobileTogether designs as MobileTogether solutions to the server MobileTogether Designer has a setting that specifies the address and port of the MobileTogether Server to which to deploy designs Administrator ports Select unsecure HTTP and secure HTTPS ports to be used by the administrator These ports can be used for server configuration user role and user license administration workflow deployment and workflow simulation Specify a hostname when you intend to open the administration page from Altova ServiceController This avoids browser warnings about the certificate not matching the URL E HTTP Port 8085 HTTPS Port 8086 Hostname myhost altova com The HTTP port is the unsecure port HTTPS is the secure port To use HTTPS you need to set up SSL Encryption If you set up the HTTPS port and wish to avoid browser warnings about the SSL certificate not matching the URL then specify the hostname of the computer on which the MobileTogether Server configuration page will be opened Set the mobile client ports The ports that mobile devices will use to connect to the ser
14. 01 amp anonymous amp root Create User Import Domain Users 2 Onthe Create User page enter a user name and password 3 To assign privileges to the user you can either select the privileges directly by checking their check boxes and or assign roles to the user see next section A user will have privileges that are directly assigned plus those inherited from all assigned roles We recommend using roles to assign privileges to a user see next section 4 Select a password policy from the policies that you have defined 5 Click Save to finish The user now appears in the list of users see screenshot above You can edit a user s properties by clicking the user name in the list of users v Importing a domain user If Active Directory login has been enabled for a domain without automatically importing all users you can import individual domain users of an enabled domain Click Import Domain Users see screenshot below In the Import Domain Users dialog that is displayed search for the user you want to import select the user and click Import Selected Altova MobileTogether Server 2015 Altova GmbH Web Ul Reference Users and Roles 81 Users Name B TechWriter 01 amp anonymous E B root Create User Import Domain Users After the user is imported you can assign roles to the user as for any other user The new user can now log in to MobileTogether Server with the user s domain specific user
15. Altova CentOS RedHat rpm qa grep server If MobileTogether Server is not installed go ahead with the installation as documented below in Installing MobileTogether Server If MobileTogether Server is installed and you wish to install a newer version of MobileTogether Server uninstall the old version with the command Debian Ubuntu sudo dpkg remove mobiletogetherserver CentOS RedHat sudo rpm e mobiletogetherserver If you need to uninstall an old version of Altova LicenseServer do this with the following command Debian Ubuntu sudo dpkg remove licenseserver 2015 Altova GmbH Altova MobileTogether Server 22 Setting Up MobileTogether Server Setup on Linux CentOS RedHat sudo rpm e licenseserver v Download the Linux package MobileTogether Server installation packages for the following Linux systems are available at the Altova website Distribution Package extension Debian 6 and higher Ubuntu12 04 and higher RedHat 6 and higher After downloading the Linux package copy it to any directory on the Linux system Since you will need an Altova LicenseServer in order to run MobileTogether Server you may want to download LicenseServer from the Altova website at the same time as you download MobileTogether Server rather than download it at a later time v Install MobileTogether Server In a terminal window switch to the directory where you have copied the Linux package For example if you copied
16. Altova MobileTogether Server 2015 Altova GmbH Setting Up MobileTogether Server Setup on Windows 19 After successfully registering MobileTogether Server it will be listed in the Server Management tab of the configuration page of LicenseServer Go there and assign a license to MobileTogether Server Note on cores and licenses The licensing of Altova server products is based on the number of processor cores available on the product machine for MobileTogether Server an additional licensing option is available see below For example a dual core processor has two cores a quad core processor four cores a hexa core processor six cores and so on The number of cores licensed for a product must be greater than or equal to the number of cores available on that server machine whether the server is a physical or virtual machine For example if a server has eight cores an octa core processor you must purchase at least one 8 core license You can also combine licenses to achieve the core count So two 4 core licenses can also be used for an octa core server instead of one 8 core license If you are using a computer server with a large number of CPU cores but only have a low volume to process you may also create a virtual machine that is allocated a smaller number of cores and purchase a license for that number Such a deployment of course will have less processing speed than if all available cores on the server were utilized Note Each
17. Altova ServiceController ServiceController for short is an application for conveniently starting stopping and configuring Altova services on Windows systems ServiceController is installed with Altova LicenseServer and with Altova server products that are installed as services FlowForce Server RaptorxML XBRL Server and Mobile Together Server It can be started by clicking Start Altova LicenseServer Altova ServiceController This command is also available in the Start menu folders of Altova server products that are installed as services FlowForce Server RaptorXML XBRL Server and Mobile Together Server After ServiceController has been started it can be accessed via the system tray screenshot below al EN 4 ml i 3 18 PM To specify that ServiceController starts automatically on logging in to the system click the ServiceController icon in the system tray to display the ServiceController menu screenshot below and then toggle on the command Run Altova ServiceController at Startup This command is toggled on by default To exit ServiceController click the ServiceController icon in the system tray and in the menu that appears see screenshot below click Exit Altova ServiceController B Altova FlowForce Server gt DB Altova FlowForce Web gt N Altova LicenseServer gt w Altova MobileTogether Server gt Start service Altova RaptorXML XBRL Server gt Stop service Exit Altova ServiceController Ru
18. An inactive license can be activated or deleted from the license pool If a license is deleted from the license pool it can be uploaded again to the pool by uploading the license file containing it When a license file is updated only those licenses in it that are not already in the pool will be uploaded to the pool To activate deactivate or delete a license select it and then click the Activate Deactivate or Delete button respectively Activate the license s you wish to use Before you can assign a license to an Altova product it must be active So do ensure it is active If it is inactive select it and click Activate Next Steps After you have uploaded the license file to the LicenseServer and checked that the license you 2015 Altova GmbH Altova MobileTogether Server 148 Altova LicenseServer How to Assign Licenses want is active do the following 1 Register the Altova server product FlowForce Server MapForce Server StyleVision Server with LicenseServer If you have already done this prior to uploading the license file you can now start assigning licenses 2 Assign a license to your Altova product that has been registered with the LicenseServer Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer How to Assign Licenses 149 Register Product s Before you can assign a license to an Altova server product you must register the product installation with LicenseServer The registration is done from
19. Enter address here or search for a LicenseServer A confirmation dialog appears asking you to confirm that you wish to set the current LicenseServer as the Failover LicenseServer of the Primary LicenseServer you have just selected Click Yes if you wish to confirm Note that going ahead with the confirmation will remove any installed licenses and registered clients on the current LicenseServer Once a Failover LicenseServer has been configured both the Primary LicenseServer and Failover LicenseServer will have notifications about their respective modes at the top of the Configuration Page In the two screenshots below the Failover LicenseServer is shown first then the Primary LicenseServer ALTOVA LicenseServer Failover LicenseServer for Primary at kubu6 altova com ALTOVA LicenseServer Primary LicenseServer with Failover at deji2 altova com Note the following points After a Failover LicenseServer has been configured it periodically synchronizes all licenses registered clients and license agreements from the Primary If the Primary becomes unavailable then the Failover takes over the role of LicenseServer Once the Primary becomes available again the Primary retakes control from the Failover Any license related modifications made on the Failover in this period will be lost when the Primary regains control The Failover LicenseServer will provide licenses only to clients that are of version 2015 rel 3 or later Older client
20. FlowForce Server If MobileTogether Server was installed as part of a FlowForce Server installation registering FlowForce Server with LicenseServer will automatically also register MobileTogether Server How to register FlowForce Server is described in the FlowForce Server documentation Essentially i Start Altova FlowForce Web as a service via ServiceController see previous point ii Enter your password to access the Setup page iii Select the LicenseServer name or address and click Register with LicenseServer After successful registration go to the Server Management tab of LicenseServer s configuration page to assign a license to MobileTogether Server Register a standalone MobileTogether Server Register MobileTogether Server via e its CLI using the 1icenseserver command MobileTogetherServer licenseserver options ServerName Or IP Address For example if localhost is the name of the server on which LicenseServer is installed MobileTogetherServer licenseserver localhost e the Settings tab of MobileTogether Server s Web UI Essentially i Start MobileTogether Server via ServiceController see previous point ii Enter your password to access the Setup page iii Select the LicenseServer name or address and click Register with LicenseServer After successful registration go to the Server Management tab of LicenseServer s configuration page to assign a license to MobileTogether Server v Assign a license
21. How to Assign Licenses 167 its client machine name and has an Unregister icon to its right Click this icon to unregister the product If a license was assigned to the product the assignment will be terminated when the product is unregistered To unregister all products click the Unregister Server and All Products button at the bottom of the Server Management tab see first screenshot in this section To re register a product go to the product s pre configuration page 2015 Altova GmbH Altova MobileTogether Server 168 Altova LicenseServer Configuration Page Reference 7 7 Configuration Page Reference The LicenseServer Configuration page is the administrator s interface with LicenseServer Web UI It allows the management of LicenseServer and the licensing of Altova products that have been registered with LicenseServer FlowForce Server MapForce Server StyleVision Server RaptorXML XBRL Server The LicenseServer Configuration page is viewed in a web browser How to open the Configuration page is described in the sections Open LicenseServer Config Page Windows and Open LicenseServer Config Page Linux This section is a user reference for the Configuration page and is organized by the tabs of the Configuration page License Pool Server Management Server Monitoring Settings Messages Log Out For a step by step guide of how to assign licenses with LicenseServer see the section How to Assign Licenses Altova MobileTo
22. If in the design the file s location is given by an absolute path then this path must point to a location inside a directory that is a sub directory of the Working Directory specified in this setting For example if the file is addressed with the absolute path C MTSData Test xml then the file will be accessed only if the Working Directory is C Of C MTSData Server side solution s working directory Directory C MobileTogether Specify the server side directory where solution s files can be saved It is also used as the base for resolving solution s relative paths The Working Directory setting in effect restricts any read write access to local files during execution of solutions Only files inside the Working Directory or any of its sub directories can be accessed by MobileTogether Server for the execution of solutions v Cache settings Specifies i the directory where cache files are saved ii the timeout for each cache operation and iii the duration in days for how long cache log items are displayed See the Cache tab for more information 2015 Altova GmbH Altova MobileTogether Server 100 Web UI Reference Settings Cache settings Cache directory C ProgramData Altova MobileTogetherServer cache Specify the server side directory where cached files will be placed a Cache operation timeout 0 sec s Timeout in seconds for each cache operation 0 means infinite Cache Log Limi
23. If you need to stop MobileTogether Server replace start with stop in the above commands 2015 Altova GmbH Altova MobileTogether Server 48 Server Procedures Start MobileTogether Server v On Mac OS X To start MobileTogether Server as a service on Mac OS Xsystems run the following command in a terminal window sudo launchctl unload Library LaunchDaemons com altova MobileTogetherServer plist If at any time you need to stop MobileTogether Server use sudo launchctl unload Library LaunchDaemons com altova MobileTogetherServer plist Altova MobileTogether Server 2015 Altova GmbH Server Procedures Set Up SSL Encryption 4 3 2015 Altova GmbH Set Up SSL Encryption If you require that communications between your MobileTogether Server and MobileTogether Client devices are encrypted using the SSL protocol you will need to e Generate an SSL private key and create an SSL public key certificate file e Set up MobileTogether Server for SSL communication The steps to do this are listed below MobileTogether uses the open source OpenSSL toolkit to manage SSL encryption The steps listed below therefore need to be carried out on a computer on which OpenSSL is available OpenSSL typically comes pre installed on most Linux distributions and on Mac OS X machines It can also be installed on Windows computers 1 Generate a private key SSL requires that a private key is installed on MobileTogether Server This private k
24. Keep this entry blank 49 Altova MobileTogether Server 50 Server Procedures 3 Buy an SSL certificate Purchase an SSL certificate from a recognized certificate authority CA such as VeriSign or Thawte For the rest of these instructions we follow the VeriSign procedure The procedure with other CAs is similar Go to the VeriSign website Click Buy SSL Certificates Different types of SSL certificates are available For MobileTogether Server Secure Site or Secure Site Pro certificates are sufficient EV extended verification is not necessary since there is no green address bar for users to see Proceed through the sign up process and fill in the information required to place your order When prompted for the CSR created in Step 2 copy and paste the content of the my csr file into the order form Pay for the certificate with your credit card Set Up SSL Encryption Allow time for obtaining a certificate Obtaining public key certificates from an SSL certificate authority CA typically takes two to three business days Please take this into account when setting up your MobileTogether Server 4 Receive public key from CA Your certificate authority will complete the enrollment process over the next two to three business days During this time you might get emails or phone calls to check whether you are authorized to request an SSL certificate for your DNS domain Please work with the authority to complete the
25. Mobile client ports Select unsecure HTTP and secure HTTPS ports the Mobile clients will use These ports cannot be used for administrative purposes V HTTP Port 8083 E HTTPS Port 8084 Make sure that any firewall is set up to allow access to MobileTogether Server through the HTTPS port 10 Test SSL communication Altova MobileTogether Server 2015 Altova GmbH Server Procedures Set Up SSL Encryption 53 You can now use any SSL testing tool to check whether secure communication with your server via HTTPS is working properly For example this can be done witha browser using the following SSL test site https ssltools websecurity symantec com checker views certCheck jsp This will tell you i whether the public key certificate file was properly constructed with the intermediate trust chain in Step 7 and ii whether your server can be reached properly through the firewall 11 Enable MobileTogether Clients to use SSL In MobileTogether Client apps that communicate with an SSL enabled MobileTogether Server enable SSL communication by checking the SSL Encryption checkbox See the MobileTogether Client documentation for information about how to find this check box 2015 Altova GmbH Altova MobileTogether Server 54 Server Procedures Set Administrator and Mobile Client Ports 4 4 Set Administrator and Mobile Client Ports The administrator ports are used to connect to the Web UI of MobileTogether Server
26. Server with LicenseServer 5 Assign licenses to Altova server In the Server Management tab of the Configuration page Licenses can thereafter be conveniently monitored and managed centrally with LicenseServer See the Configuration Page Reference for available functionality Note The LicenseServer Configuration page does not support SSL v LicenseServer versions and their compatibility with Altova server products New versions of Altova server products can only be licensed with the version of LicenseServer that is the latest at the time of the server product s release However older versions of Altova server products will work with newer versions of LicenseServer So if you are installing a new version of an Altova server product and if your current LicenseServer version is not the latest de install this older version and install the latest version available on the Altova website All registration and licensing information held in your older version of LicenseServer will be saved at the time of de installation to a database on your server machine and will be imported automatically into the newer version When you install a newer version of LicenseServer the older version will be de installed before the newer version is installed The version number of the currently installed LicenseServer is given at the bottom of the LicenseServer configuration page all tabs Current version 1 23 Altova MobileTogether Server 2015 Altova GmbH
27. ServiceController is installed with Altova LicenseServer and with Altova server products that are installed as services FlowForce Server RaptorXML XBRL Server and Mobile Together Server It can be started by clicking Start Altova LicenseServer Altova ServiceController This command is also available in the Start menu folders of Altova server products that are installed as services FlowForce Server RaptorxML XBRL Server and Mobile Together Server After ServiceController has been started it can be accessed via the system tray screenshot below T 1 oO 3 18PM To specify that ServiceController starts automatically on logging in to the system click the ServiceController icon in the system tray to display the Service Controller menu screenshot below and then toggle on the command Run Altova ServiceController at Startup This command is toggled on by default To exit ServiceController click the ServiceController icon in the system tray and in the menu that appears see screenshot below click Exit Altova ServiceController Altova MobileTogether Server 2015 Altova GmbH Setting Up MobileTogether Server Setup on Windows 17 BD Altova FlowForce Server BD Altova FlowForce Web Ad Altova LicenseServer Altova LicenseServer a eae D Altova MobileTogether Server Start service Altova RaptorXML XBRL Server Stop service Exit Altova ServiceController Run Altova ServiceController at startup A aml PD 11 00 A
28. Settings tab of the Configuration page then a new URL is generated each time LicenseServer is started You will need to check the current version of webUI htm1 to find out the current URL of the Configuration page The dynamically generated URL in webu htm1 will have a form something like http 127 0 0 1 55541 and it is located in the function checkIfServiceRunning ina script near the end of the lt head gt element While the port number in the URL is dynamically assigned the IP address part identifies the server on which LicenseServer has been installed If you wish to access the LicenseServer Configuration page from another machine make sure that the IP address part of the URL has the correct IP address or name of the server on which LicenseServer has been installed For example the URL could be something like http MyServer 55541 Note The Configuration page can also be accessed directly via the Finder Applications Altova License Server icon Logging in with the initial password 2015 Altova GmbH Altova MobileTogether Server 144 Altova LicenseServer How to Assign Licenses After going through the steps above the Configuration page is opened with the login mask displayed screenshot below You can log in with the initial password of default After you have logged in you can change your password in the Settings tab ALTOVA LicenseServer Please enter password to log in Initial password is default sec
29. The install command installs MobileTogether Server as a service on the server machine The command takes no options Note that installing MobileTogether Server as a service does not automatically start the service To start the service use the start command To uninstall MobileTogether Server as a service use the uninstall command Examples Examples of the install command mobiletogetherserver install v Casing on the command line MobileTogetherServer on Windows mobiletogetherserver on Unix Linux Mac Note that lowercase mobiletogetherserver works on all platforms Windows Linux and Mac while upper lower MobileTogetherServer works only on Windows and Mac Altova MobileTogether Server 2015 Altova GmbH 113 Command Line Usage 6 5 start This section e Command syntax e Command description e Examples Command syntax Windows MobileTogetherServer start Linux mobiletogetherserver start Mac mobiletogetherserver start Command description start The start command starts MobileTogether Server as a service on the server machine The command takes no options Note that if MobileTogether Server is not installed as a service you can install it with the install command To uninstall MobileTogether Server as a service use the uninstall command Examples Examples of the start command mobiletogetherserver start v Casing on the command line MobileTogetherServer on Windows mobiletogetherser
30. an Altova LicenseServer on your network MapForce Server will automatically also be registered with LicenseServer How to register FlowForce Server is described in the FlowForce Server documentation and in the section Register FlowForce Server with LicenseServer After the registration you can go to LicenseServer and assign a MapForce Server license to MapForce Server How to do this is described in the section Assign Licenses to Registered Products Registering a standalone MapForce Server Windows If you have installed MapForce Server as a standalone package you must register it with an Altova LicenseServer on your network and then license it from the Altova LicenseServer You can register MapForce Server via its command line interface CLI by using the Licenseserver command MapForceServer licenseserver Server Or IP Address For example if LicenseServer is running on http localhost 8088 then register MapForce Server with MapForceServer licenseserver localhost 2015 Altova GmbH Altova MobileTogether Server 156 Altova LicenseServer How to Assign Licenses After successfully registering MapForce Server you can go to LicenseServer and assign a license to MapForce Server How to do this is described in the section Assign Licenses to Registered Products Registering MapForce Server Linux On Linux machines MapForce Server can be registered with LicenseServer by using the licenseserver command of the MapForce Server C
31. and privileges privilege Create a new role as follows 1 Inthe Users and Roles Roles tab click Create Role see screenshot below This displays the Create Role page 2015 Altova GmbH Altova MobileTogether Server 84 Web Ul Reference Roles ce Name amp all amp authenticated B workflow designer a workflow user Create Role Import Domain Roles 2 On the Create Role page give the role a name Users and Roles 3 To define privileges for the role select the privileges by checking their check boxes Privileges Y Maintain users roles and privileges Y Set own password V Override security V Allow to use stored password on client do not require authentication on application start V View unfiltered log W View cache overview W View user licenses overview V Read users and roles V Manage server settings Trace workflow Enables detailed workflow execution logging to files including working XML files when the Logging to File option ts enabled V Read global resources W Write global resources V Open workflow from designer V Save workflow from designer W Run server simulation 4 Click Save to finish After you have saved the role you can assign members to it in the Members pane at the bottom of the page see next section A member can be a user or another role You can subsequently edit a role s properties by clicking the role s name in the list of r
32. as a service To stop MobileTogether Server in this mode press Ctrl C The command takes no options Examples Examples of the debug command mobiletogetherserver debug v Casing on the command line MobileTogetherServer on Windows mobiletogetherserver on Unix Linux Mac Note that lowercase mobiletogetherserver works on all platforms Windows Linux and Mac while upper lower MobileTogetherServer works only on Windows and Mac 2015 Altova GmbH Altova MobileTogether Server 116 Command Line Usage 6 8 upgradedb This section e Command syntax e Command description e Examples Command syntax Windows MobileTogetherServer upgradedb Linux mobiletogetherserver upgradedb Mac mobiletogetherserver upgradedb Command description upgradedb The upgradedb command updates the structure of the internal MobileTogether Server database to that of the new MobileTogether Server version and inserts correct default values This is necessary if the structure of the DB changes from one version of MobileTogether Server to the next The DB structure needs to be updated in order for the new version to work with the existing data The command takes no options Examples Examples of the upgradedb command mobiletogetherserver upgradedb v Casing on the command line MobileTogetherServer on Windows mobiletogetherserver on Unix Linux Mac Note that lowercase mobiletogetherserver works on all platforms Windows Li
33. command above contains one argument the command export resourcestrings for which help is required When the example command above is executed information about the xportresourcestrings command will be displayed in the terminal v Casing on the command line MobileTogetherServer on Windows mobiletogetherserver on Unix Linux Mac Note that lowercase mobiletogetherserver works on all platforms Windows Linux and Mac while upper lower MobileTogetherServer works only on Windows and Mac 2015 Altova GmbH Altova MobileTogether Server 122 Command Line Usage help The help option Help information about a command is also available by using the help option with the command for which help information is required For example using the help option with the xportresourc strings command as follows mobiletogetherserver exportresourcestrings help achieves the same result as does using the help command with an argument of xportresourcestrings mobiletogetherserver help exportresourcestrings In both cases help information about the exportresourcestrings Command is displayed Altova MobileTogether Server 2015 Altova GmbH Command Line Usage version 123 6 12 version This section e Command syntax e Command description e Examples Command syntax Windows MobileTogetherServer version Linux mobiletogetherserver version Mac mobiletogetherserver version Command description The version comm
34. do this are listed below MobileTogether uses the open source OpenSSL toolkit to manage SSL encryption The steps listed below therefore need to be carried out on a computer on which OpenSSL is available OpenSSL typically comes pre installed on most Linux distributions and on Mac OS X machines It can also be installed on Windows computers 1 Generate a private key SSL requires that a private key is installed on MobileTogether Server This private key will be used to encrypt all data sent to MobileTogether Client apps To create the private key use the following OpenSSL command openssl genrsa out private key 2048 This creates a file called private key which contains your private key Note where you save the file You will need the private key to i generate the Certificate Signing Request CSR and ii to be installed on MobileTogether Server see Step 8 below 2 Certificate Signing Requests CSRs A Certificate Signing Request CSR is sent to a certificate authority CA such as VeriSign or Thawte to request a public key certificate The CSR is based on your private key and contains information about your organization Create a CSR with the following OpenSSL command which provides the private key file private key that was created in Step 1 as one of its parameters openssl req new nodes key out my csr During generation of the CSR you will need to give information about your organization such as that listed belo
35. execution logging to files if the logging to file directory option is enabled in the Logging group of the Settings dialog box Read global resources Allows the user with this privilege to read the global resource alias configuration from the server Write global resources Allows the user with this privilege to write save the global resource alias configuration to the server Open work flow from designer Allows a user to open a deployed MobileTogether design file from the server The host login details are supplied by selecting the menu option File Open from MobileTogether server Save workflow from designer Allows a user to save deploy a MobileTogether design file to the server The host login details are supplied by selecting the menu option File Save to MobileTogether server Altova MobileTogether Server 2015 Altova GmbH Server Procedures Available Privileges 61 a Run server simulation Allows the user having this privilege to run a simulation from the browser and preview the result Note the Back browser button returns you to the container view 2015 Altova GmbH Altova MobileTogether Server 62 Server Procedures Configure the Firewall 4 7 Configure the Firewall Server IP address and network firewall settings Your server can have a public IP address accessible over the Internet and or a private IP address accessible within a private network for example via WiFi within a company network If a mobile cli
36. has 2 CPU core s Key Code CPU Cores Licenses for 2 CPU core s are required a aT ea A IC Limit to single thread execution Altova StyleVision Server 2014 This server has 2 CPU core s Key Code CPU Cores Licenses for 2 CPU core s are required ey ee I Limit to single thread execution Altova MapForce Server 2014 This server has 2 CPU core s ESA aCe ASN eA RM UELI Max licensed CPU cores 0 ILimit to single thread execution w Request evaluation licenses Unregister server and all products Note the following points about the Server Management tab Each product is listed under the name of its client machine In the screenshot above one client machine named Doc altova con is listed This client machine Doc altova com has three Altova products registered with the LicenseServer If an Altova product on a different client machine is registered with this LicenseServer then that client machine with its registered products will also be listed in the Server Management tab Each registered Altova product on a client machine has its own Key Code entry which takes the key code of a license A registered product s key code is assigned by clicking its Edit Assigned Licenses button see icon list below and selecting the required license from those available for that product for example FlowForce Server in the license pool This procedure is explained in more detail below Each product also has a line stating how many CPU cores need
37. in MobileTogether Designer See the http manual altova com MobileTogether mobiletogetherdesigner index html for more information e Max Cache Entries A cache can be created by using a set of parameters Each set of parameters generates one cache entry and if different sets of parameters are specified multiple cache entries will be created When defining a cache the maximum number of cache entries can be specified so that an upper limit is placed on the amount of server space that is used for the caches of a particular data source specify parameters This number specifies how many cache entries will be stored before the first cache entry is purged and the latest cache entry is appended Altova MobileTogether Server 2015 Altova GmbH Web Ul Reference Cache 95 e Total Cache Size This is the total size for all cache entries allocated to the cache on the hard disk or other medium Cache size is automatically allocated e Active This check box lets you activate or deactivate a cache on the server When a cache is deactivated its metadata properties still exists on the server but the cache is emptied and it is not available Click Save to confirm the setting e To delete a cache from the server select it and click Delete Selected If the cache has been defined to be updated periodically a new cache will be generated at the next update time 2015 Altova GmbH Altova MobileTogether Server 96 Web UI Reference Settings 5 6 Sett
38. in curly brackets such as option Or product 3 Contact Altova Support to generate a localized MobileTogether Server DLL file from your translated XML file 4 After you receive your localized DLL file from Altova Support save the DLL in the c Program Files x86 Altova lt APPFOLDER bin folder Your DLL file will have a name of the form MobileTogetherServer2016_lc d1l The _1c part of the name contains the language code For example in MobileTogetherServer2016_de d11 the de part is the language code for German Deutsch 5 Run the setdeflang command to set your localized DLL file as the MobileTogether Server application to use For the argument of the setdeflang command use the language code that is part of the DLL name Note Altova MobileTogether Server is delivered with support for five languages English German Spanish French and Japanese So you do not need to create a localized version of these languages To set any of these languages as the default language use MobileTogether Server s setdeflang command Altova MobileTogether Server 2015 Altova GmbH Command Line Usage setdeflang 119 6 10 setdeflang This section e Command syntax e Command description e Examples e Supported languages Command syntax Windows MobileTogetherServer setdeflang sdl LangaugeCode Linux mobiletogetherserver setdeflang sdl LangaugeCode Mac mobiletogetherserver setdeflang sdl LangaugeCode Command description T
39. installations to run Stopping LicenseServer will also stop all connected MobileTogether Server installations If this happens you will need to first restart LicenseServer and then restart the stopped MobileTogether Server installation that you want to work with Start and stop LicenseServer as follows v On Windows You can start LicenseServer via the Altova ServiceController which is available in the system tray First click Start All Programs Altova LicenseServer Altova ServiceController to start Altova ServiceController and display its icon in the system tray see screenshot below If you select the Run Altova ServiceController at Startup option Altova ServiceController will start up on system start and its icon will be available in the system tray from then onwards GB Altova FlowForce Server gt EJ Altova FlowForce Web gt N Altova LicenseServer la W Altova MobileTogether Server gt Start service Altova RaptorXML XBRL Server gt Stop service Exit Altova ServiceController Run Altova ServiceController at startup A i 1 11 00 AM To start LicenseServer click the Altova ServiceController icon in the system tray hover over Altova LicenseServer in the menu that pops up see screenshot above and then select Start Service from the LicenseServer submenu If LicenseServer is already running the Start Service option will be disabled To stop LicenseServer select Stop Service from the LicenseServe
40. license can be used for only one client machine at a time even if the license has unused licensing capacity For example if a 10 core license is used for a client machine that has 6 CPU cores then the remaining 4 cores of licensing capacity cannot be used simultaneously for another client machine MobileTogether Server licenses Two types of MobileTogether Server license are available Customers can select a license type that best suits their requirements e Core licenses These are assigned to MobileTogether Servers on the basis of the cores on the server machine see the explanation above An unlimited number of MobileTogether Client devices can then connect to the server e User licenses These specify the maximum number of users MobileTogether Client devices that are allowed to connect to the MobileTogether Server at one time 2015 Altova GmbH Altova MobileTogether Server 20 Setting Up MobileTogether Server Setup on Linux 3 2 Setup on Linux This section describes the installation and licensing of MobileTogether Server on Linux systems Debian Ubuntu CentOS RedHat Installation on Linux e System requirements Uninstall old versions of Altova server products Download the Linux package Install MobileTogether Server Altova LicenseServer LicenseServer versions Trial license Licensing on Linux e Start LicenseServer e Start MobileTogether Server e Register MobileTogether Server e Assign a license Notes about Env
41. license file now and check that the license you want is active If you have already done this carry on to the next step Assign Licenses 2 Assign a license to your Altova product that has been registered with the LicenseServer Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer How to Assign Licenses 159 Register RaptorXML XBRL Server This section e Registering RaptorxML XBRL Server Windows e Registering RaptorxML XBRL Server Linux e Next steps RaptorXML XBRL Server must be installed on the server machine or network to which LicenseServer is connected and then be started as a servce It must then be registered with LicenseServer Only after registration can a license be assigned to it from LicenseServer This section describes how to register RaptorxML XBRL Server with LicenseServer Registering RaptorXML XBRL Server Windows You can register RaptorXVML XBRL Server via its command line interface CLI by using the licenseserver command RaptorXML Server RaptorXML licenseserver Server Or IP Address RaptorXML XBRL RaptorXMLXBRL licenseserver Server Or IP Address Server For example if LicenseServer is running on http localhost 8088 then register RaptorXML XBRL Server with RaptorXML Server RaptorxXML licenseserver localhost RaptorXML XBRL RaptorXMLXBRL licenseserver localhost Server After successfully registering RaptorxML XBRL Server you can go to LicenseServer and assign a
42. license to RaptorXML XBRL Server How to do this is described in the section Assign Licenses to Registered Products Registering RaptorXML XBRL Server Linux On Linux machines RaptorXML XBRL Server can be registered with LicenseServer by using the licenseserver command of the RaptorXML XBRL Server CLI Note that RaptorXML XBRL Server must be started with root rights sudo opt Altova RaptorxXMLServer2016 bin raptorxmlserver licenseserver localhost 2015 Altova GmbH Altova MobileTogether Server 160 Altova LicenseServer How to Assign Licenses sudo opt Altova RaptorXMLXBRLServer2016 bin raptorxmlxbrlserver licenseserver localhost In the command above localhost is the name of the server on which LicenseServer is installed Notice also that the location of the RaptorXML XBRL Server executable is opt Altova RaptorxXMLServer2016 bin opt Altova RaptorXMLXBRLServer2016 bin After successfully registering RaptorxML XBRL Server you can go to LicenseServer and assign a license to RaptorXML XBRL Server How to do this is described in the section Assign Licenses to Registered Products Next Steps After you have registered your Altova product with LicenseServer do the following 1 If you have not already uploaded your license file s to the LicenseServer see previous section Upload the license s upload the license file now and check that the license you want is active If you have already done this carry on to
43. name and password v Assigning roles to a user Roles can be assigned to a user on the user s Properties page To access the user s Properties page click the user name in the Users and Roles Users tab At the bottom of the user s Properties page is the Assigned Roles pane screenshot below Assigned Roles Roles available Roles assigned to the user Tech 01 a r a Name Assign gt gt Name m a workflow designer m B all 2 workflow user lt lt Remove amp authenticated All available roles are listed on the left All roles assigned to the user are listed on the right Select the available role in the list on the left that you want to assign and click Assign To remove an assigned role select it in the list on the right and click Remove To see a listing of all the privileges of a user go to Users and Roles Reports Privileges by User v Deleting a user A user can be deleted by root user or any user that has the Maintain users roles and privileges privilege Delete a user as follows In the Users and Roles Users tab select the user s you want to delete see screenshot below click Delete Selected Users 2015 Altova GmbH Altova MobileTogether Server 82 Web Ul Reference Users and Roles A anonymous amp root Delete Selected Users Altova MobileTogether Server 2015 Altova GmbH Web Ul Reference Users and Roles 83 Roles A role defines a set of privileges It can be assigne
44. on other users File based databases File based databases such as SQLite databases must reside in the folder defined in the Settings tab of MobileTogether Server as the Server Side s Solutions Working Directory By default this folder is var Altova MobileTogetherServer SolutionFiles JDBC Connections Note the following points e The Java Runtime Environment or SDK must be installed e The JDBC Connects for the target database must be installed e The following environment variables must be set correctly for your environment o CLASSPATH to find the jar files o PATH to find the JRE but might not be necessary depending on the installation o JAVA_HOME if necessary depending on the installation Note On Mac OS Xservers the only database connections supported are JDBC Altova MobileTogether Server 2015 Altova GmbH Setting Up MobileTogether Server Setup on Mac OSX 37 Listing of important files The Plist file is installed in the Library LaunchDaemons folder The parts highlighted in blue are environment specific and will need to be adjusted to match your environment Plist file lt xml version 1 0 encoding UTF 8 gt lt DOCTYPE plist PUBLIC Apple DTD PLIST 1 0 EN http www apple com DTDs PropertyList 1 0 dtd gt lt plist version 1 0 gt dict gt lt key gt Label lt key gt lt string gt com altova MobileTogetherServer lt string gt lt key gt ProgramArguments lt key gt
45. products as sub packages registering FlowForce Server will automatically also register the Altova server products After successfully 2015 Altova GmbH Altova MobileTogether Server 154 Altova LicenseServer How to Assign Licenses registering FlowForce Server you can go to LicenseServer and assign a license to FlowForce Server How to do this is described in the section Assign Licenses to Registered Products Registering FlowForce Server via the FlowForce CLI Linux On Linux machines FlowForce Server can be registered with LicenseServer by using the licenseserver command of the FlowForce Server CLI Note that FlowForce Server must be started with root rights sudo opt Altova FlowForceServer2016 bin flowforceserver licenseserver localhost In the command above localhost is the name of the server on which LicenseServer is installed Notice also that the location of the FlowForce Server executable is opt Altova MapForceServer2016 bin After successfully registering FlowForce Server you can go to LicenseServer and assign a license to FlowForce Server How to do this is described in the section Assign Licenses to Registered Products Next Steps After you have registered your Altova product with LicenseServer do the following 1 If you have not already uploaded your license file s to the LicenseServer see previous section Upload the license s upload the license file now and check that the license you want is active If you
46. resourcestrings command mobiletogetherserver exportresourcestrings de c Strings xml This command creates a file called strings xm1 at c that contains all the resource strings of the MobileTogether Server application in German v Casing on the command line MobileTogetherServer on Windows mobiletogetherserver on Unix Linux Mac Note that lowercase mobiletogetherserver works on all platforms Windows Linux and Mac while upper lower MobileTogetherServer works only on Windows and Mac Creating localized versions of MobileTogether Server You can create a localized version of MobileTogether Server for any language of your choice Five localized versions English German Spanish French and Japanese are already available in the C Program Files x86 Altova MobileTogetherServer2 0 bin folder and therefore do not need to be created Create a localized version as follows 1 Generate an XML file containing the resource strings by using the xportresourcestrings command see command syntax above The resource strings in this XML file will be one of the five supported languages English en German de Spanish es French fr or Japanese ja according to the LanguageCode argument used with the command 2 Translate the resource strings from one of the four supported languages into the target language The resource strings are the contents of the lt string gt elements in the XML file Do not translate variables
47. that the location of the MobileTogether Server executable is opt Altova MobileTogetherServer2 0 bin e the Settings tab of MobileTogether Server s Web UI Essentially i Start MobileTogether Server via ServiceController see previous point ii Enter your password to access the Setup page iii Select the LicenseServer name or address and click Register with LicenseServer After successful registration go to the Server Management tab of LicenseServer s configuration page to assign a license to MobileTogether Server v Assign a license After successfully registering MobileTogether Server it will be listed in the Server Management tab of the configuration page of LicenseServer Go there and assign a license to MobileTogether Server Note on cores and licenses The licensing of Altova server products is based on the number of processor cores available on the product machine for MobileTogether Server an additional licensing option is available see below For example a dual core processor has two cores a quad core processor four cores a hexa core processor six cores and so on The number of cores licensed for a product must be greater than or equal to the number of cores available on that server machine whether the server is a physical or virtual machine For example if a server has eight cores an octa core processor you must purchase at least one 8 core license You can also combine licenses to achieve the core count So
48. the address and port of the MobileTogether Server to which to deploy designs Altova MobileTogether Server 2015 Altova GmbH Web UI Reference Settings 97 Administrator ports Select unsecure HTTP and secure HTTPS ports to be used by the administrator These ports can be used for server configuration user role and user license administration workflow deployment and workflow simulation Specify a hostname when you intend to open the administration page from Altova ServiceController This avoids browser warnings about the certificate not matching the URL E HTTP Port 8085 W HTTPS Port 8086 Hostname myhost altova com The HTTP port is the unsecure port HTTPS is the secure port To use HTTPS you need to set up SSL Encryption If you set up the HTTPS port and wish to avoid browser warnings about the SSL certificate not matching the URL then specify the hostname of the computer on which the MobileTogether Server configuration page will be opened v SSL certificates Specifies the private key certificate and public key certificate to use for SSL communication Click Browse and select the files containing the certificates Private Key for private key and Certificate for public key See Setting Up SSL Encryption for more information SSL certificates Select the private key and the certificate needed for secure SSL communication A valid private key and certificate must be supplied in order to us
49. the user s access rights are determined by the user s privileges Privileges are assigned to the user either directly or via roles in the Users and Roles tab SS Privileges Maintain users roles and privileges Set own password v vi W Override security V Allow to use stored password on client do not require authentication on application start v View unfiltered log View cache overview S View user licenses overview E Read users and roles lt Manage server settings Trace workflow Enables detailed workflow execution logging to files including working XML files when the Logging to File option is enabled Read global resources Y Write global resources Save workflow from designer v v v Open workflow from designer v v VY Run server simulation The available privileges are described below Maintain users roles and privileges Any user having this privilege can create delete and edit users and roles their privilege assignments and passwords This is an administrative privilege and should only be assigned to MobileTogether administrators By default only the user root possesses this privilege a Set own password Any user having this privilege can change his own password Users who do not have this privilege need to have their password set by a MobileTogether administrator By default the authenticated role and hence every user account except anonymous
50. to be licensed to run that product on that client If the number of licensed cores is less than the number required then the information is marked in red see screenshot above The number of CPU cores that need to be licensed is the number of CPU cores on that client and is obtained from the client machine by LicenseServer If multiple versions of a single product for example StyleVision Server 2013 and StyleVision Server 2014 have been installed on one machine and if each of these installations has been registered with a single LicenseServer then the multiple registrations are consolidated in a single registration in the Server Management tab and displayed as a single registration When a license is assigned to this single registration 2015 Altova GmbH Altova MobileTogether Server 164 Altova LicenseServer How to Assign Licenses all the installations indicated by that registration will be licensed However multiple instances of only one installation can be run simultaneously on the client machine For example multiple instances of StyleVision Server 2013 or multiple instances of StyleVision Server 2014 can be run simultaneously but not one instance of StyleVision Server 2013 and one instance of StyleVision Server 2014 Note that newly installed versions must be registered for them to run e New versions of Altova server products can only be licensed with the latest version of LicenseServer at the time of the product s release Older A
51. to the Applications folder in Finder and double clicking the MobileTogether Server icon there v Altova LicenseServer In order for any Altova Server product including MobileTogether Server to run that server product must be licensed via an Altova LicenseServer on your network The Altova LicenseServer installation package is available on the virtual drive you have mounted in the previous step To install Altova LicenseServer double click the installer package included on the virtual drive and follow the on screen instructions You will need to accept the license agreement for installation to proceed Altova LicenseServer can also be downloaded and installed separately from the Altova website http www altova com download html The LicenseServer package will be installed in the folder 2015 Altova GmbH Altova MobileTogether Server 32 Setting Up MobileTogether Server Setup on Mac OS X usr local Altova LicenseServer For information about how to register MobileTogether Server with Altova LicenseServer and license it see the section Licensing on Mac OS X v LicenseServer versions Altova server products must be licensed either with the version of LicenseServer that is appropriate to the installed MobileTogether Server version or with a later version of LicenseServer The LicenseServer version that is appropriate for a particular version of MobileTogether Server is displayed during the installation of MobileTogether Server
52. username and password The default username password iS root root lf Active Directory Login via one or more domains has been defined then a Login combo box is available in which you can i select from among the defined domains or ii choose to login directly not via a domain v On Linux To access the Web UI enter its URL in the address bar of a browser and press Enter By default the URL of the Web UI page for administrative access is To sign in enter the username and password The default username password iS root root If Active Directory Login via one or more domains has been defined then a Login combo box is available in which you can i select from among the defined domains or ii choose to login directly not via a domain v On Mac OS X Altova MobileTogether Server 2015 Altova GmbH Web UI Reference 69 To access the Web UI enter its URL in the address bar of a browser and press Enter By default the URL of the Web UI page for administrative access is To sign in enter the username and password The default username password iS root root lf Active Directory Login via one or more domains has been defined then a Login combo box is available in which you can i select from among the defined domains or ii choose to login directly not via a domain Web UI tabs The Web Ul is the administrator interface of MobileTogether Server The various administrative functions are available in the following W
53. usually open on most firewalls by default So if you are having difficulties with firewall settings and if port 80 is not already bound to some other service you could specify port 80 as the MobileTogether Server port for client communication Altova MobileTogether Server 2015 Altova GmbH Chapter 3 Setting Up MobileTogether Server 12 Setting Up MobileTogether Server 3 Setting Up MobileTogether Server This section describes installation licensing and other setup procedures It is organized into the following sections Setup on Windows Setup on Linux Setup on Mac OS X Setting Up SSL Encryption Altova MobileTogether Server 2015 Altova GmbH Setting Up MobileTogether Server Setup on Windows 13 3 1 Setup on Windows This section describes the installation and licensing of MobileTogether Server on Windows systems Installation on Windows e System requirements Installing MobileTogether Server Altova LicenseServer LicenseServer versions Trial license Application folder location Licensing on Windows e Start ServiceController Start LicenseServer Start MobileTogether Server Register MobileTogether Server Assign a license 2015 Altova GmbH Altova MobileTogether Server 14 Setting Up MobileTogether Server Setup on Windows Installation on Windows MobileTogether Server is available for installation on Windows systems Its installation and setup procedure is described below v System requirements v
54. which is denoted by the character Co ntai ner Type here to search Search E Recursive Global Resource Persistent Name A s Description i ss pp App ver npt Version Last Deployed on Configuration Data Run in Browser O contacts C public Permissions Permissions Create Container Permissions v Functionality The buttons of the tab provide the following functionality Create Container Creates a container in the current folder Click a container to open it Saves changes such as a modification of descriptions elete Selected Deletes the selected container or file Permissions Sets which users roles can access individual containers and their level of access Search Searches for the term submitted Check Recursive to search in descendant containers Other available actions e To navigate up the container hierarchy click the required ancestor folder in the path at the top of the Workflows tab e To navigate down the container hierarchy click a container to open it e Click a solution file s URL to run the solution v The container public Clicking the public container opens the container and displays its contents public is a predefined container containing sample design files Solutions that are delivered with the program Click a solution s URL to run it Altova Mobile Together Server 2015 Altova GmbH Web Ul Reference Workflows 71 Workflows Users and Roles Userlicenses Lo
55. 015 Altova GmbH Command Line Usage assignlicense Windows only 109 MobileTogetherServer on Windows mobiletogetherserver on Unix Linux Mac Note that lowercase mobiletogetherserver works on all platforms Windows Linux and Mac while upper lower Mobi leTogetherServer works only on Windows and Mac Command options Options are listed in their short forms in the first column and long forms second column together with their descriptions third column On the command line one or two dashes can be used for both short and long forms Values are true false If true then the license file is only uploaded to LicenseServer and validated It is not assigned to MobileTogether Server Form test only true false Set to true if the option is specified without a value 2015 Altova GmbH Altova MobileTogether Server 110 Command Line Usage verifylicense Windows only 6 3 verifylicense Windows only This section e Command syntax e Command description e Examples e Command options Command syntax Windows MobileTogetherServer verifylicense options Note This command is supported only on Windows systems It is not supported on Linux or Mac systems Command description Checks whether the current product is licensed Additionally the 1icense key option enables you to check whether a specific license key is already assigned to the product For details about licensing see the LicenseServer docu
56. 68 opening on Linux 141 opening on Mac OS X 143 opening on Windows 138 2015 Altova GmbH 189 URL of 138 URL of Linux 141 URL of Mac OS X 143 D Default password 138 E Encryption 49 exportresourcestrings command 117 F FlowForce Server registering with LicenseServer 150 H help command 121 Host settings 96 HTTP and HTTPS ports for mobile clients 96 for server administrators 96 Installation on Linux 21 Installation on Mac OS X 30 Installation on Windows 14 L License Pool 145 169 Licenses assigning 162 174 uploading 145 169 190 LicenseServer Configuration page 168 connection settings 96 installation on Mac OS X 133 installation on Windows 129 131 interface with 168 registering FlowForce Server with 150 registering MapForce Server with 155 registering StyleVision Server with 157 registering with 96 see Altova LicenseServer 45 settings 180 starting 136 steps for assigning licenses 135 licenseserver command 106 LicenseServer configuration page see Configuration page 138 141 143 Licensing on Linux 24 Licensing on Mac OS X 33 Licensing on Windows 16 Linux installation on 21 licensing on 24 Localization 117 119 Log of server actions 92 Log settings 96 Logout 186 Mac OS X installation on 30 licensing on 33 MapForce Server registering with LicenseServer 155 Messages 186 Mobile client ports 54 96 Mobile clients
57. If LicenseServer is not installed go ahead with the installation as documented in the next steps If LicenseServer is installed and you wish to install a newer version of it uninstall the old version with the command Debian Ubuntu sudo dpkg remove licenseserver CentOS RedHat sudo rpm e licenseserver Installing Altova LicenseServer On Linux systems LicenseServer must be installed independently of other Altova server products It is not included as part of the installation packages of Altova server products Download Altova LicenseServer from the Altova website and copy the package to any directory on the Linux system Distribution Installer extension Debian Ubuntu CentOS RedHat 2015 Altova GmbH Altova MobileTogether Server 132 Altova LicenseServer Installation Linux In a terminal window switch to the directory where you have copied the Linux package For example if you copied it to a user directory called MyAltova that is located say in the home User directory then switch to this directory as follows cd home User MyAltova Install LicenseServer with the following command Debian sudo dpkg install licenseserver 1 23 debian deb Ubuntu sudo dpkg install licenseserver 1 23 ubuntu deb CentOS sudo rpm ivh licenseserver 1 23 1 x86_64 rpm RedHat sudo rpm ivh licenseserver 1 23 1 x86_64 rpm The LicenseServer package will be installed in opt Altova LicenseServer For information
58. LI Note that MapForce Server must be started with root rights sudo opt Altova MapForceServer2016 bin mapforceserver licenseserver localhost In the command above localhost is the name of the server on which LicenseServer is installed Notice also that the location of the MapForce Server executable is opt Altova MapForceServer2016 bin After successfully registering MapForce Server you can go to LicenseServer and assign a license to MapForce Server How to do this is described in the section Assign Licenses to Registered Products Next Steps After you have registered your Altova product with LicenseServer do the following 1 If you have not already uploaded your license file s to the LicenseServer see previous section Upload the license s upload the license file now and check that the license you want is active If you have already done this carry on to the next step Assign Licenses 2 Assign a license to your Altova product that has been registered with the LicenseServer Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer How to Assign Licenses 157 Register StyleVision Server This section Registering StyleVision Server from FlowForce Server Windows Registering a standalone StyleVision Server Windows Registering StyleVision Server Linux Next steps StyleVision Server can be installed as part of the FlowForce Server package or as a standalone server product In either case it must be regis
59. LicenseServer settings specify the LicenseServer machine to connect to and enables you to register MobileTogether Server with LicenseServer See the section Setting Up MobileTogether Server for information about licensing 2015 Altova GmbH Altova MobileTogether Server 102 Web UI Reference Settings LicenseServer Host 127 0 0 1 v Server is registered with LicenseServer and license is acquired e To search for LicenseServers on your network click the Search button The detected LicenseSereers are listed in the dropdown list of the combo box From this list select the LicenseServer that you wish to connect to e To enter a server address click the Address button and enter the server address When the LicenseSerer is found Register with LicenseServer becomes enabled Click the button to register MobileTogether Server with LicenseServer Click Acquire License to go to LicenseServer and assign a license to MobileTogether Server Altova MobileTogether Server 2015 Altova GmbH Chapter 6 Command Line Usage 104 Command Line Usage 6 Command Line Usage This section e Default location of MobileTogether Server executable e Usage and list of CLI commands Default location of MobileTogether Server executable Given below are the default locations of the MobileTogether Server executable Windows lt ProgramFilesFolder gt Altova MobileTogetherServer2 0 bin MobileTogetherServer exe Linux opt Altova MobileTo
60. M v Start LicenseServer To start LicenseServer click the ServiceController icon in the system tray hover over Altova LicenseServer in the menu that pops up see screenshot below and then select Start Service from the LicenseServer submenu If LicenseServer is already running the Start Service option will be disabled Altova FlowForce Server gt BD Altova FlowForce Web gt TN Altova LicenseServer E I Altova MobileTogether Server gt Start service Altova RaptorXML XBRL Server gt Stop service Exit Altova ServiceController Run Altova ServiceController at startup A ra D 11 00 AM v Start MobileTogether Server To start MobileTogether Server click the ServiceController icon in the system tray hover over Altova MobileTogether Server in the menu that pops up see screenshot below and then select Start Service from the MobileTogether Server submenu If MobileTogether Server is already running the Start Service option will be disabled 2015 Altova GmbH Altova MobileTogether Server 18 Setting Up MobileTogether Server Setup on Windows BD Altova FlowForce Server BD Altova FlowForce Web Al Altova LicenseServer 4 Altova MobileTogether Server Altova RaptorXML XBRL Server gt i Start service Exit Altova ServiceController Stop service Run Altova ServiceController at startup EL a a p i gt 11 00 AM v Register MobileTogether Server Register MobileTogether Server through
61. Roles i attenere age sos eta TEE sede ta E bu pay AASER EATA a 56 4 6 Available Privileges oserei enaren opus ven Soe can E Ea e E EE E aaa Rs 59 4 7 Conhigure the Frewal sroti nirre verity E EE A E E a EaR 62 4 8 Information for Clients eese errasse iaa oar ei earr ENa Eene E Taaa ia ER 63 4 9 How to Back Up and Restore MobileTogether Server eeesereeresesrerrereesressseee 64 4 10 Frequently Asked Questions sssssesseeeesessesssesersessssssertreesssssstrreeesessssesreereesssseseee 66 Altova Mobile Together Server 5 Web UI Reference 68 Sl Worktlows wiuanisiend anid anlerddanidnideniaidaniaenddas 70 o 2 Wsers and Role sts i sss 3 iesiet ett roses Savio ieee E ine da eh ee ese eet eedes dss 75 S2 USET Senne a eara E a E e ARa N aaa Raa o aS 78 S22 ROES aeee a E a aR ante E MORO a ant satis 83 3 2 3 PassWord POlCie vrsne anene innen aer E aE EEE EEEE aE Nio 87 D2 Reponse ae sit eet a a E setae es Pee 89 5 3 User TEIGENSES ennea ie Sia tite elds eee a See ee ioe eee Sled 90 DA LOB eds sete EE E EE E AT oa saad odeBe cna vege nag cba dee tes E gctnetieaes Bene 92 DD Caches ch aes hee e a E a a a Tt a n ea ot 94 Eo E E T E EE E E T E E evevcsst 96 6 Command Line Usage 104 Ol wliCENSESELVER ao OE A AEE AE A Re EES 106 6 2 assignlicense Windows only ssssseeeseessesssesrreessssssesreerssssssssrrereessssesesreeesesseseseee 108 6 3 verifylicense Windows only eseessseseessesssssrrrrssssssrsreersssssss
62. Server2 0 etc tool usr local Altova FlowForceServer2016 tools This command copies the tool file from ete directory of MobileTogether Server to the FlowForce Server tools directory The tool file is required by FlowForce Server it contains the path to the MobileTogether Server executable You do not need to run this command if you install FlowForce Server before installing MobileTogether Server v Uninstall old versions of Altova server products Before uninstalling MobileTogether Server stop the service with the following command sudo launchctl unload Library LaunchDaemons com altova MobileTogetherServer2 0 plist To check whether the service has been stopped open the Activity Monitor in Finder and make sure that MobileTogether Server is not in the list In the Applications folder in Finder right click the MobileTogether Server icon and select Move to Trash The application will be moved to Trash You will however still need to remove the application from the usr folder Do this with the command sudo rm rf usr local Altova MobileTogetherServer2 0 If you need to uninstall an old version of Altova LicenseServer you must first stop it running as a service Do this with the following command Altova MobileTogether Server 2015 Altova GmbH Setting Up MobileTogether Server Setup on Mac OSX 31 sudo launchctl unload Library LaunchDaemons com altova LicenseServer plist To check whether the service has been stopped ope
63. User and Reference Manual ALTOVA Lt MobileTogether Altova MobileT ogether Server User amp Reference Manual All rights reserved No parts of this work may be reproduced in any form or by any means graphic electronic or mechanical including photocopying recording taping or information storage and retrieval systems without the written permission of the publisher Products that are referred to in this document may be either trademarks and or registered trademarks of the respective owners The publisher and the author make no claim to these trademarks While every precaution has been taken in the preparation of this document the publisher and the author assume no responsibility for errors or omissions or for damages resulting from the use of information contained in this document or from the use of programs and source code that may accompany it In no event shall the publisher and the author be liable for any loss of profit or any other commercial damage caused or alleged to have been caused directly or indirectly by this document Published 2015 2015 Altova GmbH Table of Contents 1 Altova MobileTogether Server 3 2 introduction 6 2 1 MobileTogether Overview soeieto iaeaea eeii eeke ieaie aea eA 7 2 2 Using MobileTogether Server ce eeeeeeessncecececeeeesesnaeeeceeeceesesecaeceeeeeeeseeseaneaeeees 9 3 Setting Up MobileTogether Server 12 31 Setup On WiIndOWS onean anea ress suscbengecdasoesouvesseqe
64. Windows Windows XP SP2 for x64 SP3 for x86 Windows Vista Windows 7 Windows 8 Windows 10 v Windows Server Windows Server 2008 R2 or newer v Installing MobileTogether Server MobileTogether Server can be installed on Windows systems as follows e As a separate standalone server product called MobileTogether Server To install MobileTogether Server download and run the MobileTogether Server installer Follow the onscreen instructions The installers of both MobileTogether Server and FlowForce Server are available at the Altova website and will install the products with the necessary registrations After installation the MobileTogether Server executable will be located by default at lt ProgramFilesFolder gt Altova MobileTogetherServer2 0 bin MobileTogetherServer exe v Altova LicenseServer e In order for MobileTogether Server to work it must be licensed via an Altova LicenseServer on your network e When you install MobileTogether Server on Windows systems an option is available that allows you to download and install Altova LicenseServer together with MobileTogether Server e If an Altova LicenseServer is already installed on your network you do not need to install another one unless a newer version of Altova LicenseServer is required See next point LicenseServer versions e During the installation process of MobileTogether Server check or uncheck the option for installing Altova LicenseServer as appropriate
65. a GmbH Altova MobileTogether Server 142 Altova LicenseServer How to Assign Licenses ALTOVA LicenseServer Please enter password to log in Initial password is default essee Setting a fixed or dynamic port for the Configuration page The port of the Configuration page Web Ul and consequently its address can be specified in the Settings page By default the port is 8088 You can set any other port you want for the LicenseServer Configuration page see screenshot below Alternatively you allow the port to be selected dynamically each time LicenseServer starts up In this case you will need to find out the URL of the Configuration page from the file webuI htm1 see Open LicenseServer Config Page Windows and Open LicenseServer Config Page Linux Web UI Changing these settings will cause the LicenseServer to restart and any currently running and licensed applications will be shut down Configure the host addresses where the web UI is available to administrators All interfaces and assigned IP addresses Only the following hostname or IP address 0 0 0 0 Ensure this hostname or IP address exists or LicenseServer will fail to start Configure the port used for the web UI 5D Dynamically chosen by the operating system Fixed port 8088 Ensure this port is available or LicenseServer will fail to start The advantage of a fixed port is that the page URL is known in advance and therefore can be ac
66. a data source in the Page Sources window select Cache Settings and specify the properties of the cache There are two main reasons to create caches i If a page data source generates reports slowly for example a large database ii If a data source is not modified often In such cases execution of a solution would be faster if data is taken from data caches on the server In order to keep caches up to date the frequency of cache updates can be specified when the cache is created Once a cache has been defined in MobileTogether Designer it can be used by the data sources of different designs providing the underlying data structure is compatible If a data source is defined as having a cache the cached data will be used when the solution is run Caches can be used as soon as the solution has been deployed to the server Details displayed and available actions In the Cache tab you can see all caches available on the server activate or deactivate individual caches save any change to the active inactive status of a cache and delete selected caches Cache Overview Name Max Cache Entries Total Cache Size Active V gt NEW_CACHE 1 OKB E Save Delete Selected e Name Names are given at the time a cache is defined in MobileTogether Designer and cannot be changed in MobileTogether Server The same cache can be used in multiple designs if the referenced data structure is compatible Assigning caches to different designs is done
67. about how to proceed with assigning licenses see the section How to Assign Licenses v LicenseServer versions and their compatibility with Altova server products New versions of Altova server products can only be licensed with the version of LicenseServer that is the latest at the time of the server product s release However older versions of Altova server products will work with newer versions of LicenseServer So if you are installing a new version of an Altova server product and if your current LicenseServer version is not the latest de install this older version and install the latest version available on the Altova website All registration and licensing information held in your older version of LicenseServer will be saved at the time of de installation to a database on your server machine and will be imported automatically into the newer version When you install a newer version of LicenseServer the older version will be de installed before the newer version is installed The version number of the currently installed LicenseServer is given at the bottom of the LicenseServer configuration page all tabs Current version 1 23 Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer Installation Mac OS X 133 7 4 Installation Mac OS X Altova LicenseServer can be installed on Mac OS X systems version 10 8 or higher Since you might need to uninstall a previous version uninstalling is described first Sys
68. achine MobileTogether Server licenses Two types of MobileTogether Server license are available Customers can select a license type that best suits their requirements e Core licenses These are assigned to MobileTogether Servers on the basis of the cores on the server machine see the explanation above An unlimited number of MobileTogether Client devices can then connect to the server e User licenses These specify the maximum number of users MobileTogether Client devices that are allowed to connect to the MobileTogether Server at one time Assigning a license To assign a license to a registered product click the Edit Assigned Licenses button of that product This pops up the Manage Licenses dialog screenshot below Manage licenses Altova RaptorXML XBRL Server DOC altova com Requires licenses for 2 CPU cores Max licensed CPU cores 16 Available licenses i CPU Cores License Type Key Code Expires in days SMP days left W 16 Cores M2LOCMY W78MPXJ A8H3C40 589 Apply Changes Go to License Pool Note the following points about the licenses displayed in the Manage Licenses dialog e The product to be licensed is listed at the top left of the dialog In the screenshot above 2015 Altova GmbH Altova MobileTogether Server 166 Altova LicenseServer How to Assign Licenses the product is Altova RaptorXML XBRL Server e The machine on which the server is installed Doc altova com in the screenshot above is listed
69. age in the address bar of an Internet browser http lt serverIPAddressOrName gt 8085 Firewall Note Make sure that the port address is not blocked by your firewall v Register MobileTogether Server 2015 Altova GmbH Altova MobileTogether Server 34 Setting Up MobileTogether Server Setup on Mac OS X Register MobileTogether Server via e its CLI using the licenseserver command sudo usr local Altova MobileTogetherServer2 0 bin MobileTogetherServer licenseserver options ServerName Or IP Address For example if localhost is the name of the server on which LicenseServer is installed sudo usr local Altova MobileTogetherServer2 0 bin MobileTogetherServer licenseserver localhost In the command above localhost is the name of the server on which LicenseServer is installed Notice also that the location of the MobileTogether Server executable is usr local Altova MobileTogetherServer2 0 bin e the Settings tab of MobileTogether Server s Web UI Essentially i Start MobileTogether Server via ServiceController see previous point ii Enter your password to access the Setup page iii Select the LicenseServer name or address and click Register with LicenseServer After successful registration go to the Server Management tab of LicenseServer s configuration page to assign a license to MobileTogether Server v Assign a license After successfully registering MobileTogether Server it will be listed in the Server Manage
70. age will be http lt serverIPAddressOrName gt 8088 The URL is present in the HTML code of the Configuration page itself which is named webUI html and is located at var opt Altova LicenseServer webUI html If you have set the URL of the Configuration page to be generated dynamically in the Settings tab of the Configuration page then a new URL is generated each time LicenseServer is started You will need to check the current version of webUI htm1 to find out the current URL of the Configuration page The dynamically generated URL in webu htm1 will have a form something like http 127 0 0 1 55541 and it is located in the function checkIfServiceRunning ina script near the end of the lt head gt element While the port number in the URL is dynamically assigned the IP address part identifies the server on which LicenseServer has been installed If you wish to access the LicenseServer Configuration page from another machine make sure that the IP address part of the URL has the correct IP address or name of the server on which LicenseServer has been installed For example the URL could be something like http MyServer 55541 Logging in with the initial password After going through the steps above the Configuration page is opened with the login mask displayed screenshot below You can log in with the initial password of default After you have logged in you can change your password in the Settings tab 2015 Altov
71. all privileges and having the ability to add other users and to set roles Its initial name password combination is root root The password can be changed at any time 2015 Altova GmbH Altova MobileTogether Server 76 Web Ul Reference Users and Roles anonymous anonymous is an account for anonymous users that access services exposed via the HTTP serice interface It cannot be used for logging in top the Web UI and it has no initial password v About Privileges A privilege is an activity that a user is allowed to carry out There is a fixed number of MobileTogether Server privileges and a user can be assigned zero to all of the available privileges It is however good practice to assign privileges via roles see next section rather than to assign privileges directly to the user The assigning of privileges and roles to a user is done by a user that has been assigned this privilege Initially it is root user that has this privilege The screenshot below shows all the available privileges Privileges V Maintain users roles and privileges V Set own password V Override security V Allow to use stored password on client do not require authentication on application start View unfiltered log V View cache overview V View user licenses overview V Read users and roles Manage server settings Trace workflow Enables detailed workflow execution logging to files including working XML files whe
72. all the users roles that have that privilege v About Roles A role defines a set of privileges It can be assigned to another role or to a user A role s privileges automatically become the privileges of any other role or any user that the role is assigned to A user can be assigned any number of roles As a result a user will have all the privileges defined in the multiple assigned roles The following roles are predefined e authenticated is automatically assigned to every user except anonymous So user with a name and password is assigned the authenticated role e allis automatically assigned to every user including anonymous e workflow designer is assigned to users that design workflows in MobileTogether Designer This role allows a user to open and save workflows as well as to runa simulation on the server e workflow user is assigned to users running the workflow on a mobile device This role allows the user to access the servce interface without needing to log in to the server and start the solution on the client 2015 Altova GmbH Altova MobileTogether Server 58 Server Procedures Users and Roles Altova MobileTogether Server 2015 Altova GmbH Server Procedures Available Privileges 59 4 6 Available Privileges Privileges themselves are access rights to the various administrative functions and services of MobileTogether Server When a user logs in to MobileTogether Server either via its Web UI or services interface
73. and displays the version number of MobileTogether Server and exits The command takes no options Examples Examples of the version command mobiletogetherserver version v Casing on the command line MobileTogetherServer on Windows mobiletogetherserver on Unix Linux Mac Note that lowercase mobiletogetherserver works on all platforms Windows Linux and Mac while upper lower MobileTogetherServer works only on Windows and Mac 2015 Altova GmbH Altova MobileTogether Server Chapter 7 Altova LicenseServer 126 Altova LicenseServer Altova LicenseServer Altova LicenseServer hereafter also called LicenseServer for short provides a central location for the management of licenses for Altova products Altova applications running in a network can have licenses assigned to them from the LicenseServer thus giving administrators the flexibility to manage and monitor licenses Current version 1 23 Licensing process with Altova LicenseServer To assign an Altova server product a license via Altova LicenseServer you need to do the following 1 Start LicenseServer 2 Open the LicenseServer Configuration page which is the Web UI of LicenseServer on Windows Linux or Mac OS X 3 Upload the license s you have received from Altova to LicenseServer Do this in the License Pool tab of the Configuration page 4 Register Altova server products FlowForce Server MapForce Server StyleVision Server RaptorXML XBRL
74. any spaces for example hostnamel IPAddress1 hostname2 The port number of the service is fixed at 35355 The default settings allow unrestricted access to LicenseServer and its configuration page from 2015 Altova GmbH Altova MobileTogether Server 184 Altova LicenseServer Configuration Page Reference within the networks to which LicenseServer is connected If you wish to restrict access to either LicenseServer or its configuration page enter the appropriate settings and click Save Run a connectivity test see above to check that the settings are correct Alert Mail settings Altova LicenseServer needs to be connected to the altova com server If the connection is broken for more than 24 5 hours 5 days LicenseServer will not allow licenses As a result work sessions with Altova products licensed by LicenseServer could be disrupted In order to alert the administrator that a connection is broken an alert mail can be sent to an email address The Alert Mail pane see screenshot below is where you enter settings for sending alert mails to an administrator s email address Alert Mail Configure email settings for communication with administrator SMTP Host 127 001 SMTP Ports User authentication myusername User password feesess ts From mylicserver altovacom To myadmin altova com Send Test Mail Miscellaneous E Show hint how to receive evaluation licenses for a server product Send a warning email
75. as from permissions directly assigned to the user e Inheritance rules for users take precedence over container hierarchy rules e f a permission is redefined for any role the user is a member of container hierarchy inheritance for this particular permission is overridden Permissions are checked for every user interaction A user can only successfully access and or edit when all required permissions are granted Permissions are set for the following groups Container e Read The user can list the contents and find an object in the container e Read Write Additional to read can create new and delete existing objects depending on other permissions that may apply Work flow e Read The user can run solutions e Read Write The user can additionally write to solution data To modify file data write access must also be granted for the container Security e Read The user is permitted to read the permission list of any child object of the container e Read Write The user can additionally change the permissions list of any child object of the container e By default a user is permitted to read only permissions assigned to it or a role itis a member of If the Read Users and Roles privilege is granted see Users and Roles users can read all permission entries Altova MobileTogether Server 2015 Altova GmbH Web Ul Reference Editing the permissions of a container 1 Click the Permissions button of the container This takes y
76. aster Licensing Server at altova com The Altova LicenseServer needs to be able to communicate with the Master Licensing Server at altova com to validate and authenticate license related data and to ensure continuous compliance with the Altova license agreements This communication occurs over HTTPS using port 443 If the Altova LicenseServer after making the initial verification with the altova com Master Licensing Server is unable to again connect with altova com for a duration of more than 5 days 120 hours then the Altova LicenseServer will no longer permit the usage of any Altova software products connected to the Altova LicenseServer Any such loss of connection with the altova com master servers will be logged in the Messages tab of the Configuration page of the Altova LicenseServer In addition the administrator can configure the Altova LicenseServer to automatically send an alert email when the connection to altova com is lost Alert Mail settings are available in the Settings tab of the Configuration page Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer Installation Windows 7 2 2015 Altova GmbH Installation Windows Altova LicenseServer can be installed on Windows systems in one of two ways e As an independent installation e As part of an Altova server product installation Altova server products are Altova FlowForce Server Altova MapForce Server Altova StyleVision Server Altova Rapt
77. ation go to the Server Management tab of LicenseServer s configuration page to assign a license to MobileTogether Server 2015 Altova GmbH Altova MobileTogether Server 162 Altova LicenseServer How to Assign Licenses Assign Licenses to Registered Products This section e Before assigning a license e The Server Management tab e Icons in the Server Management tab e Note on cores and licenses e Assigning a license e Unregistering products from LicenseServer Before assigning a license Before you assign a license to an Altova product make sure that e The relevant license has been uploaded to the license pool of LicenseServer and that the license is active e Your Altova product has been registered with LicenseServer The Server Management tab Licenses are assigned in the Server Management tab of the LicenseServer Configuration page screenshot below The screenshot shows that three Altova products have been registered with LicenseServer Since MapForce Server and StyleVision Server are bundled with FlowForce Server registering FlowForce Server with LicenseServer automatically also registers MapForce Server and StyleVision Server No additional registration of the latter two products are required if FlowForce Server is registered Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer How to Assign Licenses 163 ALTOVA LicenseServer DOC altova com Altova FlowForce Server 2014 This server
78. be edited o Show Licenses Appears with each license Switches to the License Pool tab and highlights the selected license so that license details can be read Unregister This Product Available with each product The selected product on the selected client machine will be unregistered from LicenseServer Assigning a license To assign a license to a registered product click the Edit Assigned Licenses button of that product This pops up the Manage Licenses dialog screenshot below 2015 Altova GmbH Altova MobileTogether Server 176 Altova LicenseServer Configuration Page Reference Manage licenses Altova RaptorXML XBRL Server DOC altova com Requires licenses for 2 CPU cores Max licensed CPU cores 16 Available licenses i CPU Cores License Type Key Code Expires in days SMP days left W 16 Cores M2LOCMY W78MPXJ A8H3 C40 589 Apply Changes Go to License Pool Select the license you wish to assign After selecting the license s click Apply Changes The license s will be assigned to that product and displayed in the Server Management tab see screenshot below This server has 2 CPU core s s BUMO9M6 X5XJW9A 8U999H5 9H6XL75 5L2AA11 85F8WM1 16 i Licenses for 2 CPU core s are required Limit to single thread execution Max licensed CPU cores 16 Note Licenses for Altova s MobileTogether Server are also issued on the basis of the number of users that is client devices that connect to the server
79. by clicking the Delete All button at the top of the tab or by defining a date range and clicking Delete Searching for log messages To access the Search dialog screenshot below click the Search button at the top or bottom left of the log table see screenshot above Altova MobileTogether Server 2015 Altova GmbH Web UI Reference Log 93 contains v 2014 06 10 equal v system Reset For each search rule select a field such as Date or User an operator Such as contains or equals and the value to search for Add a new search rule by clicking the Add Rule button Delete a search rule by clicking its Delete Rule button The a11 selector at the top specifies that the search condition is fulfilled only when all the search rules are individually fulfilled The any selector specifies that the search condition is fulfilled if any one search rule is fulfilled Click Find to start the search Click Reset to remove the search filter 2015 Altova GmbH Altova MobileTogether Server 94 Web Ul Reference Cache 5 5 Cache The Cache tab displays the details of caches that are currently available on the server A cache is a data file that is generated from a data source of a design at a given time In the Web UI of MobileTogether Server you can see details about the caches on the server activate deactivate caches and delete caches Creating caches A new cache is defined in MobileTogether Designer for a data source Right click
80. cds sueeguaeseetoctassseoses 13 3 1 1 Installation on WMdOW Sisse serere neato aeoea enaa aE R EE AAEE 14 3 1 2 Licensing on Windows eeeessssssssesereessssssrrrreesssssstrrreestssestsrreeeessssssrereees 16 3 2 Setup on LinUk seen ea n a a aa a a E Gan E OE a LA 20 3 2 1 Installation on Lm X eein ee eae E Eae op EERE Eai 21 3 221 Ticensme on Linkisin eo EEA EERE 24 3 2 3 Notes about Environment cccccceseecececececeeeaeaeaeaeaeaeaeaeaeaeaeaeaeaeaeaeaeas 27 3 3 Setup on Mac OSX wecsssiecssscsseectsssedevansicencasvegnouaceadeucerssecevseescuiceasstsousesbansedaanesests 29 3 3 1 Installation on Mac OS X ot o eee eaea E Aaea EEN ERREA RERE Se 30 3 3 2 Licensing on Mac OS X esessssserressssssrrrretsrsssserereeressssrsrreeeessssssrereees 33 3 3 3 Notes about Environment eesseesesseeeessssssrrrretssesssrrrreestssssrsrreeeessssssrrrrees 36 3 4 Setting Up SSL Encryption 20 0 eee ee seccccceceeeesesnaeceeeeeceeseneaaeaeeeeeeeseesennaaeeeeeeeeees 38 4 Server Procedures 44 4 1 Start Altova LicenseServer 2 02 ccccecccccccccccececececeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeess 45 4 2 Start MobileTogether Server 0 0 eeeesesececececeseesennececeeececeesssnaeeeeeeeeeseeeenneaeeees 47 4 3 Set Up SSL Encryption asses riie re sas caazectategs cdvesidesobissed EE EEE Eaa ESEESE a 49 44 Set Administrator and Mobile Client Ports ceeeeessccccccecesseseseceececeeecessesenneaeeees 54 45 Users and
81. ceee Login Setting a fixed or dynamic port for the Configuration page The port of the Configuration page Web Ul and consequently its address can be specified in the Settings page By default the port is 8088 You can set any other port you want for the LicenseServer Configuration page see screenshot below Alternatively you allow the port to be selected dynamically each time LicenseServer starts up In this case you will need to find out the URL of the Configuration page from the file webuI htm1 See Open LicenseServer Config Page Windows and Open LicenseServer Config Page Linux Web UI Changing these settings will cause the LicenseServer to restart and any currently running and licensed applications will be shut down Configure the host addresses where the web UI is available to administrators All interfaces and assigned IP addresses 5 Only the following hostname or IP address 0 0 0 0 Ensure this hostname or IP address exists or LicenseServer will fail to start Configure the port used for the web UL D Dynamically chosen by the operating system Fixed port 8088 Ensure this port is available or LicenseServer will fail to start The advantage of a fixed port is that the page URL is known in advance and therefore can be accessed easily If the port is assigned dynamically the port part of the URL will have to be looked up in the file webUI htm1 each time LicenseServer is started Altova Mobile To
82. censeServer the older version will be de installed before the newer version is installed The version number of the currently installed LicenseServer is given at the bottom of the LicenseServer configuration page all tabs Current version 1 23 The version number of the LicenseServer that is appropriate for any particular version of a server 129 Altova MobileTogether Server 130 Altova LicenseServer Installation Windows product is displayed during the installation of that version of the server product You can choose to install this version of LicenseServer along with the server product or you can install the newer version of LicenseServer separately In both cases the installer will automatically de install the previous version and install the new version Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer Installation Linux 131 7 3 Installation Linux Altova LicenseServer can be installed on Linux systems Debian Ubuntu CentOS RedHat System requirements Linux e CentOS 6 or newer e RedHat 6 or newer e Debian 6 or newer e Ubuntu 12 04 or newer Note that the Qt library version 4 available under GNU GPL and LGPL must be installed Uninstalling old versions of LicenseServer On the Linux command line interface CLI you can check whether LicenseSerer is installed with the following command Debian Ubuntu dpkg list grep Altova CentOS RedHat rpm qa grep server
83. censeServer service is available to clients All interfaces and assigned IP addresses Local only localhost Only the following hostnames or IP addresses Ensure the hostnames or IP addresses exist or LicenseServer will fail to start e Web UI Allowed IP addresses can vary from all interfaces and IP addresses on that machine to a fixed address and ports can be either dynamically calculated or fixed This allows a wide range of allowed IP Address Port settings The default port setting is 8088 e Proxy Server available from v1 3 onwards lf a proxy server is being used to connect to the Internet the details of the proxy server must be entered in the Proxy Server pane see screenshot above Otherwise the proxy server settings can be left blank To configure LicenseServer to use a proxy server enter the proxy server s host name and if required a port number If the proxy server does not need authentication then the User Name and Password fields can be left blank e License Service The machine on which License Server is installed can be connected to multiple networks via one or more network interfaces On each network the License Server machine is known by a host name and an IP address The License Service setting lets you configure on which networks the license servce is available The localhost option allows the service on the local machine only If you list hostnames and or IP addresses use a comma separated list without
84. cessed easily If the port is assigned dynamically the port part of the URL will have to be looked up in the file webUI htm1 each time LicenseServer is started Altova Mobile Together Server 2015 Altova GmbH Altova LicenseServer How to Assign Licenses 143 Open LicenseServer s Config Page Mac OS X This section Opening the Configuration page for the first time with the returned URL URL of the LicenseServer Configuration page Logging in with the initial password Setting a fixed port for the Configuration page Opening the Configuration page for the first time with the returned URL On Mac OS Xsystems when you register your Altova server product with LicenseServer via the CLI the URL of the LicenseServer Configuration page is returned On opening this URL ina browser you are prompted to read and accept the license agreement After accepting the license agreement the Configuration page s login mask is displayed screenshot below URL of the LicenseServer Configuration page To open the LicenseServer Configuration page at any time enter its URL in the address bar of a browser and press Enter By default the URL of the Configuration page will be http lt serverIPAddressOrName gt 8088 The URL is present in the HTML code of the Configuration page itself which is named webUI html and is located at var Altova LicenseServer webUI html If you have set the URL of the Configuration page to be generated dynamically in the
85. ckey cer This is the public key certificate file of your SSL certificate It includes your public key certificate as well as the complete chain of trust in the form of the intermediate certificates that were used by the CA to sign your certificate The public key certificate file will be installed on MobileTogether Server together with the private key see Step 8 8 Install SSL certificate on MobileTogether Server The SSL certificate is a set of certificates that are saved in the following files e private key Contains the private key certificate e publickey cer Contains the public key certificate and the CA s intermediate certificates primary and secondary Altova MobileTogether Server 2015 Altova GmbH Setting Up MobileTogether Server Setting Up SSL Encryption 41 To install the SSL certificates on MobileTogether Server do the following e Log in to the MobileTogether Server UI by default on port 8085 of your server e Go to the Settings tab e Under SSL Certificates see screenshot below upload the two certificate files SSL certificates Select the private key and the certificate needed for secure SSL communication A valid private key and certificate must be supplied in order to use secure HTTPS ports The private key certificate must be in PEM format Private Key Browse_ No file selected Certificate Browse_ No file selected o For the private key select private key created in Step 1 o F
86. configuration page Web Ul for the proxy server used to connect to the Internet if any and for License Service availability These settings are described in Network settings below e Email server settings and the alert mail recipient to contact in the event of a significant LicenseServer occurrence These settings are described in Alert Mail settings below e After you change a setting click Save at the bottom of the pane A changed setting will not take effect till it is saved Failover LicenseServer settings A second LicenseServer can be configured to take over from the Primary LicenseServer if the Primary LicenseServer becomes unavailable This second LicenseServer is called the Failover LicenseServer Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer Configuration Page Reference 181 Failover LicenseServer Settings To reduce the risk of an unavailable LicenseServer you can configure a second LicenseServer as a backup or Failover LicenseServer In the event that the Primary LicenseServer becomes unavailable a Failover LicenseServer can take over LicenseServer Mode 5 Primary LicenseServer Failover LicenseServer Please note The Failover LicenseServer periodically synchronizes all licenses registered clients and license assignments from the Primary LicenseServer Whenever a Failover LicenseServer takes over from a Primary LicenseServer any changes to these items made on the Failover LicenseServer du
87. ct Form json true fals 2015 Altova GmbH Altova MobileTogether Server 108 Command Line Usage assignlicense Windows only 6 2 assignlicense Windows only This section e Command syntax e Command description e Examples e Command options Command syntax Windows MobileTogetherServer assignlicense options FILE Note This command is supported only on Windows systems It is not supported on Linux or Mac systems Command description On execution the assignlicense command uploads the license file specified by the FILE argument to the registered LicenseServer and assigns the license to MobileTogether Server on this machine The FILE argument takes the filepath of the license file The test only option allows you to upload to LicenseServer and validate the license without assigning the license to MobileTogether Server For details about licensing see the LicenseServer documentation Examples Examples of the assignlicense command mobiletogetherserver assignlicense C MobileTogether Server12345 altova_licenses mobiletogetherserver assignlicense test only true C MobileTogether Server12345 altova_licenses The first command above uploads the specified license to LicenseServer and assigns it to MobileTogether Server The second command uploads the specified license to LicenseServer and validates it without assigning it to MobileTogether Server v Casing on the command line Altova MobileTogether Server 2
88. d to another role or to a user A role s privileges automatically become the privileges of any other role or any user that the role is assigned to A user can be assigned any number of roles As a result a user will have all the privileges defined in the multiple assigned roles The following roles are predefined authenticated is automatically assigned to every user except anonymous So user with a name and password is assigned the authenticated role all is automatically assigned to every user including anonymous workflow designer is assigned to users that design workflows in MobileTogether Designer This role allows a user to open and save workflows as well as to runa simulation on the server workflow user is assigned to users running the workflow on a mobile device This role allows the user to access the service interface without needing to log in to the server and start the solution on the client Roles Name amp all B authenticated BR workflow designer R workflow user Create Role Import Domain Roles Via the Users and Roles Roles tab you can create new roles edit the properties of roles and assign roles to users and or other roles Click the name of a role to access its Properties page where you can select deselect privileges and assign the role to a user and or other roles v Creating a role and defining its privileges A new role can be created by root user or any user that has the Maintain users roles
89. d to be imported individually as MobileTogether Server users This import is done via the Import Altova Mobile Together Server 2015 Altova GmbH Web UI Reference Settings 101 Users button of the Users tab e Domain suffixes Enter the domains to include separating domains from one another with a comma v Email settings These settings enable emails to be sent by the end user via the server Typically the solution will provide an event that triggers a Send Email action that has been defined to send the email from the server In order for the server to do this it needs to access the SMTP server of the email service provider usually your ISP The settings for the SMTP server are entered in this pane screenshot below Email settings Configure settings for server side email sending SMTP Host smtp gmail com SMTP Port 587 Use SSL User Name altovauser Password evcccccce Send Test Email e SMTP Host and SMTP Port These are the SMTP host name and SMTP port of your ISP s SMTP server These details are provided to you by your ISP e User Name and Password The user name and password of an email account that is registered with the email service provider After entering the details click Save You can send a test email to check whether MobileTogether Server is able to correctly send via the SMTP server v LicenseServer MobileTogether Server must be registered with an Altova LicenseServer on your network The
90. default is as follows var opt Altova MobileTogetherServer var Altova MobileTogetherServer Windows XP C Documents and Settings All Users Application Data Altova MobileTogetherServer Windows Vista Windows 7 C ProgramData Altova MobileTogetherServer Windows 8 The following table lists the main files and folders in the application data folder cache Default directory for caches of solutions If a cache is not available it will be recreated automatically at runtime logs Default directory for log files that are created when the Logging to file option is enabled and for general MobileTogether Server logs Default directory for XML or image files referenced from deployed solutions PEM file with certificate needed for secure SSL communication key pem PEM file with private key needed for secure SSL communication mobiletogether db This is the main database file SQLite that stores the MobileTogether Server object system user data deployed Altova MobileTogether Server 2015 Altova GmbH Server Procedures How to Back Up and Restore MobileTogether Server 65 solutions files and others mobiletogetherlog db This is the database file SQLite that stores the MobileTogether Server logs mobiletogetherserver cf Stores global configuration settings of MobileTogether Server port g number solutions directory etc mobiletogetherserver 1i File with ID of registered LicenceServer client csid
91. define any constraint and cannot be changed If you want users to have stronger passwords than defined by the default policy create a strong policy and assign this policy to individual users v Creating a password policy A new password policy can be created by root user or any user that has the Maintain users roles and privileges privilege Create a new password policy as follows 1 Inthe Users and Roles Password Policies tab click Create Policy see screenshot below This displays the Create Password Policy page Password Policies Name Default Policy MediumSecurity Create Policy 2 Onthe Create Password Policy page give the policy a name 3 To define the constraints of the password click the plus icon next to a constraint Total length Letters Digits and enter a value for the constraint see screenshot below 2015 Altova GmbH Altova MobileTogether Server 88 Web UI Reference Users and Roles Password policy MediumSecurity Policy name MediumSecurity Password Policies Total length must contain at least characters Letters must contain at least letters Digits 4 Click Save to finish After you have saved the policy you can assign users to it in the Members pane at the bottom of the page see next section You can subsequently edit a policy s properties by clicking its name in the list of policies in the Users and Roles Policies tab v Assigning members users to a password
92. ds For example sudo etc init d licenseserver stop v Start MobileTogether Server Start MobileTogether Server as a daemon with the following command Debian 6 7 sudo etc init d mobiletogetherserver start Debian 8 sudo systemctl start mobiletogetherserver Ubuntu lt 14 sudo initctl start mobiletogetherserver Ubuntu 15 sudo systemctl start mobiletogetherserver CentOS 6 sudo initctl start mobiletogetherserver CentOS 7 sudo systemctl start mobiletogetherserver RedHat sudo initctl start mobiletogetherserver To set up and configure MobileTogether Server open its Web UI Setup page by entering the URL of the Web UI page in the address bar of an Internet browser http lt serverIPAddressOrName gt 8085 Firewall Note Make sure that the port address is not blocked by your firewall Altova MobileTogether Server 2015 Altova GmbH 2015 Altova GmbH Setting Up MobileTogether Server Setup on Linux v Register MobileTogether Server Register MobileTogether Server via e its CLI using the licenseserver Command sudo opt Altova MobileTogetherServer2 0 bin mobiletogetherserver licenseserver options ServerName Or IP Address For example if localhost is the name of the server on which LicenseSerer is installed sudo opt Altova MobileTogetherServer2 0 bin mobiletogetherserver licenseserver localhost In the command above localhost is the name of the server on which LicenseServer is installed Notice also
93. dy in the license pool will be added to the license pool licenses that are already in the pool will not be re added 2015 Altova GmbH Altova MobileTogether Server 172 Altova LicenseServer Configuration Page Reference Icons in the License Pool tab Edit Assigned Licenses Appears with each license in the Assignments column Pops up the Manage Licenses dialog in which new licenses can be assigned to the product and already assigned licenses can be edited P o Show License Information Appears with each license in the Assignments column Provides information about the currently active clients License information The following license information is displayed e Status Can be one of the following values Failed Verification Activating Active Inactive Blocked See License status above e Name Company The name and company of the licensee This information was submitted at the time of purchase e Product Edition Version The version and edition of the licensed products e Key Expires in days SMP days left The license key to unlock the product and the number of days left before the license expires Each licensed purchase comes with a Support amp Maintenance Package which is valid for a certain number of days The SMP column notes how many SMP days are still left e License Type The number of users or CPU cores that the license allows is listed in the column Whether it is users or cores that the license reg
94. e See the documentation of your Altova server product for additional information 5 Inthe Server Management tab of the LicenseServer Configuration page assign a license to the Altova server product according to the number of cores on the product machine Note on cores and licenses The licensing of Altova server products is based on the number of processor cores available on the product machine for MobileTogether Server an additional licensing option is available see below For example a dual core processor has two cores a quad core processor four cores a hexa core processor six cores and so on The number of cores licensed for a product must be greater than or equal to the number of cores available on that server machine whether the server is a physical or virtual machine For example if a server has eight cores an octa core processor you must purchase at least one 8 core license You can also combine licenses to achieve the core count So two 4 core licenses can also be used for an octa core server instead of one 8 core license If you are using a computer server with a large number of CPU cores but only have a low volume to process you may also create a virtual machine that is allocated a smaller number of cores and purchase a license for that number Such a deployment of course will have less processing speed than if all available cores on the server were utilized Note Each license can be used for only one client machi
95. e number of processor cores available on the product machine for MobileTogether Server an additional licensing option is available see below For example a dual core processor has two cores a quad core processor four cores a hexa core processor six cores and so on The number of cores licensed for a product must be greater than or equal to the number of cores available on that server machine whether the server is a physical or virtual machine For example if a server has eight cores an octa core processor you must purchase at least one 8 core license You can also combine licenses to achieve the core count So two 4 core licenses can also be used for an octa core server instead of one 8 core license If you are using a computer server with a large number of CPU cores but only have a low volume to process you may also create a virtual machine that is allocated a smaller number of cores and purchase a license for that number Such a deployment of course will have less processing speed than if all available cores on the server were utilized Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer How to Assign Licenses 165 Note Each license can be used for only one client machine at a time even if the license has unused licensing capacity For example if a 10 core license is used for a client machine that has 6 CPU cores then the remaining 4 cores of licensing capacity cannot be used simultaneously for another client m
96. e secure HTTPS ports The private key certificate must be in PEM format Private Key No file selected Certificate Browse_ No file selected v Logging Logs contain reports of workflow activity and they are displayed in the Log tab of the Web UI The settings in this pane define logging parameters 2015 Altova GmbH Altova MobileTogether Server 98 Web UI Reference Settings Logging Logging level detail Error ba Select logging detail you want to use during a workflow execution Logs are by default stored in the database and are accessible via Log page Log Limit 7 day s v Logging to file Enable workflow execution logging to file for users granted the Trace workflow privilege Log files contain detailed workflow execution information including working XMLs Logging to file directory C ProgramData Altova MobileTogetherServer logsTXT Specify the server side directory where log files will be placed e Logging level detail The detail can vary from logging only errors through logging errors and warnings and most detailed logging errors warnings and information e Log limit Specifies for how long logs are kept e Log files Users that have been granted Trace workflow privileges can have logs saved to file if the Logging to file option is selected The directory where logs are saved is specified in the Logging to file directory option v Workflow simulation on serve
97. eServer sssseeecececeeeseeeeneeeeeeeceseesenneaeeees 145 7 6 6 Register Products iicet ieii 149 Register FIOWFOrce Servet 150 Register MapForce Serve r ccccessssscsscccsnnsesseseessceceanenaseneesscscenaeeaseneess 155 Register Style Vision Server eseese eses eseseseseseses 157 Register RaptorXML XBRL Servei sccscccccccceseesesscnececeeesessensnnnaeeees 159 Register MobileTogether Servet eserse 161 7 6 7 Assign Licenses to Registered Products esseneeeeeeeeeerereessesesrrerressessseee 162 7 7 Configuration Page Reference eseeeeecessessersrrressssssrrrreertsseserrreesesssstereeesessessseet 168 PA License Pool ninen ya narea a a e E teeta E ease eaeaes 169 Tih Server Management roria e ar E a Er AE Eai sees 174 TAs S rverMonitGrine a eaae r ra E ieee eas ec EAE S EENES ote eevee 179 TET E 8S E E ET 180 TTS Messages L g Out derreire i ninia a aeai ia 186 Te Password Reset Aano eR a EEEE EEE EE O a EEE ie 187 Index 189 Altova Mobile Together Server Chapter 1 Altova MobileTogether Server Altova MobileTogether Server 3 1 Altova MobileTogether Server MobileTogether Server serves MobileTogether solutions to client mobile devices It runs on MS Windows Linux and Mac OS X machines e MobileTogether solutions are created in Altova s MobileTogether Designer application and are deployed from MobileTogether Designer to MobileTogether Server e The MobileTogether Client app tha
98. eb UI tabs e Workflows An interface for managing the server s container structure and container permissions e Users and Roles To set up user accounts and roles and the privileges associated with users and roles The access rights of users are defined in this tab e User licenses Shows the mobile devices that are currently licensed and their license details e Log Displays the logged server actions according to the selected filters e Cache This tab shows the details of caches that are currently available on the server Caches can also be activated deactivated and deleted e Settings MobileTogether Server settings such as access ports log settings and server session timeouts are defined in this tab 2015 Altova GmbH Altova MobileTogether Server 70 Web Ul Reference Workflows 5 1 Workflows The Workflows tab screenshot below provides an interface for managing the container structure of the root folder of MobileTogether Server and the access rights permissions for each container Containers are folders that contain sub containers and or solutions aka design files or mtd files MTD files cannot be added to a container via the server s Web UI but are deployed to the server from MobileTogether Designer At deployment the exact path to a container must be specified this is facilitated by being able to browse in MobileTogether Designer to the required container The Work flows tab initially displays the root container
99. ed in the following files e private key Contains the private key certificate e publickey cer Contains the public key certificate and the CA s intermediate certificates primary and secondary 2015 Altova GmbH Altova MobileTogether Server 52 Server Procedures Set Up SSL Encryption To install the SSL certificates on MobileTogether Server do the following e Log in to the MobileTogether Server UI by default on port 8085 of your server e Go to the Settings tab e Under SSL Certificates see screenshot below upload the two certificate files SSL certificates Select the private key and the certificate needed for secure SSL communication A valid private key and certificate must be supplied in order to use secure HTTPS ports The private key certificate must be in PEM format Private Key Browse_ No file selected Certificate Browse_ No file selected o For the private key select private key created in Step 1 o For the certificate select publickey cer created in Step 7 e Click Save at the bottom of the General Settings section to save your changes 9 Set the server s HTTPS port After installing the SSL certificate you can specify a server port for SSL client communication Do this as follows e Log in to the MobileTogether Server UI by default on port 8085 of your server e Go to the Settings tab e Under Mobile Client Ports see screenshot below enable and specify the HTTPS port
100. ee a listing of all the privileges of a user or role go to the tab Users and Roles Reports Privileges by User v Importing a domain role If Active Directory login has been enabled for a domain you can import the individual roles of an enabled domain Click Import Domain Roles see screenshot below In the Import Domain Roles dialog that is displayed search for the role you want to import select it and click Import Selected 2015 Altova GmbH Altova MobileTogether Server 86 Web UI Reference Users and Roles Roles Name B al C B authenticated B workflow designer B workflow user Create Role Import Domain Roles After the role is imported you can assign privileges to the role as for any other role The new privileges will be allowed to those domain specific roles Altova MobileTogether Server 2015 Altova GmbH Web Ul Reference Users and Roles 87 Password Policies A password policy defines the strength of passwords that use that policy You can define your own password policies and apply different policies to different users The Users and Roles Password Policies tab screenshot below displays all defined password policies enables you to create new policies assign policies to users and delete policies Password Policies Name Default Policy MediumSecurity Create Policy Note By default every new user is assigned the default password policy which does not
101. en the remaining 4 cores of licensing capacity cannot be used simultaneously for another client machine MobileTogether Server licenses Altova MobileTogether Server 2015 Altova GmbH Setting Up MobileTogether Server Setup on Mac OSX 35 Two types of MobileTogether Server license are available Customers can select a license type that best suits their requirements e Core licenses These are assigned to MobileTogether Servers on the basis of the cores on the server machine see the explanation above An unlimited number of MobileTogether Client devices can then connect to the server e User licenses These specify the maximum number of users MobileTogether Client devices that are allowed to connect to the MobileTogether Server at one time 2015 Altova GmbH Altova MobileTogether Server 36 Setting Up MobileTogether Server Setup on Mac OS X Notes about Environment Folders Given below is a list of important folders in your MobileTogether Server setup a Installation root usr local Altova MobileTogetherServer2 0 a Database License and Solution Files var Altova MobileTogetherServer Environment settings Library LaunchDaemons com altova MobileTogetherServer plist The environment settings file must be defined according to your specific envronment The example path above serves only as a general guide Note These environment variables are only set for the MobileTogether Server process and do not have an impact
102. end the request You will receive an e mail from Altova containing the 30 day evaluation license s The number of cores for which the license will be valid per product will be exactly the number required by the product at the time the request is sent Save the license s to disk and upload to the license pool Unregistering products Each Altova product registered with LicenseServer is listed in the Server Management tab under its client machine name and has an Unregister icon to its right Click this icon to unregister the 2015 Altova GmbH Altova MobileTogether Server 178 Altova LicenseServer Configuration Page Reference product If a license was assigned to the product the assignment will be terminated when the product is unregistered To unregister all products click the Unregister Server and All Products button at the bottom of the Server Management tab see first screenshot in this section To re register a product with LicenseServer go to the product s Setup page or its CLI and register it See Register FlowForce Server Register MapForce Server Register StyleVision Server and Register RaptorxXML XBRL Server For more information see the section Assigning Licenses to Registered Products Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer Configuration Page Reference 179 Server Monitoring The Server Monitoring tab provides an overview of servers currently running licensed Altova products It contain
103. enses The User Licenses tab screenshot below displays license information about the devices currently connected to and licensed with MobileTogether Server and enables licenses to be activated and deactivated User licenses Licenses used 5 of 8 Licensing mode Auto M ID User Name Device Client Version Request Time Active Activation Time 5 root Mozilla 5 0 Windows NT 6 1 WOW64 1 1 4 2014 09 26 15 03 19 v 2014 09 26 15 03 19 4 root Samsung GT 19000 Android 2 3 3 1 4 2014 07 09 12 10 49 v 2014 07 09 12 10 49 3 root WPS device WP 8 0 10501 0 1 0 b1 2014 07 08 14 48 30 Ea 2014 07 08 14 48 30 2 root Mozilla 5 0 Windows NT 6 1 WOW64 1 1 3 2014 06 12 11 05 21 v 2014 06 12 11 05 21 1 root Apple iPhone iPhone OS 6 0 1 0 b1 2014 06 04 12 13 07 v 2014 06 10 16 34 21 P Search Page 1 ofi 235 v View1 5o0f5 e A MobileTogether Server license allows a certain number of devices to communicate with the MobileTogether Server at any given time This number is given in the Licenses used field For example in the screenshot above the server is licensed to communicate with 8 devices Two devices are connected and both are licensed indicated by their Active check boxes being selected The Licenses used field therefore shows 2 out of 8 licenses used e Once a client device connects to the server it will be assigned a license automatically if the Licensing mode option is set to Auto see screenshot above If this opti
104. ent device tries to connect via the Internet using the server s private IP address then the connection will not work This is because the private IP address is not known on the Internet and cannot be resolved If a client device uses a private IP address then the client device must already have access to the private network To ensure that the server can be accessed do one of the following e Provide the server with a public IP address so that it can be reached via the Internet On the client device use this public IP address to access the server If you use a firewall and install MobileTogether Server on a server with a private IP address inside the private network then use the network firewall to forward requests sent to a public IP address port combination to your MobileTogether Server server On the client device use the public IP address You must also ensure that the firewall is configured to allow access to the server port used for MobileTogether Client communication The ports used by MobileTogether Server are specified in the Settings page of the the Web UI of MobileTogether Server see the MobileTogether Server user manual On the client device this is the port that must be specified as the server port to access Tip Port 80 is usually open on most firewalls by default So if you are having difficulties with firewall settings and if port 80 is not already bound to some other service you could specify port 80 as the MobileTogeth
105. er Altova RaptorXML XBRL Altova StyleVision Server Altova FlowForce Server Altova StyleVision Server C FS36_License altova_licenses 2013 2013 2013 2013 2013 MMSUC1U HC139LF 3D78278 966PPHM DAST2WU To upload a license file which you receive from Altova GmbH for your Altova server product click the Browse button browse for the license file and select it On clicking Upload all the licenses 2015 Altova GmbH Altova MobileTogether Server 170 Altova LicenseServer Configuration Page Reference contained in the license file are placed in the license pool and displayed on the License Pool page screenshot above License status License status values are as follows e Activating When a license is uploaded into the license pool of LicenseServer the server will transmit license related data to the altova com master licensing server to validate authenticate and activate the license that was supplied This is necessary to ensure compliance with the Altova license agreements During this initial activation and authentication transaction which typically lasts between 30 seconds and a couple of minutes depending on your Internet connection speed and overall network traffic the status of the license will be indicated as Activating e Failed Verification f a connection with the altova com master licensing server cannot be made then the status of the license in the pool will be shown as Failed Verifica
106. er By default the URL of the Configuration page will be http lt serverIPAddressOrName gt 8088 The URL is present in the HTML code of the Configuration page itself which is named WebUI htm1 and is located at Altova MobileTogether Server How to Assign Licenses 2015 Altova GmbH Altova LicenseServer How to Assign Licenses 139 C ProgramData Altova LicenseServer WebUI html If you have set the URL of the Configuration page to be generated dynamically in the Settings tab of the Configuration page then a new URL is generated each time LicenseServer is started You will need to check the current version of WebUI htm1 to find out the current URL of the Configuration page The dynamically generated URL in WebUI htm1 will have a form something like http 127 0 0 1 55541 optionally an additional string and it is located in the function checkI fServiceRunning in a script near the end of the lt head gt element While the port number in the URL is dynamically assigned the IP address part identifies the server on which LicenseServer has been installed If you wish to access the LicenseServer Configuration page from another machine make sure that the IP address part of the URL has the correct IP address or name of the server on which LicenseServer has been installed For example the URL could be something like http MyServer 55541 Logging in with the initial password After going through the steps above the Confi
107. er Server port for client communication Altova MobileTogether Server 2015 Altova GmbH Server Procedures Information for Clients 63 48 Information for Clients The MobileTogether Client app on mobile devices will need to connect to MobileTogether Server The following server information will be required by the MobileTogether Client app IP Address The IP address of MobileTogether Server Port The HTTP or HTTPS port which is specified in the Mobile Client Ports setting SSL Whether communication should be SSL encrypted or not As what user to log in This will determine access rights See Users and Roles The password of the user account Note Data that is saved on the web client is saved in the local storage aka web storage of your browser HTML 5 0 local storage is supported in the following browsers IE 8 0 Firefox Safari Chrome Opera iPhone Android IOF 4 0 4 0 10 5 2 0 2 0 Updating server settings on client devices In order for a client device to run a solution the server s access settings must be configured on that device If the server settings change for example if the MobileTogether Server is moved to another machine that has a different IP address then the server settings on client devices must be modified accordingly In MobileTogether Designer you can use the MobileTogether function mt server config url to generate a URL that contains the new server settings and looks something like this mobileto
108. er at Startup option Altova ServiceController will start up on system start and its icon will be available in the system tray from then onwards BD Altova FlowForce Server gt DB Altova FlowForce Web gt H Altova LicenseServer 5 D Altova MobileTogether Server gt Start service Altova RaptorXML XBRL Server gt Stop service Exit Altova ServiceController Run Altova ServiceController at startup a a i g 14 00 AM To start LicenseServer click the Altova ServiceController icon in the system tray hover over Altova LicenseServer in the menu that pops up see screenshot below and then select Start Service from the LicenseServer submenu If LicenseServer is already running the Start Service option will be disabled Linux systems To start LicenseServer as a service on Linux systems run the following command in a terminal window Debian 6 7 sudo etc init d licenseserver start Debian 8 sudo systemctl start licenseserver Ubuntu lt 14 sudo initctl start licenseserver Ubuntu 15 sudo systemctl start licenseserver CentOS 6 sudo initctl start licenseserver CentOS 7 sudo systemctl start licenseserver RedHat sudo initctl start licenseserver Altova Mobile Together Server 2015 Altova GmbH Altova LicenseServer How to Assign Licenses 137 If you need to stop LicenseServer replace start with stop in the above command Mac OS X systems To start LicenseServer as a service on Mac OS Xsystems r
109. erver Altova ServiceController to start Altova ServiceController and display its icon in the system tray see screenshot below If you select the Run Altova ServiceController at Startup option Altova ServiceController will start up on system start and its icon will be available in the system tray from then onwards BD Altova FlowForce Server gt GB Altova FlowForce Web gt A Altova LicenseServer D Altova MobileTogether Server gt Start service Altova RaptorXML XBRL Server gt Stop service Exit Altova ServiceController Run Altova ServiceController at startup a Z g 11 00 AM ia To start MobileTogether Server click the Altova ServiceController icon in the system tray hover over MobileTogether Server in the menu that appears see screenshot above and then select Start Service from the MobileTogether Server submenu If MobileTogether Server is already running the Start Service option will be disabled To stop MobileTogether Server select Stop Service from the MobileTogether Server submenu see screenshot above v On Linux To start MobileTogether Server as a service on Linux systems run the following command in a terminal window Debian sudo etc init d mobiletogetherserver start Ubuntu sudo initctl start mobiletogetherserver CentOS 6 sudo initctl start mobiletogetherserver CentOS 7 sudo systemctl start mobiletogetherserver RedHat sudo initctl start mobiletogetherserver
110. erver If no global resource is specified Default is displayed e Persistent Data A Clear Data button appears in this column if data has been changed while running the solution Click the button if you wish to undo the changes e Run in Browser The server URL where the solution file is deployed Click to run the solution Permissions Permissions are access rights and they can be set for each container individually Permissions determine which users or roles have access to that container and what kind of access each user role has read write use These access rights can be set for the container its workflows or solutions and read write security 2015 Altova GmbH Altova MobileTogether Server 72 Web Ul Reference Workflows Permissions for public contacts User or Role name Permissions Container Read Write inherited from ob public amp anonymous Workflow Read Write Use inherited from o public Security Read inherited from 6 public Container Read inherited from 5 B authenticated Workflow Read Write Use Security Read inherited from Container Read Write inherited from Workflow Read Write Use inherited from B authenticated Security Read Write inherited from Add Permissions a Rules for inheritance of permissions e For containers permissions are inherited from parent containers e For users permissions are inherited from all roles the user is a member of as well
111. erver Server Or IP Address For example if LicenseServer is running on http localhost 8088 then register StyleVision Server with StyleVisionServer licenseserver localhost After successfully registering StyleVision Server you can go to LicenseServer and assign a 2015 Altova GmbH Altova MobileTogether Server 158 Altova LicenseServer How to Assign Licenses license to StyleVision Server How to do this is described in the section Assign Licenses to Registered Products Registering StyleVision Server Linux On Linux machines StyleVision Server can be registered with LicenseServer by using the licenseserver command of the StyleVision Server CLI Note that StyleVision Server must be started with root rights sudo opt Altova StyleVisionServer2016 bin stylevisionserver licenseserver localhost In the command above localhost is the name of the server on which LicenseServer is installed Notice also that the location of the StyleVision Server executable is opt Altova StyleVisionServer2016 bin After successfully registering StyleVision Server you can go to LicenseServer and assign a license to StyleVision Server How to do this is described in the section Assign Licenses to Registered Products Next Steps After you have registered your Altova product with LicenseServer do the following 1 If you have not already uploaded your license file s to the LicenseServer see previous section Upload the license s upload the
112. erver at altova com The Altova LicenseServer needs to be able to communicate with the Master Licensing Server at altova com to validate and authenticate license related data and to ensure continuous compliance with the Altova license agreements This communication occurs over HTTPS using port 443 If the Altova LicenseServer after making the initial verification with the altova com Master Licensing Server is unable to again connect with altova com for a duration of more than 5 days 120 hours then the Altova LicenseServer will no longer permit the usage of any Altova software products connected to the Altova LicenseServer Any such loss of connection with the altova com master servers will be logged in the Messages tab of the Configuration page of the Altova LicenseServer In addition the administrator can configure the Altova LicenseServer to automatically send an alert email when the connection to altova com is lost Alert Mail settings are available in the Settings tab of the Configuration page Activating deactivating and deleting a license An active license can be deactivated by selecting the license and clicking Deactivate An inactive license can be activated Activate button or deleted Delete button When a license is deleted it is removed from the license pool A deleted license can be added again to the license pool by uploading the license file containing it If a license file is re uploaded only licenses that are not alrea
113. es from an SSL certificate authority CA typically takes two to three business days Please take this into account when setting up your MobileTogether Server 4 Receive public key from CA Your certificate authority will complete the enrollment process over the next two to three business days During this time you might get emails or phone calls to check whether you are authorized to request an SSL certificate for your DNS domain Please work with the authority to complete the process After the authorization and enrollment process has been completed you will get an email containing the public key of your SSL certificate The public key will be in plain text form or attached as a 5 Save public key to file For use with MobileTogether Server the public key must be saved ina cer file If the public key was supplied as text copy paste all the lines from BEGIN CERTIFICATE END CERTIFICATE into a text file that we will call myeertificate cer 6 Save CA s intermediate certificates to file To complete your SSL certificate you will need two additional certificates the primary and secondary intermediate certificates Your certificate authority CA will list content of intermediate certificates on its website 2015 Altova GmbH Altova MobileTogether Server 40 Setting Up MobileTogether Server Setting Up SSL Encryption e Verisign s intermediate certificates https knowledge verisig
114. ether Server as a service e MobileTogether Server for debugging not as a ne upgradedb Upgrades the internal MobileTogether Server DB to the structure of the new version and enters correct default values where necessary Exports all application resource strings to an XML file Sets the default language help Displays help for a specific command For example help generate Displays the version and exits 2015 Altova GmbH Altova MobileTogether Server 106 Command Line Usage licenseserver 6 1 licenseserver This section e Command syntax e Command description e Examples e Command options Command syntax Windows MobileTogetherServer licenseserver options Server Or IP Address Linux mobiletogetherserver licenseserver options Server Or IP Address Mac mobiletogetherserver licenseserver options Server Or IP Address Command description On execution the 1icenseserver command registers MobileTogether Server with the LicenseServer specified by the Server Or IP Address argument Server Or IP Address identifies the machine on the network on which Altova LicenseServer is installed and running It can be the machine s name or its IP address For the 1icenseserver command to be executed successfully the two servers must be connected on the network and LicenseServer must be running You must have administrator privileges to be able to register MobileTogether Server with LicenseServer Once MobileTogether Se
115. ey will be used to encrypt all data sent to MobileTogether Client apps To create the private key use the following OpenSSL command openssl genrsa out private key 2048 This creates a file called private key which contains your private key Note where you save the file You will need the private key to i generate the Certificate Signing Request CSR and ii to be installed on MobileTogether Server see Step 8 below 2 Certificate Signing Requests CSRs A Certificate Signing Request CSR is sent to a certificate authority CA such as VeriSign or Thawte to request a public key certificate The CSR is based on your private key and contains information about your organization Create a CSR with the following OpenSSL command which provides the private key file private key that was created in Step 1 as one of its parameters openssl req new nodes key out my csr During generation of the CSR you will need to give information about your organization such as that listed below This information will be used by the certificate authority to verify your company s identity e Country e Locality the city where your business is located e Organization your company name Do not use special characters these will invalidate your certificate e Common Name the DNS name of your server This must exactly match your server s official name that is the DNS name client apps will use to connect to the server e A challenge password
116. g Cache Settings Help English Container public Type here to search Search J Recursive PA Global Resource Persistent Name Al Descripti i 5 Run in Bron me pp App ver ption Version LastDeployedon Configuration ae un in Browser contacts Permissions new Permissions E fe sogtime JogTime 10 Altova JogTime custom app 20 2015 10 06 13 19 11 Default v l fel Assertions Sample description for file Assertions dpl 15 2015 03 30 10 51 56 Default v http 127 0 0 1 3085 run d pu v The display of a container s contents A container contains sub containers and or solutions aka design files or mtd files The contents of each container are displayed as a tabular list The columns of the table display the properties of solutions e Name Name of the solution file as saved in MobileTogether Designer e App App version The App and App Ver columns appear only if at least one AppStore App see the MobileTogether Designer user manual has been deployed to the server They display respectively the name of the AppStore App and its version e Description Short description of the solution which can be entered by clicking in the field e Version Version of MobileTogether Designer in which the solution was created e Last Deployed On The date and time of the solution s last deployment e Global Resource Configuration The global resource that has been defined for that solution and deployed to the s
117. ge has a Delete button that allows you to delete that particular message The Log Out tab serves as the Log Out button Clicking the tab logs you out immediately and then displays the Login mask Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer Password Reset 187 7 8 Password Reset If you forget your LicenseServer password you can use the passwordreset command from the CLI to reset the password to default 1 Open a command line window 2 Change to the directory where the LicenseServer application package or executable is installed 3 Enter the command licenseserver passwordreset This resets the LicenseServer administrator password to default 4 You can now log in to the Administrator Web UI with the password default 2015 Altova GmbH Altova MobileTogether Server Index Index A Active directory login 96 Address of server 96 Administrator interface 168 Administrator ports 54 96 Alert emails 180 Altova LicenseServer see LicenseServer 126 connection settings 96 registering with 96 starting 45 Altova ServiceController 134 Assigning licenses 162 174 B Backing up MobileTogether Server 64 Browsers enabling execution of solutions for 96 C Cache settings 96 Caches creating 94 settings of 94 Client ports 96 Client users list 90 Command line usage 104 Commands exportresourcestrings 117 help 121 licenseserver 106 setdeflang 119 Configuration page 1
118. ge to be displayed Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer How to Assign Licenses 153 ALTOVA LicenseServer DOC altova com Altova FlowForce Server 2014 EA This server has 2 CPU core s Key Code CPU Cores Licenses for 2 CPU core s are required El Limit to single thread execution Max licensed CPU cores 0 Altova StyleVision Server 2014 This server has 2 CPU core s b Licenses for 2 CPU core s are required El Limit to single thread execution Max licensed CPU cores 0 Altova MapForce Server 2014 wa This server has 2 CPU core s ESA Rae ae eA RUE Max licensed CPU cores 0 F Limit to single thread execution w Request evaluation licenses Unregister server and all products In the screenshot below three Altova products have been registered with the Altova LicenseServer at DOC altova com How to assign licenses is described in the next section Assign Licenses to Registered Products Registering FlowForce Server via the FlowForce CLI Windows On Windows machines FlowForce Server can also be registered with an Altova LicenseServer on your network via the command line CLI by using the 1icenseserver command FlowForceServer licenseserver Server Or IP Address For example if LicenseServer is running on http localhost 8088 then register FlowForce Server with FlowForceServer licenseserver localhost If FlowForce Server was installed with other Altova server
119. gether mt change settings settings lt json encoded settings gt This URL can be sent as an email link to client users When the link is tapped server settings on the client are automatically updated See the MobileTogether Designer user manual for more information about generating this URL 2015 Altova GmbH Altova MobileTogether Server 64 4 9 Server Procedures How to Back Up and Restore MobileTogether Server How to Back Up and Restore MobileTogether Server This section describes how to back up and restore MobileTogether Server e Backing up MobileTogether Server consists of copying essential application data files and data files to a safe location e Restoring Mobile Together Server consists of copying the backed up files into place on the new installation e Updating client connections to the server These procedures are described below Backing up MobileTogether Server Before starting a backup MobileTogether Server must be stopped This is necessary in order to avoid inconsistency between the DB status of live files and backup files The MobileTogether Server files that need to be backed up are located by default in the application data folder see below The cfg configuration file can be edited with a text editor as an alternative to changing settings via the Web Administration Interface or the Command Line Interface The location of the application data folder depends on the operating system and platform and by
120. gether Server 2015 Altova GmbH Altova LicenseServer License Pool This section e Uploading a license e License status e Activating de activating and deleting a license e icons in the License Pool tab e License information e Note on cores and licenses Configuration Page Reference 169 The License Pool tab displays all the licenses that are currently on the LicenseServer see screenshot below When a license file is uploaded to the LicenseServer with the Upload button on this page all the licenses contained in the license file are placed in the license pool on the server and are displayed on the License Pool page The License Pool page displays information about all the licenses currently on the LicenseServer and thus provides a convenient overview of all Altova product licenses On this page you can also activate deactivate and delete selected licenses Ey Altova LicenseServer ALTOVA LicenseServer License Poo server Management Server Montring etings Messoges Loy Out He Status Name Company Mr Nobody Altova GmbH Mr Nobody Altova GmbH Active Mr Nobody Altova GmbH Inactive Mr Nobody Altova GmbH Inactive Mr Nobody Altova GmbH Deactivate Upload License File Upload Uploading a license Product Active Mr Nobody Altova GmbH Altova FlowForce Server Mr Nobody Altova GmbH Altova FlowForce Server Edition Version 2013 Key a Expires in day SMP days lef Altova MapForce Serv
121. gether Server 2015 Altova GmbH Altova LicenseServer How to Assign Licenses 145 Upload Licenses to LicenseServer This section e Uploading a license file to the license pool of LicenseServer e License status e Activating the licenses you wish to use e Next steps Uploading a license file to the license pool of LicenseServer After you have obtained a license file from Altova you must upload it to the Altova LicenseServer How to do this is described below Each license file can contain one or more licenses and depends on your purchase When you upload a license file all the licenses in it will be uploaded to LicenseServer and can be assigned to an Altova product that has been registered with that LicenseServer All the uploaded licenses from one or more license files and for all Altova products are collected in a license pool on the LicenseServer The license pool is displayed in the License Pool tab of the LicenseServer Configuration page screenshot below License files are uploaded to the LicenseServer using the Upload function of the License Pool tab see screenshot below ALTOVA LicenseServer License Poo Server Management Server Monitoring Settings Messages 0 Log Out Help Licenses E Status Name Company Product Edition Version Key Expires in days SMP days left License Type Upload License File Click the Browse button and select the license file you want The license file will appear
122. getherServer2 0 bin mobiletogetherserver Mac usr local Altova MobileTogetherServer2 0 bin mobiletogetherserver Usage and list of CLI commands General command line syntax for MobileTogetherServer is Windows MobileTogetherServer h help version lt command gt options arguments Linux mobiletogetherserver h help version lt command gt options arguments Mac mobiletogetherserver h help version lt command gt options arguments v Casing on the command line MobileTogetherServer on Windows mobiletogetherserver on Unix Linux Mac Note that lowercase mobiletogetherserver works on all platforms Windows Linux and Mac while upper lower MobileTogetherServer works only on Windows and Mac where h help Displays the help text Displays the version of MobileTogether Server 2015 Altova GmbH Altova MobileTogether Server Command Line Usage 105 Valid CLI commands are listed below and are explained in the sub sections of this section licenseserver Register MobileTogether Server with LicenseServer on the local network assignlicense Upload a license to LicenseServer and assign it to MobileTogether Server on this machine verifylicense Check if the current MobileTogether Server is licensed optionally check if a given license key is assigned Installs MobileTogether Server as a service Starts MobileTogether Server as a service Uninstalls MobileTog
123. guration page is opened with the login mask displayed screenshot below You can log in with the initial password of default After you have logged in you can change your password in the Settings tab ALTOVWA LicenseServer License Pool Server Management Server Monitoring Settings Messages Log Out Please enter password to log in Initial password is default jeoccece Login Setting a fixed or dynamic port for the Configuration page The port of the Configuration page Web Ul and consequently its address can be specified in the Settings page By default the port is 8088 You can set any other port you want for the LicenseServer Configuration page see screenshot below Alternatively you allow the port to be selected dynamically each time LicenseServer starts up In this case you will need to find out the URL of the Configuration page from the file webuI htm1 See Open LicenseServer Config Page Windows and Open LicenseServer Config Page Linux 2015 Altova GmbH Altova MobileTogether Server 140 Altova LicenseServer How to Assign Licenses Web UI Changing these settings will cause the LicenseServer to restart and any currently running and licensed applications will be shut down Configure the host addresses where the web UI is available to administrators All interfaces and assigned IP addresses Only the following hostname or IP address 0 0 0 0 Ensure this hostname or IP address exists or Lice
124. have already done this carry on to the next step Assign Licenses 2 Assign a license to your Altova product that has been registered with the LicenseServer Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer How to Assign Licenses 155 Register MapForce Server This section Registering MapForce Server from FlowForce Server Windows Registering a standalone MapForce Server Windows Registering MapForce Server Linux Next steps MapForce Server can be installed as part of the FlowForce Server package or as a standalone server product In either case it must be registered with Altova LicenseServer After it has been registered with LicenseServer you can assign a license to it from LicenseServer On Windows systems you can install MapForce Server as part of the FlowForce installation If MapForce Server is installed as part of the FlowForce Server package it will automatically be registered with LicenseServer when FlowForce is registered with LicenseServer On Linux systems the two products must be installed separately If MapForce Server is installed after FlowForce Server then it will be registered automatically when FlowForce Server is registered But if MapForce Server is installed before FlowForce Server you will have to register both products separately Registering MapForce Server from FlowForce Server Windows MapForce Server is packaged with FlowForce Server so when FlowForce Server is registered with
125. he LicenseServer can be specified in one of two ways e You can search for Altova LicenseServers that are currently available on the network that is those that are currently running Do this by clicking the Search for Altova LicenseServers button highlighted yellow in the screenshot below 2015 Altova GmbH 151 Altova MobileTogether Server 152 Altova LicenseServer How to Assign Licenses LicenseServer Enter address here or search for LicenseServer 2 The search returns a list of available Altova LicenseServers on the network One LicenseServer will be selected screenshot below and the others will be available in the dropdown list of the combo box Select the LicenseServer on which your FlowForce license is stored LicenseServer techwriter altova com Register with LicenseServer e Alternatively you can enter the address of the LicenseServer in the LicenseServer field If the currently running LicenseServers are available as a dropdown list you must click the Manually Enter Address button to be able to enter an address in the LicenseServer field After you have specified the LicenseServer click Register with LicenseServer The Altova server application will be registered with the specified LicenseServer and that LicenseServer s Configuration page will open in a browser with its Server Management tab active screenshot below Note You may need to allow pop ups in order for the LicenseServer Configuration pa
126. he setdeflang command short form is sa1 sets the default language of MobileTogether Server It takes a mandatory LanguageCode argument Examples An example of the setdeflang command mobiletogetherserver setdeflang DE The command above sets the default language for messages to German v Casing on the command line MobileTogetherServer on Windows mobiletogetherserver on Unix Linux Mac Note that lowercase mobiletogetherserver works on all platforms Windows Linux and Mac while upper lower MobileTogetherServer works only on Windows and Mac Supported languages 2015 Altova GmbH Altova MobileTogether Server 120 Command Line Usage setdeflang The table below lists the languages currently supported together with their language codes English Altova MobileTogether Server 2015 Altova GmbH Command Line Usage help 121 6 11 help This section e Command syntax e Command description e Examples e The help option Command syntax Windows MobileTogetherServer help Command Linux mobiletogetherserver help Command Mac mobiletogetherserver help Command Command description The help command takes a single argument Commana the name of the command for which help is required It displays the correct syntax of the command and other information relevant to the correct execution of the command Examples An example of the help command mobiletogetherserver help exportresourcestrings The
127. her Server Setup on Linux 27 Notes about Environment Folders Given below is a list of important folders in your MobileTogether Server setup a Installation root opt Altova MobileTogetherServer2 0 a Database License and Solution Files var opt Altova MobileTogetherServer Environment settings etc profile d jdbc sh The environment settings file must be defined according to your specific envronment The example path above serves only as a general guide Note The environment settings file sets the variables for all users on the system File based databases File based databases such as SQLite databases must reside in the folder defined in the Settings tab of MobileTogether Server as the Server Side s Solutions Working Directory By default this folder is var opt Altova MobileTogetherServer SolutionFiles JDBC Connections Note the following points e The Java Runtime Environment or SDK must be installed e The JDBC drivers for the target database must be installed e The following environment variables must be set correctly for your environment o CLASSPATH to find the jar files o PATH to find the JRE but might not be necessary depending on the installation o JAVA_HOME if necessary depending on the installation Note On Linux servers the only database connections supported are JDBC 2015 Altova GmbH Altova MobileTogether Server 28 Setting Up MobileTogether Server Setup on Linux Listing
128. if contact with a running product is lost SMTP Host and SMTP Port are the access details of the email server from which the email alert Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer Configuration Page Reference 185 will be sent User Authentication and User Password are the user s credentials for accessing the email server The From field takes the address of the email account from which the email will be sent The To field takes the recipient s email address Click Save when done After saving the Alert Mail settings email alerts will be sent to the address specified whenever a significant event occurs such as when connection to altova com is lost Note that such events are also recorded in the Messages tab and can be looked up there Miscellaneous settings Show hints for receiving and deploying evaluation licenses Checking this box see screenshot above displays at the top of the configuration page brief instructions about how to evaluate and deploy evaluation licenses Send a warning email if contact with a running product is lost A warning message is sent from the From address to the To address if a connection with a product that is licensed and running is lost 2015 Altova GmbH Altova MobileTogether Server 186 Altova LicenseServer Configuration Page Reference Messages Log Out The Messages tab displays all messages relevant to licenses in the license pool of the LicenseServer Each messa
129. ileTogether Server Altova LicenseServer LicenseServer versions Trial license Licensing on Mac OS X e Start LicenseServer e Start MobileTogether Server e Register MobileTogether Server e Assign a license Notes about Environment 2015 Altova GmbH Altova MobileTogether Server 30 Setting Up MobileTogether Server Setup on Mac OS X Installation on Mac OS X MobileTogether Server is available for installation on Mac OS Xsystems Its installation and setup procedure is described below v System requirements v Mac OSX Mac OS X 10 8 or newer Java for OS X latest version v Install Java for OS X You must install Java for OS X in order for MobileTogether Server to run The latest version at the time of writing Java for OS X 2014 001 is available at http support apple com kb DL1572 For the latest Java for OS X version provided by Apple when you install do a search for Java for OS X at the Apple website Note that this Java version for OS X might not be the latest Java version provided by Sun Microsystems but this is the version you need to install v FlowForce Server integration If you install MobileTogether Server together with FlowForce Server it is recommended that you install FlowForce Server first If you install MobileTogether Server before FlowForce Server then after having installed both MobileTogether Server and FlowForce Server run the following command cp usr local Altova MobileTogether
130. in the Upload License File text field and the Upload button will be enabled Click the Upload button to upload the license file All the licenses in the file are uploaded and displayed in the License Pool tab The screenshot below shows multiple licenses uploaded from multiple license files 2015 Altova GmbH Altova MobileTogether Server 146 Altova LicenseServer AJ Altova LicenseServer ALTOVA LicenseServer License Poo server anagement server Montrng Setngs Messages Log Out Hep Status Active Active Active Inactive Inactive Name Company Mr Nobody Altova GmbH Mr Nobody Altova GmbH Mr Nobody Altova GmbH Mr Nobody Altova GmbH Mr Nobody Altova GmbH Mr Nobody Altova GmbH Product Altova FlowForce Server Altova FlowForce Server Altova MapForce Server Altova RaptorXML XBRL Altova StyleVision Server Altova FlowForce Server Altova StyleVision Server Edition Version 2013 Key MMSUC1U HC139LF 3D78278 966PPHM DAST2WU How to Assign Licenses Expires in day SMP days lef 334 334 Deactivate Upload License File C FS36_License altova_licenses Upload License status License status values are as follows e Activating When a license is uploaded into the license pool of LicenseServer the server will transmit license related data to the altova com master licensing server to validate authenticate and activate the license that was supplied This is necessary to en
131. ings The Settings tab is divided into a General Settings pane and a LicenseServer pane The General Settings pane contains sub panes for various MobileTogether Server settings These sub panes and the LicenseServer pane are described separately below After changing any setting in the General Settings pane click Save for the setting to take effect v Host settings Specifies whether the server will use a specific IP address or all interfaces and IP addresses If a single IP address is to be used enter it in the Only the following IP address field Host settings Select the network adapters the server will use All interfaces and assigned IP addresses Only the following IP address v Mobile client ports The ports that mobile devices will use to connect to the server The HTTP port is the unsecure port HTTPS is the secure port To use HTTPS you need to set up SSL Encryption Mobile client ports Select unsecure HTTP and secure HTTPS ports the Mobile clients will use These ports cannot be used for administrative purposes v HTTP Port 8083 HTTPS Port 8084 v Administrator ports The administrator ports provide access for the following purposes e To connect to the server s Web UI and perform administrative functions such as setting up Users and Roles To deploy MobileTogether designs as MobileTogether solutions to the server MobileTogether Designer has a setting that specifies
132. ipal amp root amp workflow user amp TechWriter 01 amp root amp TechWriter 01 amp root B Deploy amp TechWriter 01 amp root a workflow designer Granted to and or inherited from Principals grantedto amp root granted to amp amp workflow user grantedto TechWriter 01 grantedto amp root grantedto TechWriter 01 grantedto amp root inherited from 4 amp workflow designer inherited from amp workflow designer grantedto amp root granted to amp workflow designer The Privileges by User Report screenshot below lists each user role with a summary of its privileges The inheritance is also displayed Privileges by User Report Principal Privilege B Deploy Open workflow from designer Read global resources Run server simulation Save workflow from designer Write global resources amp TechWriter 01 Manage server settings Open workflow from designer Read global resources 2015 Altova GmbH Granted to and or inherited from Principals inherited from 4 amp workflow designer inherited from amp workflow designer inherited from RR workflow designer inherited from 4 amp workflow designer inherited from 4 amp workflow designer grantedto Q amp TechWriter 01 grantedto Q amp TechWriter 01 inherited from amp workflow designer inherited from SQ workflow designer Altova MobileTogether Server 90 5 3 Web Ul Reference User Licenses User Lic
133. ironment Altova MobileTogether Server 2015 Altova GmbH Setting Up MobileTogether Server Setup on Linux 21 Installation on Linux MobileTogether Server is available for installation on Linux systems Its installation and setup procedure is described below v System requirements v Linux CentOS 6 or newer RedHat 6 or newer Debian 6 or newer Ubuntu 12 04 or newer Note that the Qt library version 4 available under GNU GPL and LGPL must be installed v FlowForce Server integration If you are installing MobileTogether Server together with FlowForce Server it is recommended that you install FlowForce Server first Otherwise after having installed both MobileTogether Server and FlowForce Server run the following command cp opt Altova MobileTogetherServer2 0 etc tool opt Altova FlowForceServer2016 tools This command copies the tool file from ete directory of MobileTogether Server to the FlowForce Server tools directory The tool file is required by FlowForce Server it contains the path to the MobileTogether Server executable You do not need to run this command if you install FlowForce Server before installing MobileTogether Server v Uninstall old versions of Altova server products If you need to uninstall a previous version do this as follows On the Linux command line interface CLI you can check which Altova server products are installed with the following command Debian Ubuntu dpkg list grep
134. is used to activate deactivate a license Click Save to finalize the change e Request Time Activation Time The times when a license is requested and activated respectively Search Click the Search button to open the Search dialog screenshot below and search by a combination of one or more user license fields any v ID equal 4 Device x equal v Samsung ID User Name Client Version Request Time Active Activation Time e The Any All combo box specifies whether all the rules you define must be satisfied or any one rule e The Add Rule icon next to the Any All combo box adds a rule to the search definition Each rule consists of three parts i a user license field ii a relationship definition and iii a value A submitted value must exactly match a value in the specified field to return a match An empty value part will use an empty string as that field s submitted value The Delete Rule icon next to each rule deletes that rule Click Find to start the search Click Reset to show all user licenses 2015 Altova GmbH Altova MobileTogether Server 92 Web UI Referenc 5 4 Log e Log The Log tab shows the logged actions according to the selected filters located at the top of the tab see screenshot below Log View Showlast 7 da 2014 04 14 Search Date User 2014 04 14 11 system 2014 04 14 11 system 2014 04 14 11 system 2014 04 13 02 system 2014 04 11 19 s
135. isted together with all the users roles that have that privilege v About Roles A role defines a set of privileges It can be assigned to another role or to a user A role s privileges automatically become the privileges of any other role or any user that the role is assigned to A user can be assigned any number of roles As a result a user will have all the privileges defined in the multiple assigned roles The following roles are predefined e authenticated is automatically assigned to every user except anonymous So user with a name and password is assigned the authenticated role e all is automatically assigned to every user including anonymous e workflow designer iS assigned to users that design workflows in MobileTogether Designer This role allows a user to open and save workflows as well as to runa simulation on the server e workflow user is assigned to users running the workflow on a mobile device This role allows the user to access the servce interface without needing to log in to the server and start the solution on the client 2015 Altova GmbH Altova MobileTogether Server 80 Web UI Reference Users and Roles v Creating a user A new user can be created by root user or any user that has the Maintain users roles and privileges privilege Create a new user as follows 1 Inthe Users and Roles Users tab click Create User see screenshot below This displays the Create User page Users Name amp TechWriter
136. it to a user directory called MyAltova that is located say in the home User directory then switch to this directory as follows cd home User MyAltova Install MobileTogether Server with the following command Debian sudo dpkg install mobiletogetherserver 2 0 debian deb Ubuntu sudo dpkg install mobiletogetherserver 2 0 ubuntu deb CentOS sudo rpm ivh mobiletogetherserver 2 0 1 x86_64 rpm RedHat sudo rpm ivh mobiletogetherserver 2 0 1 x86_64 rpm The MobileTogether Server package will be installed in the folder opt Altova MobileTogetherServer2 0 v Altova LicenseServer In order for any Altova Server product including MobileTogether Server to run that server product must be licensed via an Altova LicenseServer on your network On Linux systems Altova LicenseServer will need to be installed separately Download LicenseServer from the Altova website and copy the package to any directory on the Linux system Install it just like you installed MobileTogether Server see previous step Debian sudo dpkg install licenseserver 1 23 debian deb Ubuntu sudo dpkg install licenseserver 1 23 ubuntu deb CentOS sudo rpm ivh licenseserver 1 23 1 x86_64 rpm RedHat sudo rpm ivh licenseserver 1 23 1 x86_64 rpm Altova MobileTogether Server 2015 Altova GmbH Setting Up MobileTogether Server Setup on Linux 23 The LicenseServer package will be installed in opt Altova LicenseServer For information about h
137. ix 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 Altova MobileTogether Server 2015 Altova GmbH Chapter 5 Web UI Reference 68 Web Ul Reference 5 Web UI Reference MobileTogether Server has a Web User Interface Web Ul with which you can easily configure MobileTogether Server The Web UI can be opened in any Internet browser on any of the supported operating systems Accessing the Web UI of MobileTogether Server The MobileTogether Server Web UI is accessed as follows v On Windows To access the Web UI click the ServiceController icon in the system tray see screenshot below hover over Altova MobileTogether Server in the menu that pops up and then select Configure from the MobileTogether Server submenu If MobileTogether Server is not already running use the Start Service option to start MobileTogether Server BD Altova FlowForce Server ie Altova FlowForce Web Al Altova LicenseServer G Altova MobileTogether Server gt Altova MobileTogether Server E moane O ooe Z Altova RaptorXML XBRL Server Start service Exit Altova ServiceController Stop service Run Altova ServiceController at startup A i 1 11 00 AM m To sign in enter the
138. licenses to registered products ALTOVWA LicenseServer Server Management Er een aes PON ee Red DOC altova com Altova FlowForce Server 2014 This server has 2 CPU core s Key Code CPU Cores Licenses for 2 CPU core s are required oe Meena enn Limit to single thread execution Altova StyleVision Server 2014 This server has 2 CPU core s Key Code CPU Cores Licenses for 2 CPU core s are required El Limit to single thread execution Altova MapForce Server 2014 This server has 2 CPU core s iii SRC ASN eA RRR Aiax licensed CPU cores 0 El Limit to single thread execution Max licensed CPU cores 0 w Request evaluation licenses Unregister server and all products Note the following points about the Server Management tab e Each product is listed under the name of its client machine In the screenshot above one client machine named Doc altova com has three Altova products registered with the LicenseServer If an Altova product on a different client machine is registered with this LicenseServer then that client machine with its registered products will also be listed in Altova Mobile Together Server 2015 Altova GmbH Altova LicenseServer Configuration Page Reference 175 the Server Management tab e Each registered Altova product on a client machine has its own Key Code entry which takes the key code of a license A registered product s key code is assigned by clicking its Edit Assigned License
139. lients to use SSL In MobileTogether Client apps that communicate with an SSL enabled MobileTogether Server enable SSL communication by checking the SSL Encryption checkbox See the MobileTogether Client documentation for information about how to find this check box Altova MobileTogether Server 2015 Altova GmbH Chapter 4 Server Procedures 44 Server Procedures 4 Server Procedures This section describes important server procedures It assumes that MobileTogether Server has already been licensed Note however that in order for MobileTogether Server to be accessed both LicenseServer and MobileTogether Server must be started and running as services Start Altova LicenseServer Start MobileTogether Server Set Up SSL Encryption Set Administrator and Mobile Client Ports Users and Roles Available Privileges Configure the Firewall Information for Clients How to Back Up and Restore MobileTogether Server Altova MobileTogether Server 2015 Altova GmbH Server Procedures Start Altova LicenseServer 4 1 2015 Altova GmbH Start Altova LicenseServer In order to run an installation of an Altova server product i gt Server ii RaptorXML XBRL Server iii MobileTogether Server iv MapForce Server v StyleVision Server that installation must be licensed with an Altova LicenseServer on your network LicenseServer must be running continuously as a servce in order for all connected MobileTogether Server
140. ltova server products will work with newer versions of LicenseServer So if you are installing a new version of an Altova server product and if your current LicenseServer version is not the latest de install the older version of LicenseServer and install the latest version All registration and licensing information held in your older version of LicenseServer will be saved at the time of de installation to a database on the server and will be imported automatically into the newer version The version number of the LicenseServer that is appropriate for any particular version of a server product is displayed during the installation of that server product You can choose to install this version along with the server product The version of the currently installed LicenseServer is given at the bottom of the LicenseServer configuration page Icons in the Server Management tab Edit Assigned Licenses Available with each product Pops up the Manage Licenses dialog in which new licenses can be assigned to the product and already assigned licenses can be edited P o Show Licenses Appears with each license Switches to the License Pool tab and highlights the selected license so that license details can be read Unregister This Product Available with each product The selected product on the selected client machine will be unregistered from LicenseServer Note on cores and licenses The licensing of Altova server products is based on th
141. ment tab of the configuration page of LicenseServer Go there and assign a license to MobileTogether Server Note on cores and licenses The licensing of Altova server products is based on the number of processor cores available on the product machine for MobileTogether Server an additional licensing option is available see below For example a dual core processor has two cores a quad core processor four cores a hexa core processor six cores and so on The number of cores licensed for a product must be greater than or equal to the number of cores available on that server machine whether the server is a physical or virtual machine For example if a server has eight cores an octa core processor you must purchase at least one 8 core license You can also combine licenses to achieve the core count So two 4 core licenses can also be used for an octa core server instead of one 8 core license If you are using a computer server with a large number of CPU cores but only have a low volume to process you may also create a virtual machine that is allocated a smaller number of cores and purchase a license for that number Such a deployment of course will have less processing speed than if all available cores on the server were utilized Note Each license can be used for only one client machine at a time even if the license has unused licensing capacity For example if a 10 core license is used for a client machine that has 6 CPU cores th
142. mentation Examples Examples of the verifylicense command mobiletogetherserver verifylicense mobiletogetherserver verifylicense license key ABCDEFG HIJKLMN OPORSTU VWXYZ12 3456789 The commands above check respectively whether the product has been licensed and whether the product has been licensed with the license key given as the value of the license key option v Casing on the command line MobileTogetherServer on Windows mobiletogetherserver on Unix Linux Mac Note that lowercase mobiletogetherserver works on all platforms Windows Linux and Mac while upper lower MobileTogetherServer works only on Windows and Mac Altova MobileTogether Server 2015 Altova GmbH Command Line Usage verifylicense Windows only 111 Command options Options are listed in their short forms in the first column and long forms second column together with their descriptions third column On the command line one or two dashes can be used for both short and long forms 1 license key Checks whether the submitted license key has already been assigned to the product Form 1icense key VALUE 2015 Altova GmbH Altova MobileTogether Server 112 Command Line Usage install 6 4 _ install This section e Command syntax e Command description e Examples Command syntax Windows MobileTogetherServer install Linux mobiletogetherserver install Mac mobiletogetherserver install Command description
143. mobiletogetherserver 1i Contains the address of the LicenseServer and failover if one is esvr specified Restoring MobileTogether Server To restore a previous configuration of MobileTogether Server from backup files see above do the following 1 Install the same version of MobileTogether Server as that from which you backed up see above 2 Stop MobileTogether Server 3 Copy the backed up files see above into the correct folders on the new installation 4 Start MobileTogether Server Updating client connections to the server If you have moved MobileTogether Server to another machine with new settings such as a new IP address client device settings to connect to MobileTogether Server must be updated See Information for Clients for details 2015 Altova GmbH Altova MobileTogether Server 66 Server Procedures Frequently Asked Questions 4 10 Frequently Asked Questions v There are several work flows 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 work flow 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 Inform
144. n Altova ServiceController at startup Pa E T rN a gt 11 00 AM Starting and stopping Altova services Each installed Altova service component will have an entry in the ServiceController menu see screenshot above An Altova service can be started or stopped via a command in its ServiceController sub menu Additionally important administration tasks of individual services can be accessed via the ServiceController menu In the screenshot above for example Altova LicenseServer service has a sub menu in which you can choose to access LicenseServer s Configuration page via the Configure command Altova Mobile Together Server 2015 Altova GmbH Altova LicenseServer How to Assign Licenses 135 7 6 How to Assign Licenses To assign an Altova server product a license using Altova LicenseServer do the following 1 Start LicenseServer 2 Open the LicenseServer Configuration page which is the administrator s interface with LicenseServer on Windows Linux or Mac OS X 3 Upload the license s you have received from Altova to the license pool of your Altova LicenseServer Do this in the License Pool tab of the LicenseServer Configuration page 4 Register the Altova server product FlowForce Server MapForce Server StyleVision Server RaptorXML XBRL Server with LicenseServer Depending on the product s type the method of registering it with LicenseServer will be different either via the product s Web UI or its command lin
145. n com support ss certificates support index page content amp id AR657 amp actp LIS T amp viewlocale en_US e Verisign s intermediate certificates for its Secure Site product https knowledge verisign com support ssl certificates support index page content amp id AR1735 Copy paste both intermediate certificates primary and secondary into separate text files and save them on your computer 7 Combine certificates in one public key certificate file You now have three certificate files e Public key mycertificate cer e Secondary intermediate certificate e Primary intermediate certificate Each contains text blocks bracketed by lines that look like this BEGIN CERTIFICATE END CERTIFICATE Now copy paste all three certificates into one file so that they are in sequence The order of the sequence is important i public key ii secondary intermediate certificate iii primary intermediate certificate Ensure that there are no lines between certificates BEGIN CERTIFICATE public key from mycertificate cer see Step 5 END CE IF ICATE BEGI ERTIFICATE secondary intermediate certificate see Step 6 IFICATE ERTIFICATE intermediate certificate see Step 6 IF ICATE prima END CE i Z iw Q mS Q W Qa ve Save the resulting combined certificate text to a file named publi
146. n the Logging to File option ts enabled V Read global resources WI Write global resources V Open workflow from designer V Save workflow from designer V Run server simulation The tab Users and Roles Reports Privileges Report provides a list of all privileges with each privilege being listed together with all the users roles that have that privilege v About Roles A role defines a set of privileges It can be assigned to another role or to a user A role s privileges automatically become the privileges of any other role or any user that the role is assigned to A user can be assigned any number of roles As a result a user will have all the privileges defined in the multiple assigned roles The following roles are predefined Altova MobileTogether Server 2015 Altova GmbH Web Ul Reference Users and Roles 77 e authenticated is automatically assigned to every user except anonymous SO user with a name and password is assigned the authenticated role e allis automatically assigned to every user including anonymous e workflow designer is assigned to users that design workflows in MobileTogether Designer This role allows a user to open and save workflows as well as to runa simulation on the server e workflow user is assigned to users running the workflow on a mobile device This role allows the user to access the service interface without needing to log in to the server and start the solution on the clie
147. n the Activity Monitor in Finder and make sure that LicenseServer is not in the list Then proceed to uninstall in the same way as described above for MobileTogether Server v Download the disk image file Download the disk image dmg file from the Altova website http www altova com download html v Install MobileTogether Server Click to open the downloaded disk image dmg This causes the MobileTogether Server installer to appear as a new virtual drive on your computer On the new virtual drive double click the installer package pkg Go through the successive steps of the installer wizard These are self explanatory and include one step in which you have to agree to the license agreement before being able to proceed To eject the drive after installation right click it and select Eject The MobileTogether Server package will be installed in the folder usr local Altova MobileTogetherServer2 0 application binaries var Altova MobileTogetherServer data files database and logs MobileTogether Server server daemon starts automatically after installation and a re boot of the machine You can start MobileTogether Server as a daemon with the following commana sudo launchctl load Library LaunchDaemons com altova MobileTogetherServer2 0 plist After starting MobileTogether Server server daemon you can open the Web UI page of MobileTogether Server in order to configure MobileTogether Server Open the Web UI page by going
148. ne at a time even if the license has unused licensing capacity For example if a 10 core license is used for a client machine that has 6 CPU cores then the remaining 4 cores of licensing capacity cannot be used simultaneously for another client machine MobileTogether Server licenses Two types of MobileTogether Server license are available Customers can select a license type that best suits their requirements e Core licenses These are assigned to MobileTogether Servers on the basis of the cores on the server machine see the explanation above An unlimited number of MobileTogether Client devices can then connect to the server e User licenses These specify the maximum number of users MobileTogether Client devices that are allowed to connect to the MobileTogether Server at one time 2015 Altova GmbH Altova MobileTogether Server 136 Altova LicenseServer How to Assign Licenses Start LicenseServer This section e How to start LicenseServer on Windows systems e How to start LicenseServer on Linux systems e How to start LicenseServer on Mac OS X systems e Note about Connection to altova com Windows systems You can start LicenseServer via the Altova ServiceController which is available in the system tray First click Start All Programs Altova LicenseServer Altova ServiceController to start Altova ServiceController and display its icon in the system tray see screenshot below f you select the Run Altova ServiceControll
149. next e The dialog displays all the currently active licenses for that product in the license pool In our screenshot there is one currently active RaptorXML XBRL Server license in the license pool LicenseServer will automatically detect from each license in the pool the product for which it has been issued e The license type can be either Cores all Altova server products including MobileTogether Server or Users MobileTogether Server only The license type is shown in the License Type column e The license in the screenshot above has been licensed for 16 CPU cores e You need to know the number of processor cores on the server on which the Altova server product has been installed If the machine has a dual core processor you need a two core the CPU Cores count license How many cores the registered server product requires is listed below the machine name The license you assign to this server must be valid for a sufficient number of cores Note that you can combine licenses to reach the required number of cores So if the machine s processor is octa core eight core you can combine two 4 core licenses e The Manage Licenses dialog will list only currently active licenses for that product Licenses for other Altova products will not be listed e Licenses that have been assigned already for example to another installation of the product on the network will have their check boxes checked So only unchecked licenses may be selected
150. nseServer will fail to start Configure the port used for the web UI Dynamically chosen by the operating system Fixed port 8088 Ensure this port is available or LicenseServer will fail to start The advantage of a fixed port is that the page URL is known in advance and therefore can be accessed easily If the port is assigned dynamically the port part of the URL will have to be looked up in the file webUI htm1 each time LicenseServer is started Altova Mobile Together Server 2015 Altova GmbH Altova LicenseServer How to Assign Licenses 141 Open LicenseServer s Config Page Linux This section Opening the Configuration page for the first time with the returned URL URL of the LicenseServer Configuration page Logging in with the initial password Setting a fixed port for the Configuration page Opening the Configuration page for the first time with the returned URL On Linux systems when you register your Altova server product with LicenseServer via the CLI the URL of the LicenseServer Configuration page is returned On opening this URL in a browser you are prompted to read and accept the license agreement After accepting the license agreement the Configuration page s login mask is displayed screenshot below URL of the LicenseServer Configuration page To open the LicenseServer Configuration page at any time enter its URL in the address bar of a browser and press Enter By default the URL of the Configuration p
151. nt 2015 Altova GmbH Altova MobileTogether Server 78 Web Ul Reference Users and Roles Users The Users and Roles Users tab screenshot below displays all users and enables you to create new users access a user s properties by clicking a user name and delete users Users Name amp TechWriter O1 amp anonymous amp root Create User Import Domain Users v About Users A user is defined by a name and password combination Users access MobileTogether Server in two ways e Web Ul access The Web Ul is the administrative interface of MobileTogether Server Logging in to the Web UI requires a name and password combination it is therefore done as a user Service interface The HTTP service interface exposes MobileTogether Server services typically to the MobileTogether Client app on a mobile device A user accesses the servce interface using a name and password combination The services exposed relate typically to access to MobileTogether solutions and their related data Two special users are predefined root is the initial administrator user It is initially the most powerful user having all privileges and having the ability to add other users and to set roles Its initial name password combination is root root The password can be changed at any time anonymous anonymous is an account for anonymous users that access services exposed via the HTTP serice interface It cannot be used for logging in
152. number Such a deployment of course will have less processing speed than if all available cores on the server were utilized Note Each license can be used for only one client machine at a time even if the license has Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer Configuration Page Reference 173 unused licensing capacity For example if a 10 core license is used for a client machine that has 6 CPU cores then the remaining 4 cores of licensing capacity cannot be used simultaneously for another client machine MobileTogether Server licenses Two types of MobileTogether Server license are available Customers can select a license type that best suits their requirements e Core licenses These are assigned to MobileTogether Servers on the basis of the cores on the server machine see the explanation above An unlimited number of MobileTogether Client devices can then connect to the server e User licenses These specify the maximum number of users MobileTogether Client devices that are allowed to connect to the MobileTogether Server at one time 2015 Altova GmbH Altova MobileTogether Server 174 Altova LicenseServer Configuration Page Reference Server Management This section e Icons in the Server Management tab e Assigning licenses e One client machine under different names e Requesting an evaluation license e Unregistering products In the Server Management tab screenshot below you can assign
153. nux and Mac while upper lower MobileTogetherServer works only on Windows and Mac Altova MobileTogether Server 2015 Altova GmbH Command Line Usage exportresourcestrings 117 6 9 exportresourcestrings This section e Command syntax e Arguments e Command description e Examples e Creating localized versions of Mobile Together Server Command syntax Windows MobileTogetherServer exportresourcestrings LanguageCode XMLOutputFile Linux mobiletogetherserver exportresourcestrings LanguageCode XMLOutputFile Mac mobiletogetherserver exportresourcestrings LanguageCode XMLOutputFile Arguments The exportresourcestrings command takes the following arguments LanguageCode Specifies the language of resource strings in the exported XML file Supported languages are en de es fr ja XMLOutputFile Specifies the location and name of the exported XML file Command description The exportresourcestrings Command outputs an XML file containing the resource strings of the MobileTogether Server application It takes two arguments i the language of the resource strings in the output XML file and ii the path and name of the output XML file Allowed export languages with their language codes in parentheses are English en German de Spanish es French r and Japanese ja Examples 2015 Altova GmbH Altova MobileTogether Server 118 Command Line Usage exportresourcestrings An example of the export
154. oading licenses 145 169 User licenses administration of 90 User login and domain specific passwords 96 importing user domains for 96 Users 56 assigning roles to 78 creating new 78 deleting 78 managing 78 W Web browsers enabling execution of solutions for 96 Windows installation on 14 licensing on 16 Workflows 70 2015 Altova GmbH 191
155. obileTogether Server Serves MobileTogether solutions to MobileTogether Client apps installed on mobile devices See the section Server Procedures for descriptions of server administration tasks e MobileTogether Client app for mobile devices Connects to a MobileTogether Server and accesses the MobileTogether solutions deployed on that server See the MobileTogether Client app user manual MobileTogether Server Deploy MTD file and l ime optionally data fijes MobileTogether Designer to Mobile Together Server 4 Create Mobile Together Design MTD file in Mobile Together Designer MobileTogether Client Device Server MobileTogether Client app installed iOS Android MTD file and data to Windows Mobile client User input to Windows server and data files HTML Client app accesses Windows MTD file on server System requirements v MobileTogether Designer 2015 Altova GmbH Altova MobileTogether Server 8 Introduction MobileTogether Overview XP SP2 for x64 SP3 for x86 Vista 7 8 10 v MobileTogether Server XP SP2 for x64 SP3 for x86 Vista 7 8 10 Linux CentOS 6 or newer RedHat 6 or newer Debian 6 or newer Ubuntu 12 04 or newer v MobileTogether Client 6 and higher for Apple mobile devices 4 0 and higher for Android mobile devices Windows Mobile Windows Phone 8 for Windows phones Windows RT Metro Windows 8 10 Windows RT for Windows touch enabled PCs and tablet computers
156. of important files The following shell script is copied to the folder opt Altova MobileTogetherServer2 0 etc SO as not to overwrite already existing configuration files Make the necessary changes as required The parts highlighted in blue are envronment specific and will need to be adjusted to match your environment Shell script jdbc environment export PATH usr local jdk1 7 0_17 bin usr lib64 qt 3 3 bin usr local bin bin usr bin usr local sbin usr sbin sbin home qa bin export JAVA_HOME usr local jdk1 7 0_17 export CLASSPATH usr local jdbc oracle ojdbc6 jar usr local jdbc oracle xdb jar usr local jdbc oracle xmlparserv2 jar usr local jdbc postgre postgresql 9 0 801 jdbc4 jar usr local jdbc mssql sqljdbc4 jar usr local jdbc iseries lib jt400 jar usr local jdbc mysql mysql connector java 5 1 16 bin jar usr local jdbc sqlite sqlitejdbc v056 jar usr local jdbc Informix_JDBC_Driver lib ifxjdbc jar usr local jdbc sybase jconn7 jconn4 jar usr local jdbc db2 db2jcc jar usr local jdbc db2 loys ioe _Ilaliceiose CU ewes 4 1 3 Altova MobileTogether Server 2015 Altova GmbH Setting Up MobileTogether Server Setup on Mac OSX 29 3 3 Setup on Mac OS X This section describes the installation and licensing of MobileTogether Server on Mac OS X systems Installation on Mac OS X e System requirements Uninstall old versions of Altova server products Download the Mac OS X package Install Mob
157. oles in the Users and Roles Roles tab To see a listing of all the privileges of a role go to the tab Users and Roles Reports Privileges by User v Assigning members users or other roles to a role Altova MobileTogether Server 2015 Altova GmbH Web Ul Reference Users and Roles 85 Roles can have members which can be either users or other roles Members inherit the privileges of its parent role To assign a member to a role go to the Members pane at the bottom of the role s Properties page screenshot below Members Users Roles available Members of role workflow designer Name Name Tech vl amp Deploy m amp TechWriter 01 Assign gt gt amp anonymous amp root lt lt Remove BR workflow user All available users roles are listed on the left All users roles that are members of the role are listed on the right Select the user role from the list on the left that you want to assign as a member and click Assign To remove an assigned user role select it in the list on the right and click Remove The screenshot above for example shows the Members pane of the workflow designer role It has a single member the role Deploy which will inherit all the privileges of the workflow designer role Note that you can give a user or a role multiple sets of privileges If a user role is added as a member of multiple roles it will inherit the privileges of all its parent roles To s
158. on is set to Manual a newly connected mobile device is shown in the list of connected devices It will be licensed only when an administrator checks the device s Active check box and clicks Save e Once the user license limit is reached no more devices can be licensed In order to license additional devices an existing license must first be deactivated An administrator can activate and deactivate devices at any time so that new devices can be licensed without exceeding the user license limit User license fields Given below is a description of the fields of the user license tab e Licensing mode Auto automatically activates a license for a newly connected device provided one is free Manual requires that the administrator manually activate a license for a device and then save the setting for the activation to take effect e D The internal number assigned to the licensed device e User Name The user name with which the client device made the connection and logged Altova MobileTogether Server 2015 Altova GmbH Web Ul Reference User Licenses 91 in The user name determines the privileges that are extended to the client device e Device The mobile device or browser that requested the license e Client Version The version of the MobileTogether Client app on the client device Knowing the client version can be important for debugging and troubleshooting errors that might occur on the client device e Active The Active check box
159. or the certificate select publickey cer created in Step 7 e Click Save at the bottom of the General Settings section to save your changes 9 Set the server s HTTPS port After installing the SSL certificate you can specify a server port for SSL client communication Do this as follows e Log in to the MobileTogether Server UI by default on port 8085 of your server e Go to the Settings tab e Under Mobile Client Ports see screenshot below enable and specify the HTTPS port Mobile client ports Select unsecure HTTP and secure HTTPS ports the Mobile clients will use These ports cannot be used for administrative purposes V HTTP Port 8083 E HTTPS Port 8084 Make sure that any firewall is set up to allow access to MobileTogether Server through the HTTPS port 10 Test SSL communication 2015 Altova GmbH Altova MobileTogether Server 42 Setting Up MobileTogether Server Setting Up SSL Encryption You can now use any SSL testing tool to check whether secure communication with your server via HTTPS is working properly For example this can be done witha browser using the following SSL test site https ssltools websecurity symantec com checker views certCheck jsp This will tell you i whether the public key certificate file was properly constructed with the intermediate trust chain in Step 7 and ii whether your server can be reached properly through the firewall 11 Enable MobileTogether C
160. orXML XBRL and Altova MobileTogether Server If LicenseServer is not installed on your system at the time an Altova server product is installed the option to install LicenseServer is selected by default during installation setup If LicenseServer is already installed the option to install it is deselected by default You can change the default option if you like For information about how to proceed with assigning licenses see the section How to Assign Licenses System requirements v Windows Windows XP SP2 for x64 SP3 for x86 Windows Vista Windows 7 Windows 8 Windows 10 v Windows Server Windows Server 2008 R2 or newer v LicenseServer versions and their compatibility with Altova server products New versions of Altova server products can only be licensed with the version of LicenseServer that is the latest at the time of the server product s release However older versions of Altova server products will work with newer versions of LicenseServer So if you are installing a new version of an Altova server product and if your current LicenseServer version is not the latest de install this older version and install the latest version available on the Altova website All registration and licensing information held in your older version of LicenseServer will be saved at the time of de installation to a database on your server machine and will be imported automatically into the newer version When you install a newer version of Li
161. ou to the container s Permissions page screenshot below Workflows 73 Permissions for public contacts User or Role name Permissions Container amp anonymous Workflow Security Container authenticated Workflow Security Container Workflow Security Add Permissions Read Write Read Write Use Read Read Read Write Use Read Read Write Read Write Use Read Write inherited from mm public inherited from D public inherited from D public inherited from D inherited from 5 inherited from EQ inherited from B authenticated inherited from 2 To edit the access rights of an already permitted user role click its Change button To add permissions for a new user role click Add Permissions Both these buttons open the Edit Permissions pane Edit Permissions User or Role Deploy role Container Read Write Workflow Inherit Security Inherit Save Changes Discard Changes Set for all Inherit Full access No access 3 Select a user role If you are editing existing permissions permissions will be inherited from this user role If you are adding permissions this user role will be added to the permitted users roles list of this container 2015 Altova GmbH Altova MobileTogether Server 74 Web Ul Reference Workflows 4 Change the permissions as required The nherit option causes permissions to be inherited from the
162. ova Mobile Together Server 2015 Altova GmbH Altova LicenseServer How to Assign Licenses 147 information and any other relevant data These statuses are summarized in the table below Activating On upload license information is sent to altova com for verification Refresh the browser to view the updated status Verification and activation can take a few minutes Failed Verification A connection to altova com could not be made After establishing a connection either restart the service or activate the license with the Activate button Active Verification was successful the license is active Inactive Verification was successful but the license is on another LicenseServer on the network Licenses can be made inactive with the Deactivate button Blocked Verification was not successful License is invalid and is blocked Contact Altova Support Note After a license has been sent to altova com for verification the browser must be refreshed to see the updated status Verification and activation can take a few minutes Note If a connection to altova com could not be made the status will be Failed Verification After establishing a connection either restart the service or try activating the license with the Activate button Note When a license is given a status of Inactive or Blocked a message explaining the status is also added to the Messages log Only an active license can be assigned to a product installation
163. ow to register MobileTogether Server with Altova LicenseServer and license it see the section Licensing on Linux v LicenseServer versions Altova server products must be licensed either with the version of LicenseServer that is appropriate to the installed MobileTogether Server version or with a later version of LicenseServer The LicenseServer version that is appropriate for a particular version of MobileTogether Server is displayed during the installation of MobileTogether Server You can install this version of LicenseServer along with MobileTogether Server or you can install LicenseServer separately Before installing a newer version of LicenseServer any older one must be de installed The LicenseServer installer will do this automatically if it detects an older version LicenseServer versions are backwards compatible They will work with older versions of MobileTogether Server If you install a new version of MobileTogether Server and if your installed LicenseServer version is older than the appropriate LicenseServer install the latest version available on the Altova website At the time of LicenseServer de installation all registration and licensing information held in the older version of LicenseServer will be saved to a database on your server machine This data will be imported automatically into the newer version when the newer version is installed The version number of the currently installed LicenseServer is given at the bo
164. parent container Altova MobileTogether Server 2015 Altova GmbH Web Ul Reference Users and Roles 75 5 2 Users and Roles The Users and Roles tab screenshot below has four sub tabs These sub tabs work together to enable user accounts to be administered User accounts can be set up and configured for privileges and summaries of accounts and privileges can be viewed in the Reports sub tab See the sub sections for detailed descriptions Workflows Usersand Roles User licenses Settings Administration Users T Roles Password Policies Reports Users Name amp TechWriter 01 amp anonymous amp root Create User Import Domain Users v About Users A user is defined by a name and password combination Users access MobileTogether Server in two ways e Web Ul access The Web Ul is the administrative interface of MobileTogether Server Logging in to the Web UI requires a name and password combination it is therefore done as a user Service interface The HTTP service interface exposes MobileTogether Server services typically to the MobileTogether Client app on a mobile device A user accesses the service interface using a name and password combination The services exposed relate typically to access to MobileTogether solutions and their related data Two special users are predefined root is the initial administrator user It is initially the most powerful user having
165. policy A password policy can be applied to a user by adding the user as a member of the policy in the Members pane at the bottom of the policy s Properties page see screenshot below Members Users available Members of policy MediumSecurity E Name Current Policy Assign gt gt Name ajl B Default for new users null wa TechWriter 01 E B root null lt lt Remove All available users are listed on the left All users that are members of the policy are listed on the right Select the user that you want to assign as a member from the list on the left and click Assign To remove an assigned user select it in the list on the right and click Remove The screenshot above for example shows the Members pane of the MediumSecurity policy It has a single member the user TechWriter 01 Altova MobileTogether Server 2015 Altova GmbH Web Ul Reference Reports Users and Roles 89 The Users and Roles Reports tab provides links to reports about privileges These reports are useful summaries of what users roles use what privileges v Privileges Report The Privileges Report screenshot below lists each privilege together with all the users and roles that use that privilege The inheritance is also displayed Privileges Report Privilege Allow to use stored password on client Maintain users roles and privileges Manage server settings Open workflow from designer v Privileges by User Report Princ
166. process After the authorization and enrollment process has been completed you will get an email containing the public key of your SSL certificate The public key will be in plain text form or attached as a cer file 5 Save public key to file For use with MobileTogether Server the public key must be saved in a cer file If the public key was supplied as text copy paste all the lines from B EGIN C ERTIFICATI END C ERTIFICATI ay Dy into a text file that we will call myeertificate cer 6 Save CA s intermediate certificates to file To complete your SSL certificate you will need two additional certificates the primary and secondary intermediate certificates Your certificate authority CA will list content of intermediate certificates on its website Altova MobileTogether Server 2015 Altova GmbH Server Procedures Set Up SSL Encryption 51 e Verisign s intermediate certificates https knowledge verisign com support ssl certificates support index page content amp id AR657 amp actp LIST amp viewlocale en_US e Verisign s intermediate certificates for its Secure Site product https knowledge verisign com support ssl certificates support index page content amp id AR1735 Copy paste both intermediate certificates primary and secondary into separate text files and save them on your computer 7 Combine certificates in one public key certificate file You now have
167. r Activating the check box allows workflow simulations to be performed on the server for users granted the Run server simulation privilege Workflow simulation on server Enable workflow simulation on the server for users granted the Run server simulation privilege v Simulation on server v Workflow execution Activating the check box allows workflow execution to be performed from web browsers Workflow execution Enable workflow execution from web browsers Workflow execution from web browsers Altova Mobile Together Server 2015 Altova GmbH Web UI Reference Settings 99 v Sessions Sets the timeout period in minutes before a new logon has to be performed This timeout applies to both administrator access as well as client access Sessions v Server side solution s working directory When solutions are run on the server this setting specifies the following e The base URI of all relative paths in the design In a design the paths of all files that are not deployed to the server will be resolved relative to the directory specified in this setting For example if a file in the design is addressed with a relative path of MTSData Test xm1 then if the file is not deployed it must be located at lt Working Directory Setting Of Server gt MTSData Test xml If the file is deployed to the server the design uses internal mechanisms to access the files e
168. r submenu see screenshot above v On Linux To start LicenseServer as a service on Linux systems run the following command in a terminal window 45 Altova MobileTogether Server 46 Server Procedures Debian Ubuntu CentOS 7 RedHat CentOS 6 sudo sudo sudo sudo sudo Start Altova LicenseServer etc init d licenseserver start initctl start licenseserver initctl start licenseserver systemctl start licenseserver initctl start licenseserver If you need to stop LicenseServer replace start with stop in the above commands v On Mac OS X To start LicenseServer as a service on Mac OS Xsystems run the following command ina terminal window sudo launchctl unload Library LaunchDaemons com altova LicenseServer plist If at any time you need to stop LicenseSerer use sudo launchctl unload Library LaunchDaemons com altova LicenseServer plist Altova MobileTogether Server 2015 Altova GmbH Server Procedures Start MobileTogether Server 47 4 2 Start MobileT ogether Server In order to run MobileTogether Server MobileTogether Server must be started as a service Additionally in order to use the Web UI of MobileTogether Server it too must be started as a service How to do this explained below v On Windows You can start MobileTogether Server via the Altova ServiceController which is available in the system tray First click Start All Programs Altova LicenseS
169. ration page if LicenseServer is on the same machine Opening the Configuration page if LicenseServer is on another machine Logging in with the initial password Setting a fixed port for the Configuration page Opening the Configuration page if LicenseServer is on the same machine On Windows systems if LicenseServer is on the same machine you can open the Configuration page of LicenseServer in one of two ways Click Start All Programs Altova LicenseServer LicenseServer Configuration Page The Configuration page opens in a new tab of your Internet browser Click the Altova ServiceController icon in the system tray mouse over Altova LicenseServer in the menu that pops up see screenshot below and then select Configure from the LicenseServer submenu Altova FlowForce Server Altova FlowForce Web 2 Altova LicenseServer a comae D Altova MobileTogether Server Start service Altova RaptorXML XBRL Server Stop service Exit Altova ServiceController Run Altova ServiceController at startup EES a i 1 11 00 AM The Configuration page opens in a new browser window and its login mask is displayed screenshot below Opening the Configuration page if LicenseServer is on another machine To open the LicenseServer Configuration page from some other Windows machine on the local network than that on which LicenseServer is installed enter the URL of the LicenseServer Configuration page in the address bar of a browser and press Ent
170. ring this period will be lost as soon as the Primary LicenseServer regains control Other settings such as Proxy Server and Mail settings are independently set in each server and are not synchronized This is a Failover LicenseServer for the LicenseServer at kubu6 altova com Last seen 2 5 2015 11 56 04 AM To set up a LicenseServer as the Failover LicenseServer do the following i Install LicenseServer as described in the Installation section Set the LicenseServer s mode to Failover LicenseServer by selecting the corresponding radio button see screenshot above By default the LicenseServer Mode is set to Primary LicenseServer In the Find Primary LicenseServer dialog that appears screenshot below enter the Primary LicenseServer you want to back up with this Failover LicenseServer You can do this in one of two ways i Click Search for LicenseServers and then select in the combo box the LicenseServer you want to backup from the list of found LicenseServers ii Click Manually Enter Address and enter the address of the LicenseServer you want to backup After entering the Primary LicenseServer click Connect to Primary LicenseServer 2015 Altova GmbH Altova MobileTogether Server 182 Altova LicenseServer Configuration Page Reference Find the Primary LicenseServer 2 To configure this LicenseServer as a Failover LicenseServer Step 1 Find or enter the address of a Primary LicenseServer Step 2 Connect to it
171. rver has been successfully registered with LicenseServer you will receive a message to this effect The message will also display the URL of the LicenseServer You can now go to LicenseServer to assign MobileTogether Server a license For details see the LicenseServer documentation Examples Examples of the Licenseserver command mobiletogetherserver licenseserver DOC altova com mobiletogetherserver licenseserver localhost mobiletogetherserver licenseserver 127 0 0 1 The commands above specifiy respectively the machine named Doc altova com and the user s Altova MobileTogether Server 2015 Altova GmbH Command Line Usage licenseserver 107 machine localhost and 127 0 0 1 as the machine running Altova LicenseServer In each case the command registers MobileTogether Server with the LicenseServer on the machine specified v Casing on the command line MobileTogetherServer on Windows mobiletogetherserver on Unix Linux Mac Note that lowercase mobiletogetherserver works on all platforms Windows Linux and Mac while upper lower Mobi leTogetherServer works only on Windows and Mac Command options Options are listed in their short forms in the first column and long forms second column together with their descriptions third column On the command line one or two dashes can be used for both short and long forms j json Prints the result of the registration attempt as a machine parsable JSON obje
172. s Your server can have a public IP address accessible over the Internet and or a private IP address accessible within a private network for example via WiFi within a company network If a mobile client device tries to connect via the Internet using the server s private IP address then the connection will not work This is because the private IP address is not known on the Internet and cannot be resolved If a client device uses a private IP address then the client device must already have access to the private network To ensure that the server can be accessed do one of the following e Provide the server with a public IP address so that it can be reached via the Internet On the client device use this public IP address to access the server If you use a firewall and install MobileTogether Server on a server with a private IP address inside the private network then use the network firewall to forward requests sent to a public IP address port combination to your MobileTogether Server server On the client device use the public IP address You must also ensure that the firewall is configured to allow access to the server port used for MobileTogether Client communication The ports used by MobileTogether Server are specified in the Settings page of the the Web UI of MobileTogether Server see the MobileTogether Server user manual On the client device this is the port that must be specified as the server port to access Tip Port 80 is
173. s are flagged as such in the Server Monitoring tab of the Primary LicenseServer screenshot below We recommend that you upgrade your client applications to version 2015 rel 3 or later if you wish to use the Failover LicenseServer feature Network settings Administrators can specify network access points to the LicenseServer configuration page and to LicenseServer Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer Configuration Page Reference 183 Web UI Changing these settings will cause the LicenseServer to restart and any currently running and licensed applications will be shut down Configure the host addresses where the web UI is available to administrators All interfaces and assigned IP addresses Only the following hostname or IP address 0 0 0 0 Ensure this hostname or IP address exists or LicenseServer will fail to start Configure the port used for the web UI Dynamically chosen by the operating system Fixed port 8088 Ensure this port is available or LicenseServer will fail to start Proxy Server Configure the proxy server connection details if a proxy server is needed to communicate with Altova s servers Hostname myproxy Port Number 1285 If the port number is left blank the default port 1080 will be used User Name myusername Password eeeeee Leave the user name and password blank if no authentication is required License Service Configure the host addresses where the Li
174. s button and selecting the required license from those available for that product for example FlowForce Server in the license pool This procedure is explained in more detail below e Each product also has a line stating how many CPU cores need to be licensed to run that product on that client If the number of licensed cores is less than the number required then the information is marked in red see screenshot above The number of CPU cores that need to be licensed is the number of CPU cores on that client and is obtained from the client machine by LicenseServer For Altova s MobileTogether Server licensing is by user client devices that access the server and not by CPU core Single thread execution If a product license for only one core is available in the license pool a machine with multiple cores can be assigned this one core license In such a case the machine will run that product on a single core Processing will therefore be slower as multi threading which is possible on multiple cores will not be available The product will be executed in single thread mode on that machine To assign a single core license to a multiple core machine select the Limit to single thread execution check box for that product Icons in the Server Management tab P Edit Assigned Licenses Available with each product Pops up the Manage Licenses dialog in which new licenses can be assigned to the product and already assigned licenses can
175. s product information along with information about users and licenses Product Edition Version User Address License Type State Last seen seconds ago Altova FlowForce Server 2015 rel 4 BIE BRAVA aam vie alt 8 CPU Cores Running 8 Licenses Altova MobileTogether Server 2 0 BIE BRAVA 9 aam vie alt 8 Users Running 1 Licenses Note Failover LicenseServers work with client applications that are v2015rel3 or later older clients are flagged 2015 Altova GmbH Altova MobileTogether Server 180 Altova LicenseServer Configuration Page Reference Settings This section Failover LicenseServer settings Network settings Alert Mail settings Miscellaneous settings The Settings tab is described below You can set the following e The password for logging in to LicenseServer Enter the desired password and click Change Password e Test connectivity to Altova by clicking Test Connection to Altova Note that you must save new settings by clicking the Save button at the bottom of the pane before testing the connection The Test Connection to Altova button is disabled while the test is in progress and becomes enabled again when the test has been completed e A second LicenseServer can be configured to take over from the Primary LicenseServer if the Primary LicenseServer becomes unavailable This second LicenseServer is called the Failover LicenseServer How to specify its settings are described here e Network settings for the web based
176. sed with an Altova LicenseServer in order to run it Licensing is a two step process 1 Register MobileTogether Server with LicenseServer Registration is done from MobileTogether Server 2 Assign a license to MobileTogether Server License assigning is done from LicenseServer The steps you need to carry out are given below v Start LicenseServer To correctly register and license MobileTogether Server with LicenseServer LicenseServer must be running as a daemon Start LicenseServer as a daemon with the following command sudo launchctl load Library LaunchDaemons com altova LicenseServer plist If at any time you need to stop LicenseServer replace load with unload in the above command sudo launchctl unload Library LaunchDaemons com altova LicenseServer plist v Start MobileTogether Server MobileTogether Server server daemon starts automatically after installation and a re boot of the machine You can start MobileTogether Server as a daemon with the following command sudo launchctl load Library LaunchDaemons com altova MobileTogetherServer2 0 plist If at any time you need to stop MobileTogether Server use sudo launchctl unload Library LaunchDaemons com altova MobileTogetherServer2 0 plist To set up and configure MobileTogether Server open its Web UI Setup page in one of the following ways e Double click the MobileTogether Server 2 0 icon in the Applications folder of the Finder e Enter the URL of the Web UI p
177. srrereessssestsreeesesssseseee 110 64A msta si sevencesdveceeies seed ee cdens va co aeeasidecastyaes ean dete ee 112 05 SLATES Seuss S dieses eet eerie Hea Hea 113 6 0 uninstall 2sccescssee ete cee a a E aes see es aoteds ales esa edesaes S 114 6 7 Sde bugas a ain a enh aa i ee Wee eek ie 115 6 8 uperadedd s sscsscccceessccavacsscgecci E R E E EA EEE ai 116 6 9 EXPOrtreSOUNCEStIIN GS i nn n a E E E aa a aT 117 6 10 setdef ling innesi iaaeaie rS E a eee ESE a eroest ease 119 S i DS oE i EE E A E E E AES 121 6127 VETSINA ee rA ATE E bes ley oon A eee 123 7 Altova LicenseServer 126 PIL Network Information ae r n a E a a Ea a aS EE A 128 T2 Installation Windows isisi ennerien aa a iaa 129 T37 Installation CAUX eee anen E E Seas ede AET dete NAE EE ASERS 131 T4 Anstallation MacOSX rissen na eneee OE nE RES EET ASS 133 RX Altova ServiceControleT erar enaren see ae EAE T EOE ERES ENRE REN ETERS 134 Tos SHOW t0 ASSION LICENSES dinen eoa enie pia or i e e E aeeoe Goes 135 ROT Start LicensEServer vcicsccccsses ceedings sdeusdsa se devves sdecnnshsvedeaeesdacndoasgeevvessdacnteass 136 7 6 2 Open LicenseServer s Config Page Windows sccecceeeeeeesenteeeeees 138 Altova Mobile Together Server 7 6 3 Open LicenseServer s Config Page Linux 0 eeeeeeseseeeceeeceeeensnneeeeees 141 7 6 4 Open LicenseServer s Config Page Mac OS X eessssececcceeeseeeennneeeees 143 7 6 5 Upload Licenses to Licens
178. sure compliance with the Altova license agreements During this initial activation and authentication transaction which typically lasts between 30 seconds and a couple of minutes depending on your Internet connection speed and overall network traffic the status of the license will be indicated as Activating e Failed Verification If a connection with the altova com master licensing server cannot be made then the status of the license in the pool will be shown as Failed Verification If this happens check your Internet connection and firewall rules to ensure that LicenseServer is able to communicate with the altova com master licensing server e Active Once the license has been authenticated and activated the status in the pool will change to Active e Inactive f a license has been verified but is present on another LicenseServer on the network the status in the pool will be shown as nactive An Inactive status also results when a license is manually deactivated in the license pool by the administrator e Blocked A license is shown in the license pool as Blocked if there was a problem authenticating the license and the altova com master licensing server has not granted permission to the LicenseServer to use this license This could be the result of a license agreement violation over usage of a license or other compliance issues Should you see a license showing up as Blocked please contact Altova Support with your license Alt
179. t 7 day s v Active Directory login Enables users to log in to the server with their domain specific user names and passwords Each domain specific user can be imported as a user in the Users tab and then be assigned roles or privileges in the usual way In the Options dialog of MobileTogether Designer the type of user login for connecting to the server can be specified either as a direct server defined user or as a domain user After enabling Active Directory login enter the domain or domains you wish to allow Then go to the Users and Roles Users tab to import specific users as MobileTogether Server users These users can now use their domain specific login information to log in to MobileTogether Server Active Directory login V Enable Enable Active Directory login Allow any existing domain user to login If unchecked use Import Domain Users button on User licenses page to allow specific domain users to login Note Even if any domain user may login you can use workflow permissions to control access to specific workflows Domain suffixes solutions mt altova com The list of comma separated domain names used for login to the server V Set as default Forces Active Directory login providers to be at the beginning of the providers list e Allow any existing domain user to log in All users in the domain can log in to MobileTogether Server If unchecked domain users will nee
180. t is installed on client mobile devices then accesses MobileTogether solutions that are deployed on a MobileTogether Server MobileTogether Server has an easy to use Web UI that provides management of server processes and logs This user manual describes how to set up MobileTogether Server and manage its processes ALTOVA MobileTogether This documentation This documentation is organized into the following sections Introduction Setting Up MobileTogether Server Server Procedures Web UI Reference Command Line Usage Altova LicenseServer Current version 2 0 2015 Altova GmbH Altova MobileTogether Server 4 Altova MobileTogether Server Last updated 09 November 2015 Altova MobileTogether Server 2015 Altova GmbH Chapter 2 Introduction 6 Introduction 2 Introduction This introduction e MobileTogether Overview which describes the MobileTogether system and the place of MobileTogether Server within that system e Using MobileTogether Server section which lists the broad steps required to set up MobileTogether Server for use with MobileTogether Client apps Altova MobileTogether Server 2015 Altova GmbH Introduction MobileTogether Overview 7 2 1 MobileTogether Overview MobileTogether consists of the following modules e MobileTogether Designer MobileTogether solutions for mobile clients are created and deployed to MobileTogether Server See the MobileTogether Designer user manual e M
181. tem requirements v MacOS xX Mac OS X 10 8 or newer Java for OS X latest version Uninstalling old versions of LicenseServer Before uninstalling LicenseServer stop the service with the following command sudo launchctl unload Library LaunchDaemons com altova LicenseServer plist To check whether the service has been stopped open the Activity Monitor terminal and make sure that LicenseServer is not in the list In Applications right click the LicenseServer icon and select Move to Trash The application will be moved to Trash You will however still need to remove the application from the usr folder Do this with the command sudo rm rf usr local Altova LicenseServer Installing Altova LicenseServer Open the download page http www altova com download html and locate the Altova LicenseServer installer under Server Software Products for Mac After downloading the disk image dmg file click to open it This mounts a new virtual drive on your computer On the virtual drive double click the package pkg file and follow the on screen instructions You will need to accept the license agreement for installation to proceed The LicenseServer package will be installed in the folder usr local Altova LicenseServer To eject the virtual drive after installation right click it and select Eject 2015 Altova GmbH Altova MobileTogether Server 134 Altova LicenseServer Altova ServiceController 7 5 Altova ServiceController
182. tered with Altova LicenseServer Only after it has been registered with LicenseServer can a license be assigned to it from LicenseServer On Windows systems if StyleVision Server was installed as part of the FlowForce Server package it will automatically be registered when FlowForce is registered On Linux systems only if StyleVision Server is installed after FlowForce Server will it be registered automatically when FlowForce Server is registered subsequently Registering StyleVision Server from FlowForce Windows StyleVision Server is packaged with FlowForce Server so when FlowForce Server is registered with an Altova LicenseServer on your network StyleVision Server will automatically also be registered with LicenseServer How to register FlowForce Server is described in the FlowForce Server documentation and in the section Register FlowForce Server with LicenseServer After the registration you can go to LicenseServer and assign a StyleVision Server license to StyleVision Server How to do this is described in the section Assign Licenses to Registered Products Registering a standalone StyleVision Server Windows If you have installed StyleVision Server as a standalone package on Windows you must register it with an Altova LicenseServer on your network and then license it from the Altova LicenseServer You can register StyleVision Server via its command line interface CLI by using the licenseserver command StyleVisionServer licenses
183. the Altova server product and the process is different for those server products that have Web Uls and those that are run from the command line only You will need the server name or IP Address of the machine on which LicenseServer is installed to carry out the registration This section describes how to register different Altova server products e Register FlowForce Server e Register MapForce Server e Register StyleVision Server e Register RaptorxML XBRL Server e Register MobileTogether Server 2015 Altova GmbH Altova MobileTogether Server 150 Altova LicenseServer How to Assign Licenses Register FlowForce Server This section Methods of registering FlowForce Server with LicenseServer Accessing the FlowForce Server Setup page Windows Accessing the FlowForce Server Setup page Linux Registering FlowForce Server via the Setup page Registering FlowForce Server via the FlowForce CLI Windows Registering FlowForce Server via the FlowForce CLI Linux Next steps Methods of registering FlowForce Server FlowForce Server can be registered with LicenseServer using any of the following methods e Via the FlowForce Server Setup page e Via the FlowForce CLI Windows e Via the FlowForce CLI Linux Accessing the FlowForce Server Setup page Windows The FlowForce Server Setup page can be accessed in one of the following ways e Via the Start menu Start Altova FlowForce Server 2016 FlowForce Server Setup Page e Via Alto
184. the next step Assign Licenses 2 Assign a license to your Altova product that has been registered with the LicenseServer Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer How to Assign Licenses 161 Register Mobile Together Server To start MobileTogether Server click the ServiceController icon in the system tray hover over Altova MobileTogether Server in the menu that pops up see screenshot below and then select Start Service from the MobileTogether Server submenu If MobileTogether Server is already running the Start Service option will be disabled B Altova FlowForce Server BD Altova FlowForce Web Ad Altova LicenseServer D Altova MobileTogether Server gt Altova RaptorXML XBRL Server gt y Start service Exit Altova ServiceController Stop service Run Altova ServiceController at startup E T m a i 1 11 00 AM Register MobileTogether Server via e The Settings tab of the MobileTogether Server Web UI i Start MobileTogether Server via ServiceController see previous point ii Enter your password to access the Setup page iii Select the LicenseServer name or address and click Register with LicenseServer e its CLI using the 1icenseserver command MobileTogetherServer licenseserver options ServerName Or IP Address For example if localhost is the name of the server on which LicenseServer is installed MobileTogetherServer licenseserver localhost After successful registr
185. three certificate files e Public key mycertificate cer e Secondary intermediate certificate e Primary intermediate certificate Each contains text blocks bracketed by lines that look like this BEGIN CERTIFICATE END CERTIFICATE Now copy paste all three certificates into one file so that they are in sequence The order of the sequence is important i public key ii secondary intermediate certificate iii primary intermediate certificate Ensure that there are no lines between certificates BEGIN CERTIFICATE public key from mycertificate cer see Step 5 END CE IF ICATE BEGI ERTIFICATE secondary intermediate certificate see Step 6 IFICATE ERTIFICATE intermediate certificate see Step 6 IF ICATE prima END CE i Z iw Q mS Q W Qa ve Save the resulting combined certificate text to a file named publickey cer This is the public key certificate file of your SSL certificate It includes your public key certificate as well as the complete chain of trust in the form of the intermediate certificates that were used by the CA to sign your certificate The public key certificate file will be installed on MobileTogether Server together with the private key see Step 8 8 Install SSL certificate on MobileTogether Server The SSL certificate is a set of certificates that are sav
186. tion If this happens check your Internet connection and firewall rules to ensure that LicenseServer is able to communicate with the altova com master licensing server e Active Once the license has been authenticated and activated the status in the pool will change to Active e Inactive f a license has been verified but is present on another LicenseServer on the network the status in the pool will be shown as nactive An Inactive status also results when a license is manually deactivated in the license pool by the administrator e Blocked A license is shown in the license pool as Blocked if there was a problem authenticating the license and the altova com master licensing server has not granted permission to the LicenseServer to use this license This could be the result of a license agreement violation over usage of a license or other compliance issues Should you see a license showing up as Blocked please contact Altova Support with your license information and any other relevant data These statuses are summarized in the table below Activating On upload license information is sent to altova com for verification Refresh the browser to view the updated status Verification and activation can take a few minutes Failed Verification A connection to altova com could not be made After establishing a connection either restart the service or activate the license with the Activate button Active Verification was successf
187. top the Web UI and it has no initial password v About Privileges A privilege is an activity that a user is allowed to carry out There is a fixed number of MobileTogether Server privileges and a user can be assigned zero to all of the available privileges It is however good practice to assign privileges via roles see next section rather than to assign privileges directly to the user The assigning of privileges and roles to a user Altova MobileTogether Server 2015 Altova GmbH Web Ul Reference Users and Roles 79 is done by a user that has been assigned this privilege Initially it is root user that has this privilege The screenshot below shows all the available privileges Privileges V Maintain users roles and privileges V Set own password V Override security V Allow to use stored password on client do not require authentication on application start View unfiltered log V View cache overview V View user licenses overview V Read users and roles Fd Manage server settings Trace workflow Enables detailed workflow execution logging to files including working XML files when the Logging to File option ts enabled V Read global resources WI Write global resources V Open workflow from designer V Save workflow from designer V Run server simulation The tab Users and Roles Reports Privileges Report provides a list of all privileges with each privilege being l
188. ttom of the LicenseServer configuration page all tabs Current version 1 23 v Trial license During the installation process you will be given the option of requesting a 30 day trial license for MobileTogether Server After submitting the request a trial license will be sent to the email address you registered 2015 Altova GmbH Altova MobileTogether Server 24 Setting Up MobileTogether Server Setup on Linux Licensing on Linux MobileTogether Server must be licensed with an Altova LicenseServer in order to run it Licensing is a two step process 1 Register MobileTogether Server with LicenseServer Registration is done from MobileTogether Server 2 Assign a license to MobileTogether Server License assigning is done from LicenseServer The steps you need to carry out are given below v Start LicenseServer To correctly register and license MobileTogether Server with LicenseServer LicenseServer must be running as a daemon on the network Start LicenseServer as a daemon with the following command Debian 6 7 sudo etc init d licenseserver start Debian 8 sudo systemctl start licenseserver Ubuntu lt 14 sudo initctl start licenseserver Ubuntu 15 sudo systemctl start licenseserver CentOS 6 sudo initctl start licenseserver CentOS 7 sudo systemctl start licenseserver RedHat sudo initctl start licenseserver If at any time you need to stop LicenseServer replace start with stop in the above comman
189. two 4 core licenses can also be used for an octa core server instead of one 8 core license If you are using a computer server with a large number of CPU cores but only have a low volume to process you may also create a virtual machine that is allocated a smaller number of cores and purchase a license for that number Such a deployment of course will have less processing speed than if all available cores on the server were utilized Note Each license can be used for only one client machine at a time even if the license has unused licensing capacity For example if a 10 core license is used for a client machine that has 6 CPU cores then the remaining 4 cores of licensing capacity cannot be used simultaneously for another client machine 25 Altova MobileTogether Server 26 Setting Up MobileTogether Server Setup on Linux MobileTogether Server licenses Two types of MobileTogether Server license are available Customers can select a license type that best suits their requirements e Core licenses These are assigned to MobileTogether Servers on the basis of the cores on the server machine see the explanation above An unlimited number of MobileTogether Client devices can then connect to the server e User licenses These specify the maximum number of users MobileTogether Client devices that are allowed to connect to the MobileTogether Server at one time Altova MobileTogether Server 2015 Altova GmbH Setting Up MobileToget
190. ul the license is active Inactive Verification was successful but the license is on another LicenseServer on the network Licenses can be made inactive with the Deactivate button Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer Configuration Page Reference 171 Blocked Verification was not successful License is invalid and is blocked Contact Altova Support Note After a license has been sent to altova com for verification the browser must be refreshed to see the updated status Verification and activation can take a few minutes Note If a connection to altova com could not be made the status will be Failed Verification After establishing a connection either restart the service or try activating the license with the Activate button Note When a license is given a status of Inactive or Blocked a message explaining the status is also added to the Messages log Only an active license can be assigned to a product installation An inactive license can be activated or deleted from the license pool If a license is deleted from the license pool it can be uploaded again to the pool by uploading the license file containing it When a license file is updated only those licenses in it that are not already in the pool will be uploaded to the pool To activate deactivate or delete a license select it and then click the Activate Deactivate or Delete button respectively Connection to the Master Licensing S
191. ulates is given in the License Type column In the case of Altova s MobileTogether Server product licenses are also assigned on the basis of the number of MobileTogether client devices that connect to MobileTogether Server the users of the server In the case of all other Altova server products licenses are assigned on the basis of CPU cores only see note below e Assignments Access to editing dialogs and information of individual licenses Note on cores and licenses The licensing of Altova server products is based on the number of processor cores available on the product machine for MobileTogether Server an additional licensing option is available see below For example a dual core processor has two cores a quad core processor four cores a hexa core processor six cores and so on The number of cores licensed for a product must be greater than or equal to the number of cores available on that server machine whether the server is a physical or virtual machine For example if a server has eight cores an octa core processor you must purchase at least one 8 core license You can also combine licenses to achieve the core count So two 4 core licenses can also be used for an octa core server instead of one 8 core license If you are using a computer server with a large number of CPU cores but only have a low volume to process you may also create a virtual machine that is allocated a smaller number of cores and purchase a license for that
192. un the following command ina terminal window sudo launchctl load Library LaunchDaemons com altova LicenseServer plist If at any time you need to stop LicenseSerer use sudo launchctl unload Library LaunchDaemons com altova LicenseServer plist Connection to the Master Licensing Server at altova com The Altova LicenseServer needs to be able to communicate with the Master Licensing Server at altova com to validate and authenticate license related data and to ensure continuous compliance with the Altova license agreements This communication occurs over HTTPS using port 443 If the Altova LicenseServer after making the initial verification with the altova com Master Licensing Server is unable to again connect with altova com fora duration of more than 5 days 120 hours then the Altova LicenseServer will no longer permit the usage of any Altova software products connected to the Altova LicenseServer Any such loss of connection with the altova com master servers will be logged in the Messages tab of the Configuration page of the Altova LicenseServer In addition the administrator can configure the Altova LicenseServer to automatically send an alert email when the connection to altova com is lost Alert Mail settings are available in the Settings tab of the Configuration page 2015 Altova GmbH Altova MobileTogether Server 138 Altova LicenseServer Open LicenseServer s Config Page Windows This section Opening the Configu
193. va ServiceController Click the ServiceController icon in the system tray In the menu that pops up select Altova FlowForce Web Setup This pops up the FlowForce Server Setup page screenshot above Accessing the FlowForce Server Setup page Linux After you have installed FlowForce Server on Linux see the FlowForce Server user documentation for information about how to do this start FlowForce Web Server as a service with the following command sudo etc init d flowforcewebserver start A message containing the URL of the FlowForce Server Setup appears in the terminal window FlowForceWeb running on http 127 0 1 1 3459 setup key 522 39315203 Enter the URL in the address field of a browser and hit Enter to access the FlowForce Server Altova MobileTogether Server 2015 Altova GmbH Altova LicenseServer How to Assign Licenses Setup page screenshot below Registering FlowForce Server via the Setup page In the Setup page screenshot below how to access it is described above the LicenseServer field specifies the Altova LicenseSerer to be used for registration ALTOVA 0 ids FlowForce REM SERVER 2014 Home Help Setup LicenseServer Enter address here or search for LicenseServer FlowForce Web Server Bind address All interfaces 0 0 0 0 v Port 8082 Default time zone Europe Berlin FlowForce Server Bind address All interfaces 0 0 0 0 v Apply settings and restart FlowForce services T
194. ver The HTTP port is the unsecure port HTTPS is the secure port To use HTTPS you need to set up SSL Encryption Altova MobileTogether Server 2015 Altova GmbH Server Procedures Set Administrator and Mobile Client Ports 55 Mobile client ports Select unsecure HTTP and secure HTTPS ports the Mobile clients will use These ports cannot be used for administrative purposes Wi HTTP Port 8083 E HTTPS Port 8084 2015 Altova GmbH Altova MobileTogether Server 56 Server Procedures Users and Roles 4 5 Users and Roles A user account is defined by a log in name and password and has a set of access rights associated with it Users access MobileTogether Server for administrative purposes or as client end users Access rights are determined by the privileges a user is granted A user receives privileges in the following ways i privileges inherited from roles the user is a member of ii privileges assigned directly to the user A role is defined by a set of privileges A role is either assigned privileges directly and or inherits the privileges of another role that it is a member of Privileges themselves are access rights to the various administrative functions and services of MobileTogether Server Examples of privileges are the right to manage server settings to set a user s own password to run simulations on the server Through the use of roles user privileges can be defined in a hierarchical
195. ver on Unix Linux Mac Note that lowercase mobiletogetherserver works on all platforms Windows Linux and Mac while upper lower MobileTogetherServer works only on Windows and Mac 2015 Altova GmbH Altova MobileTogether Server 114 Command Line Usage 6 6 uninstall This section e Command syntax e Command description e Examples Command syntax Windows MobileTogetherServer uninstall Linux mobiletogetherserver uninstall Mac mobiletogetherserver uninstall Command description uninstall The uninstall command uninstalls MobileTogether Server as a service on the server machine The command takes no options To re install MobileTogether Server as a service use the install command Examples Examples of the uninstall command mobiletogetherserver uninstall v Casing on the command line MobileTogetherServer on Windows mobiletogetherserver on Unix Linux Mac Note that lowercase mobiletogetherserver works on all platforms Windows Linux and Mac while upper lower MobileTogetherServer works only on Windows and Mac Altova MobileTogether Server 2015 Altova GmbH Command Line Usage debug 115 6 7 debug This section e Command syntax e Command description e Examples Command syntax Windows MobileTogetherServer debug Linux mobiletogetherserver debug Mac mobiletogetherserver debug Command description The debug command starts MobileTogether Server for debugging not
196. w This information will be used by the certificate authority to verify your company s identity e Country e Locality the city where your business is located e Organization your company name Do not use special characters these will invalidate your certificate e Common Name the DNS name of your server This must exactly match your server s official name that is the DNS name client apps will use to connect to the server e A challenge password Keep this entry blank Altova MobileTogether Server 2015 Altova GmbH Setting Up MobileTogether Server Setting Up SSL Encryption 39 3 Buy an SSL certificate Purchase an SSL certificate from a recognized certificate authority CA such as VeriSign or Thawte For the rest of these instructions we follow the VeriSign procedure The procedure with other CAs is similar Go to the VeriSign website Click Buy SSL Certificates Different types of SSL certificates are available For MobileTogether Server Secure Site or Secure Site Pro certificates are sufficient EV extended verification is not necessary since there is no green address bar for users to see Proceed through the sign up process and fill in the information required to place your order When prompted for the CSR created in Step 2 copy and paste the content of the my csr file into the order form Pay for the certificate with your credit card Allow time for obtaining a certificate Obtaining public key certificat
197. way For example the role of SimpleAdmin role could allow the privilege Manage server settings If AdvancedAdmin is a member of SimpleAdmin it inherits the management of server settings and could additionally be assigned the privilege Maintain users roles and privileges The hierarchical chain can the be further extended For a list of privileges see Available Privileges v About Users A user is defined by a name and password combination Users access MobileTogether Server in two ways e Web Ul access The Web Ul is the administrative interface of MobileTogether Server Logging in to the Web UI requires a name and password combination it is therefore done as a user e Service interface The HTTP senice interface exposes MobileTogether Server services typically to the MobileTogether Client app on a mobile device A user accesses the service interface using a name and password combination The services exposed relate typically to access to MobileTogether solutions and their related data Two special users are predefined root is the initial administrator user It is initially the most powerful user having all privileges and having the ability to add other users and to set roles Its initial name password combination is root root The password can be changed at any time anonymous anonymous iS an account for anonymous users that access services exposed via the HTTP senice interface It cannot be used for logging in top the Web UI
198. y into the newer version when the newer version is installed The version number of the currently installed LicenseServer is given at the bottom of the LicenseServer configuration page all tabs Current version 1 23 v Trial license During the installation process you will be given the option of requesting a 30 day trial license for MobileTogether Server After submitting the request a trial license will be sent to the email address you registered v Application folder location The application will be installed in the following folder Windows XP C Program Files Altova 32 bit Version on 64 bit OS C Program Files x86 Altova 2015 Altova GmbH Altova MobileTogether Server 16 Setting Up MobileTogether Server Setup on Windows Licensing on Windows MobileTogether Server must be licensed with an Altova LicenseServer in order to run it Licensing is a two step process 1 Register MobileTogether Server with LicenseServer Registration is done from MobileTogether Server 2 Assign a license to MobileTogether Server License assigning is done from LicenseServer The steps you need to carry out are given below v Start ServiceController Altova ServiceController is started in order to start Altova LicenseServer and Altova MobileTogether Server Altova ServiceController ServiceController for short is an application for conveniently starting stopping and configuring Altova services on Windows systems
199. ystem 2014 04 11 19 system 2014 04 11 19 system 2014 04 11 17 root 4 P Search The view can be Show from f 2014 04 07 to ys Minimum severity Info Device Design 2 public WidgetsSalesData 2 public WidgetsSalesData filtered by Delete Delete from f 2014 04 07 to x show AN f 2014 04 14 Page 1 ofi 235 y View 1 9of9 Severity Message o 00000000 License loaded from the LicenseServer Starting web server Stopping canceling running tasks Database database is locked License loaded from the LicenseServer Starting web server Stopping canceling running tasks Executed on server Error loading image Widgets Logo Deployable file nttp www altova com images WidgetsHeader png does not exist Executed on server Error loading image Imaget Deployable file http www altova com images WidgetsHeader png does not exist w r Page 1 ofi 35 y View1 9of9 e Date Ranges or specific dates can be set e Minimum severity Errors is the highest severity only errors are shown Warnings is next errors and warnings are shown Info is the lowest severity and shows errors warnings and info e Search criteria Click the Search button at the top or bottom left of the log table to open the Search dialog described below To remove the filter defined by the search criteria click the Reload Grid icon next to the Search button Logs can be deleted

Altova MobileTogether Server

Contents

Download Pdf Manuals

Related Search

Related Contents