Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
userguide:savapage [2016/12/09 05:40]
rob bosch [Step 17: Change SavaPage to use PostgreSQL]
userguide:savapage [2017/12/10 04:30] (current)
rob bosch [Step 18: Initial configuration]
Line 401: Line 401:
 By default TCP/IP connections are disabled from remote computers. To enable access from remote computers uncomment listen_address. If PostgreSQL is on the same server as SavaPage, you can keep listenaddress as localhost. By default TCP/IP connections are disabled from remote computers. To enable access from remote computers uncomment listen_address. If PostgreSQL is on the same server as SavaPage, you can keep listenaddress as localhost.
 <​file>​ <​file>​
-$ sudo nano /​var/​lib/​pgsql/​data//​postgresql.conf+$ sudo nano /​var/​lib/​pgsql/​data/​postgresql.conf
 </​file>​ </​file>​
  
Line 411: Line 411:
 </​file>​ </​file>​
 This allows remote access from ip address x.x.x.x only. This allows remote access from ip address x.x.x.x only.
-If you want remote access from multiple computers in your network use a comma separted ​list of addresses:+If you want remote access from multiple computers in your network use a comma separated ​list of addresses:
 <​file>​ <​file>​
 Listen_addresses='​addres1,​addres2,​localhost'​ Listen_addresses='​addres1,​addres2,​localhost'​
Line 516: Line 516:
 You will be able to log in with the admin account. Default password is admin, if you didn’t already change this, now is a good time to do so. You will be able to log in with the admin account. Default password is admin, if you didn’t already change this, now is a good time to do so.
  
-====== ​Apendixhandy weblocations ​======+====== ​Step 18Initial configuration ​======
  
 +When you log in the admin interface for the first time you will see the dashboard. On the right there is an overview of your SavaPage install.
 +You will notice a "Setup is needed"​ in red. This means that the initial configuration for SavaPage has not been done yet.
  
 +{{userguide:​savapage-admin-firstlogin.png}}
 +
 +There are a few steps you need to take to configure SavaPage for use:
 +
 +**(If not already done) Change the admin password**
 +As a first security measure change the master password for the built-in admin account. This account is independent and not related to the operating system or domain. The password needs to meet minimum strength requirements,​ and must contain at least six characters. ​
 +Select Options → Advanced → Reset internal admin password
 +Enter and confirm the new password and press the Apply button.
 +
 +**Set Locale**
 +Set the system'​s locale; ensure that these are correct before proceeding. Select Options → Advanced → Locale, and enter the locale string.
 +Some examples are: 
 +en, en-GB, en-US, nl, nl-NL, nl-BE. ​
 +You can leave the locale empty to accept the system default. The locale is applied to all system messages which are logged in the system log or send by email.
 +
 +**Set Currency Code**
 +Set the system'​s currency code; ensure that these are correct before proceeding. ​
 +Select Options → Financial, and enter the ISO 4217 Currency code.
 +Some examples are: USD, EUR, GBP. The currency symbol is determined in the context of the user or system locale.
 +
 +**Set User Source**
 +SavaPage optionally imports user information from a Unix (PAM, NIS, etc.) or LDAP source.
 +Select Options → User Source.
 +Select Unix if the user accounts are setup and defined on the local system as standard Unix accounts or mapped into the system from a central directory service such as LDAP via
 +nsswitch.conf and PAM. Most large established networks will use this option.
 +Note: For administrators wishing to customize the PAM authentication method at the application level, SavaPage reports itself as “savapage”.
 +The LDAP option is appropriate for large networks with existing LDAP domains. This includes networks running OpenLDAP, Apple Open Directory, Novell eDirectory and Microsoft Active Directory.
 +More information on LDAP is available in Section 4.10.1.2, “LDAP”.
 +After selecting the source, enter the necessary parameters (LDAP only) and press the Apply button.
 +
 +For NethServer specific configuration,​ you need to configure LDAP as follows:
 +
 +{{userguide:​savapage-config-ldap.png}}
 +
 +Adjust the settings to what you have chosen for Samba4 AD information on your NethServer7 instance.
 +
 +**User Synchronization**
 +Skip this step if you did not set an external User Source in the previous step. 
 +Otherwise, select Options → User Creation →  Synchronization → Synchronize now to import users.
 +Important
 +An option exists to import a subset of users from the source by selecting a group. This option is relevant if only a subset of users will ever use SavaPage.
 +Select Options → User Creation → Change Group to select the group.
 +
 +Tip
 +Test the import first by pushing the Test button. A simulated import will start, with each step echoed below the button, so you can verify the effect of your action.
 +
 +**Set Mail Options** ​
 +Select Options → Mail, enter the SMTP and Message options and press the Apply button. Data from the Messages section is used for system generated mail messages.
 +You  can  send  a  test  mail  message ​ to  a  recipient ​ of  your  choice ​ by  pressing ​ the Test button after  you  applied ​ the changes.
 +
 +**Driverless Printing**
 +Mail Print and Web Print are disabled by default.
 +You can enable and configure these options at Options → Mail Print and Options → Web Print.
 +If you enabled one of the driverless printing options, decide which PDF converters you want to enable at Options → Advanced → Converters. Beware that you might need to install the converter software on the SavaPage host.
 +
 +**Share SavaPage Client Files**
 +SavaPage client files are located in directory /​opt/​savapage/​client. This includes the SavaPage Printer Driver and JMX related files. It is useful to share this directory over the network so users can use, copy or install the files they need on their workstation. Common sharing methods include:
 +• Samba
 + - used to share files to Windows based workstations. GUI tools are available on GNU/Linux to help you with sharing the client directory via Samba. However, some system administrators may be more comfortable creating the share by hand-editing the /​etc/​samba/​smb.conf file.
 +The following configuration will share the directory in read-only form:
 +[savapage-client]
 +path = /​opt/​savapage/​client
 +comment = SavaPage Client
 +public = yes
 +only guest = yes
 +read only = yes
 +• NFS
 + - a popular sharing method used for GNU/Linux and Unix based workstations.
 +Note
 +The /​opt/​savapage/​client directory is standard shared via the client/ URL.
 +
 +**Testing**
 +Now the installation is complete, it is time to do a basic test to check if the system is ready-to-use.
 +  * Pick a workstation and login as a user that is part of the user source as configured in "Set User Source”.
 +  * Install the SavaPage Printer Driver. See the instructions at Section 10.1 of the SavaPage user manual: https://​www.savapage.org/​docs/​manual/​ch-printer.html#​ch-printer-driver,​ “Printing with a Driver”.
 +  * Open a Web Browser and go to the User Web App at https://​server.domain.tld:​8632/​user
 +  * Login to the Web App with the same credentials as used in the workstation login.
 +  * Print a test document such as a web page or basic document to the SavaPage printer.
 +  * Thumbnail images of the printed pages should appear in the Web App.
 +
 +**Add a balance to allow loggin in**
 +If the user has no credit to print, he can not log in the userinterface. In order to add credit to the user balance, ​
 +
 +====== Apendix: handy weblocations ======
  
 Savapage website: [[https://​www.savapage.org]] Savapage website: [[https://​www.savapage.org]]