Getting started

friendlyway composer network services

Version 3.0.0

 

 

Contents

1. Two distribution models of composer network services

2. Network configuration

3. Function overview

4. Installation of the client software

5. Setup of an automatic fault notification

 

 

 

 

1. Two distribution models of composer network services

 

1.1 Using composer network services server from friendlyway (ASP model)

This model implies that you buy licenses for certain number of clients, install the client software on terminals, and use online services from friendlyway without own installation of the composer network services server. You get the user ID and password for the administration console you can access at http://client-manager.net/WebConsole. Note that this model also implies that each client machine has internet connection.

For a composer 2007 demo license and a trial account for composer network services you can contact the friendlyway Sales.

 

1.2 Using own composer network server installation    

This model implies that you install own composer network services server the client stations with client software will connect to. In this case, no internet access is required if clients are inside of a closed network. The administration console is accessible at http://yourservername/Webconsole (where "yourservername" is the computer name of the installed server in the network). Default user ID and password are admin / password (must be changed after server installation).

 

1.2.1 How to install your own composer network services server:

Download the composer network services setup from the link you received from friendlyway Sales. After installing it on the server, install the cns-license.exe application received from friendlyway Sales on the server too.

 

1.2.2 Computer requirements for composer network services server:

Up to 10 clients:

- Windows 2000 Professional Service Pack 4, Windows XP Professional or Windows Vista, Windows 2000 Server Standard Edition or Windows 2003 Server Standard Edition

- Internet Information Services (IIS) must be installed on the computer (belongs to Windows)

 

More than 10 clients:

-Windows 2000 Server Standard Edition or Windows 2003 Server Standard Edition

- Internet Information Services (IIS) must be installed on the computer (belongs to Windows)

- Microsoft SQL Server 2000 (must be purchased separately from Microsoft). Note that in the next versions of composer network services server, free-of-charge Microsoft SQL Server 2005 Express Edition will be used.

 

2. Network configuration

 

The server computer must be reachable from the client stations. The composer network services solution requires that the following ports are open:

Server computer:

Port 80 (HTTP) - used to access the web console and to send the keep-alive messages and files from client stations (terminals) to the server.

Client computer:

Port 5900 (VNC) - used to get the remote control access from the administration console to the terminal.

Port 2036 – used to send connect and reboot commands to the terminals.

Please check that your server address is available on the internet if you would like to access the administration console from internet or if your clients are located outside the closed network. Please refer to your system administrator to get an open network address for the server computer or setup the port forwarding for port 80!

 

3. Function overview

 

This version of the composer network services software has the following functions:

- Keep-alive messaging from client to server

- Monitoring of CPU utilization, memory usage, disk usage and hanged applications on clients

- Display of client state via administration console

- Mail or SMS notification of service person in case of a client fault

- Management and monitoring of client applications (web browsers, players etc.) with extended support of friendlyway secure browser, friendlyway player and friendlyway player 2007

- Automatic restart of crashed or hanged up client applications

- Desktop protection with password protected locking of critical system keys and prevention of unauthorized access of visitors to the computer desktop

- Transferring and displaying client logs files

- Report of client internet access times

- Report of web pages visited on the clients (only with friendlyway secure browser)

- Distribution of secure browser and composer packages to clients from the administration console

 

4. Installation of the client software

 

IMPORTANT NOTE: Although you can use other software then friendlyway player 2007 as kiosk application, the next two subparagraphs contain descriptions how to install and set up the client service application for running with friendlyway player 2007 as kiosk application. So, to get everything working as described in these subparagraphs, the installation of friendlyway player 2007 is required.

 

The client licenses must be already installed on your composer network services server before you install the client service application. Please refer to the Licenses page in the administration console to get information about the installed licenses. Please contact our friendlyway software sales team to obtain and upgrade your account or server with additional client licenses.

 

For each client station a terminal account will be created in a database. Every terminal account receives a name in order one client station can be differentiated from others. The name of the terminal account must be unique across the server instance; it is impossible to create several terminal accounts with one name. There are two ways for creating terminal accounts: via administration console or from the client station itself. The descriptions for both possibilities, you'll find in the subparagraphs 4.1 and 4.2.

 

4.1 Creating a terminal account via administration console

 

4.1.1 Operations in the administration console

1. Open the administration console at http://client-manager.net/webconsole if you use the friendlyway sever or at http://yourservername/webconsole if you have own server instance.

2. Log on to the administration console using your user ID and password.

