Installation of a standalone virtual printer
Pagero Printer is available at Pagero Online’s web site (www.pageroonline.com). Sign in and go to Support/Downloads. Click the symbol to download the installation file. Follow the instructions on the page to install the printer as a standalone printer.
Making the printer a network printer (if applicable)
- Set the paths for prints (they will be saved on a local disc before transfer to Pagero Online). Open the file, printsettings.ini, which is in the folder Pagero Connect in the program folder (c:\Program, Program Files, Program Files (x86)). In this file there is a property, printTargetStandalonePrinter. Give this a value, which is a path to a folder. All printed invoices will be directed to this path. Note that every \ in the path, must be entered twice, for example, c:\\pagero\\invoices. You can also enter, c:\pagero\invoices. This folder must be located on the same computer that the printer is installed on.
- To avoid sending partially created files, set the configuration parameter temporaryPdfAsFile-OrDir=temp where temp is a subdirectory to the printTargetStandalonePrinter above. The file will then be written to the temp directory first, and then moved to the directory given in printTargetStandalonePrinter.
- Make sure the System account has read and write rights to the folder given above.
- If another user (than System) is used for scheduling Pagero Server Connect (see next section), then make sure that user has read and write access to the folder created in step 1.
- Share the printer for use in network by right-clicking the printer and select Share… Make sure all users that need access to the printer can access it.
Pagero Server Connect for communication
This section describes the installation procedure for Pagero Server Connect.
Pagero Server Connect is a java based client used to communicate with Pagero’s central server, in order to receive and send electronic documents. The scripted version faciliates fully automated communication. The application communicates using https with the Pagero Online service where documents are received and processed for further distribution to document recipient.
This section contains instructions for installing Pagero Server Connect. Log in to Pagero Online’s website (www.pageroonline.com). Go to Support/Downloads. Click the symbol to download a zip file containing the installation.
Zip file content
The zip file should contain the following files:
- Pagero Server Connect.xml
- log folder
- licencse folder
- files folder
Unpack the files in dedicated folder, and check that all files in the list are included. For support and tracking, Pagero recommend the path contain Pagero. Example: C:\Program\Pagero\Poscripted
Edit config.xml (save an unedited version for backup).
Define log catalouge and log level. Add SMTP mail server and email group.
- Pagero recommends that a specific email-group is created and used in order to minimize configuration in config.xml. Relevant users is then added and edited in the email-group.
- Make sure the sending part (email-account) has the right to send mail via the email-server.
Configure the application
Multiple companies are added through copy and paste of the content:
<company name="Company 1" companyID = "">
Pagero account: user & password. Account information is provided by Pagero Service Center and through confirmation mail.
Then define the following folders:
- If both sending and receiving through Pagero, define and configure both Inbox and Outbox settings.
- All folders must be manually created.
- Pagero strongly recommend all folders are created on the local server.
Finally, save and exit config.xml
- In the event, that the folders used for reading and writing files are mounted devices, use a UNC path to indicate the location, like this: \\\\unit\path.
- When using Outbox to send files, files should not be copied to the folder Pagero Connect reads from. This is because the partially copied file may be sent. Copy files to a different folder on the same disk, then move the file to the folder from where Pagero Server Connect reads.
Enable attachment handling for outbond traffic
The server connect application supports automatic attachment document binding using file name conventions. Use the following attributes on the outbox configuration element, to enable attachment handling.
|subDocAware||If true, outbox will be aware of sub documents (Attachments)|
|masterDocRegexp||Regular expression for file name that identifies a master document (i.e. invoice) and has a group that extracts the document id.|
|subDocRegexp||Regular expression for file name that identifies a sub document (i.e. attachment) and has a group that extracts the master document id.|
|subDocPresentationRegexp||Regular expression for file name that identifies a presentation sub documentation and has a group that extracts the master document id.|
Internet access through proxy
Follow the instructions below, if your company uses a proxy to access the Internet.
! Note that we do not currently support authenticated proxies. That is, proxies that require authentication for access.
Define the following environment variables:
JAVA_RUNTIME=C:\Program\Java\jre6 #The path to your Java runtime installation
PROXY_HOST=localhost #The proxy server host name
PROXY_PORT=8888 #The proxy server host port
Use this command line, when scheduling Pagero Server Connect:
– Djavax.net.ssl.trustStorePassword=changeit -Dhttps.proxyHost=%PROXY_HOST%
– Dhttps.proxyPort=%PROXY_PORT% -Dhttp.proxyHost=%PROXY_HOST%
– Dhttp.proxyPort=%PROXY_PORT% -jar postcripted-jar-with-dependencies.jar -config
A scheduler is used to schedule sending/receiving of electronic invoices. In this example: Windows default Schedule.
User & Rights
Pagero recommends a specific user purely defines to execute the job. Choose/Create a specific (AD) user, with adequate rights for executing the job, or add user on local server/computer.
Configuration Windows Scheduler
- Define java: Example: C:\Program\Java\jre6\bin\ javaw.exe
- Set name to: Pagero Connect
- Choose interval, (editable and specifiable later).
- Define user & Password
- Choose: Advanced Settings
Alternatively import included task from the PageroServerConnect-folder: Pagero Server Connect.xml directly into the Windows Task Scheduler.
Option 1 – Use provided bat script(s)
Requires the vb script engine is installed and active.
Edit ServerConnect.bat and set the following parameters to fit your environment.
SET PAGERO_ SC_CONFIGFILE – Configurationfile for serverconnect
SET PAGERO_SC_LOGMODE – FILE or SYSTEM
SET PAGERO_SC_LOGPATH – Path for your logs
SET PAGERO_SC_MAILSERVER – servername:port
SET PAGERO_SC_LOGLEVEL – INFO or WARN
SET PAGERO_SC_MAILRECEIVERADDRESS – Receivers mail adress
SET PAGERO_SC_SENDERRADDRESS – Senders mail adress
If you use Proxy, you must set following parameters
PROXY_HOST – Proxys addres
PROXY_PORT – Proxys port
PAGERO_ SC_PROXY=%PAGERO_SC_TRUST_STORE% %PAGERO_SC_TRUST_PASSWORD%
Then enter the following parameters into the scheduling tool
Run: “C\WINDOWS\system32\wscript.exe <install path>\invis.vbs <install path>\ServerConnect.bat
Run in: <path>
Run as: <user>
Make sure right user and password are used.
Option 2 – Schedule java application manually
- Use javaw.exe instead of java.exe in order to avoid manual command window.
Default command: java -jar poscripted-jar-with-dependencies.jar -config config.xml
Full example (with path & command): C:\Program\Java\jre6\bin\javaw.exe -jar
poscripted-jar-with-dependencies.jar -config config.xml
Run in: <path>
Run as: <user>
Make sure right user and password are used.
Scheduling & Settings
Edit interval after your choice.
Control user and rights.
Save and close.
Test the procedure.
This section contains an example configuration file, used on a Windows server system.
You should not use special character in username (use only alphabetic, numbers and “_”).
<?xml version="1.0" encoding="UTF8"?> <poclient> <!-- The-logtag specifies how logging is done. Attributes: Mode FILE Logs to a text file SYSTEM Logs to the operating system log. For Windows the Event Log is used. For other system (i.e. Unix/Linux) the logs are logged to syslog at localhost via UDP Path if file mode is used it tells where the logfile shall be written
Verbose if true all DEBUG logs will be written to the log destination --> <log mode="FILE" path="c:/pagero/log" verbose="true"/> <!-- To get mail notification as a complement to the logs. Attributes: server The SMTP server that is used for sending mail level The level specifies which log level that shall be included in the mail. INFO All info, warn, error logs are included in the mail WARN All warn, error logs are included in the mail Note! If no logs are written no mail will be sent. Sender The sending mail address Receiver The receiver’s mail address --> <mail server="myMailServer" level="INFO" sender="email@example.com" receiver="firstname.lastname@example.org"/> <!-- The company-tag specifies a configuration for a company. There can be one or more companytags. Attribute: Name The name of the company/account. Used in logs. companyId Identifies a company, this is for multicompany use. If more than one company is being represented the value for companyId is the current company. If companyId is empty then the company used for sending and receiving invoices will be the currently/last logged in company --> <company name="Company one" companyId="">
<!-- The po-tag specifies the user account used to access Pagero Online Attribute: Username The username in Pagero Online Password The user's password (remember to protect this config file) --> <po username="myUserName" password="mySecret"/>
<!-- The inbox-tag specifies where the received documents will be stored Attributes: active If true the inbox is fetched prodPath The path to the directory where incoming production documents will be stored testPath The path to the directory where incoming test documents will be stored tempPath The path to the directory where files will be temporary stored during fetching of documents. The files will then be moved to the final destination directory. This behavior is used to prevent providing incomplete files in the destination directory. documentType Type of document. Valid values are INVOICE, ORDER, ORDER_RESPONSE and DISPATCH_ADVICE. If empty value all types of documents will be fetched.
! All these directories shall be on the same disk to prevent copying of files to the destination directories.--> <inbox active="false" prodPath="c:/pagero/inbox/prod" testPath="c:/pagero/inbox/test" tempPath="c:/pagero/inbox/temp" documentType = "INVOICE"/> <!-- The outbox-tag specifies where the files to send will is stored
Attributes: active If true, the outbox is sent prodPath The path to the directory where outgoing production documents will be read from. testPath The path to the directory where outgoing test documents will be read from workPath The path to the directory where files will be temporary stored during sending and until they are completely processed. In the work Path a number of sub directories are created that shows the sent file's status. Temp The files are stored here during sending to Pagero Online. Sent The files are stored here when they are successfully sent to Pagero Online. Failed The files are stored here if they failed to send them to Pagero Online. Done The files are stored here when they are successfully processed by Pagero Online. Wait The files are stored here if they need manual handling by Pagero’s support. Normally this will be done within 24h during business hours. Error The files are stored here if there occurs an error that couldn’t be proccessed by Pagero Online. If this happens contacts are needed with Pagero Online.
subDocAware attachments enabled if true masterDocRegexp file name pattern for invoice subDocRegexp file name pattern for attachment subDocPresentationRegexp file name pattern for invoice image --> <outbox active="true" prodPath="c:/pagero/outbox/prod" testPath="c:/pagero/outbox/test" workPath="c:/pagero/outbox/work" /> </company> </poclient>