|What is a backend?|
A backend is where the uploaded PDFs are processed, and where the user is directed after upload to fulfill his order (payment, order status, reorder, personal information, order details, etc.). In the 3P Starter Edition, you need to create your own backend. For the upload interface, you can use our 3P Upload Connector in PHP or write your own.
|As the publisher is tied to a printing provider, will there be a need to modify the existing application so that it can upload to an existing service?|
The Publisher has a failsafe upload interface, which works with SessionIDs and TicketIDs. We have a demo upload connector written in PHP, which receives the PDF files and puts them in the TickedID folder. It’s pretty straight forward. You will probably have to make minor changes in your database.
|Will there be a need to provide a publicly accessible ftp account for direct uploads?|
No, it’s all http. It is not recommended to use FTP, because this protocol is deactivated in many companies and firewalls.
|Are there other additional requirements for integrating to existing application that we need to be aware of?|
You need to provide an AutoUpdate folder on a webserver, where all update files are kept, like the Products.xml, which contains all product descriptions, options and prices. These files are downloaded by the installations through certain rules and intervals. You also need to be able to read this Products.xml from your backend, in order to see what product the user just uploaded and to reflect his chosen product options in the storefront.
|As the project files are encrypted locally, in which format are the pages stored on the server?|
In PDF format with optional password.
|Do I need to install tools to decrypt uploaded content?|
We provide a DTP-to-PDF format converter, if you are using OPI (highres replacement of images).
Note: OPI has meanwhile been deprecated. A similar feature involves crypted resource images, which are replaced shortly before upload.
|What is the file naming conversion that are used to store uploads on the server?|
It’s up to you. The upload connector receives files and stores them according to TicketID and SessionID.
|Before/after uploads how is the information relating to a specific order stored in the database? Should the database for the order have a specific structure?|
It’s up to you.
|Does the publisher require any form of secured connection to the service provider, i.e. SSL?|
It’s up to you. We recommend http for file upload and https for store entry. If you use https urls inside the products.xml, you need to add two DLL libraries to your SetupWizard source folder: ssleay32.dll and libeay32.dll
|While uploading, does the content pass through your servers or any service from your server before been sent to the service provider’s server?|
No, directly to your backend.
|Do you collect information from users of the application? E.g. Name, IP, location, project information?|
We only log successful uploads to be able to calculate the activity fee (AUF) and provide support. This information is anonymous and only for internal use (see Reseller Cooperation Contract for details).
|If a project is saved and a client needs to burn the project to CD and bring it with him/her to the studio, is it only the .dtp file that should be copied onto the CD/flash or any type of storage device?|
In offline mode the user burns one folder. The burning is automatic, as the Publisher comes with a burning tool.
|There is a provision to obtain pictures from google picasa, stock.xchng?|
The resource links from where to download images can be adjusted by you. It’s up to the user to check the licensing of the images. You can also purchase commercial gallery and objects resources directly from us, or provide your own image libraries.
|Does the Publisher application require any special server configuration to be able to operate seamlessly?|
You need to implement the upload connection, provide an AutoUpdate folder and parse the Products.xml file in order to reflect the selected product options in your storefront.
|Do you require access to our server?|
No. We have no insight into your customer and order database.
|On the event of migrating from one server to the other/disaster recovery, what form of assistance to you provide to your clients?|
All you URLs should point to a redirect script, which delegates to the main server. This way, servers can be replaced or upgraded.