3. Go to the Terminals tab.

4. On the Terminals page, click the New button.

5. From the selection field License key, select the license with available installations.

6. Enter the Terminal ID you would like to assign to the terminal, and press the Register terminal button.

7. A terminal account will be created and the Terminal configuration page will appear.

8. Configure your terminal or just leave default terminal settings, and then press OK to save the terminal account.

If you have more than one terminal repeat steps 4-8 to create multiply terminal accounts.

 

4.1.2 Operations on the client computer

After creating a terminal account in the administration console, install and configure the client service application on the client machine. To do that, perform the following actions:

 

1. Download the client service executable from the Downloads section of the administration console.

2. Install the client service application on the client computer.

3. Let the client restart on the message at the end of installation.

4. A blue setup screen will appear on the client's display.

5. Press the Setup button on the blue screen. The friendlyway license manager will be launched.

6. Click the Register online button.

7. If you use a proxy server, check the corresponding option, specify the address, user ID, password, port, and click Next. If you don't use proxy just click Next.

8. The Terminal server page will appear. If you use the ASP model leave the default value client-manager.net as server address, and leave fields Server account / Server password empty (to proceed, click Next). If you have own server installation specify the name of your server, enter the server account/password (for Windows), and click Next.

9. In the User authorization window, enter your user ID and password you use for the login to the administration console.

10. On the friendlyway Licenses page, select the license that will be used for the client installation.

11. On the License details page, leave checked the option with existing Terminal ID, and select the terminal Id you have created before.

12. Window informing about successful registration of your client service instance will appear, click Finish.

13. The license manager will be closed and configuration manager will start.

14. A message asking you for configuring player 2007 to run with client service will appear; click Configure friendlyway player 2007 to run with client service.

15. In the next window, leave checked the option composer 2007 project will be provided by client manager content distribution, and click OK.

16. Click “Download configuration from server”, and then click OK in the appeared window.

17. Go to the Desktop Protection tab, and check the option Display maintenance screen at start up.

18. Remember default hotkeys or specify your own, and click OK. Default hotkeys are as follows below:

Disable maintenance screen and application monitoring:  Alt+Shift+S

Enable maintenance screen and application monitoring:   Alt+Shift+P

Toggle maintenance screen:                                          Alt+Shift+F8

19. Click the OK button in the left bottom corner of the control center to upload your configuration to the server. Confirm uploading in the next window via Yes button.

20. Leave checked the option Start client service every time after computer booting, and click the button Yes, start client service.

 

After this step, the client service window will appear shortly and load the maintenance screen. The maintenance screen will remain until player has received a content package.

 

4.2 Creating a terminal account from the client computer

1. Download the client service executable from the Downloads section of the administration console.

2. Install the client service application on the client computer.

3. Let the client restart on the message at the end of installation.

4. A blue setup screen will appear on the client's display.

5. Press the Setup button on the blue screen. The friendlyway license manager will be launched.

6. Click the Register online button.

7. If you use a proxy server, check the corresponding option, specify the address, user ID, password, port, and click Next. If you don't use proxy just click Next.

8. The Terminal server page will appear. If you use the ASP model leave the default value client-manager.net as server address, and leave fields Server account / Server password empty (to proceed, click Next). If you have own server installation specify the name of your server, enter the server account/password (for Windows), and click Next.

9. In the User authorization window, enter your user ID and password you use for the login to the administration console.

10. On the friendlyway Licenses page, select the license that will be used for the client installation.

11. On the License details page, the option Create terminal account before registration will be checked, just click Next to proceed.

12. On the Register terminal page, specify the terminal ID you would like to assign to the terminal, provide terminal location information, and click Next.

13. Window informing about successful registration of your client service instance will appear, click Finish.

 

To configure the terminal and start the client service, see items 13-20 in the subparagraph 4.1.

 

5. Setup of an automatic fault notification

 

1. Open the administration console at http://client-manager.net/webconsole if you use the friendlyway sever or at http://yourservername/webconsole if you have own server instance.

2. Logon to the administration console using your user ID and password.

3. Go to the Terminal locations tab.

4. Select the terminal for fault notification from the list and click on the Service person button.

5. Enter the first and last name of the service person, specify the notification method and contact data depending on the selected notification method (e-mail address or phone / fax / mobile phone number).

 

SMS notifications are only available if you have account by Mail-to-SMS service provider. Please refer to friendlyway Software Support to setup SMS notification.

 

 

friendlyway AG, August 2007.