Skip to main content

How-To Handling Several Projects on One Publishing Server

1 Introduction​

If you have to run several projects on one PubServer you have to handle additional configurations. Here is a description of what to pay attention to.

2 Prerequisites​

The information in the document refers to priint:suite 4.x and all later versions.

2.1 Technical Requirements​

To be able to use this document you (or a colleague)

  • must be familiar with database handling and must have administrator rights at least for the project specific databases.
  • must be familiar with the Payara™ Server Admin Console and must have rights to handle the Ressources.

3 Publishing Server Installation Software​

3.1 Repository Setup​

During the publishing server installation (running install.bat on devstack/update)…

 

  … you have to setup amongst other things the repository:

 

  The setting here defines the Model in the Entity Explorer and the Project in the CometExplorer in Ison:

 

3.2 In the background​

What you do not see on the Repository Setup page are some automatically assigned settings, among others the connection to a database. You’ll get the connection via the setting of the “JDBC Resource” (see the picture in chapter 5). A JDBC Resource is used in the GlassfishTM Server to assign a JDBC Connection Pool which in turn defines all settings for the used datasource.

So what is to do to be able to run a 2nd project on your PubServer?

  4 Preparation​

  • The database administrator must create a clone of the database “comet_data”.
  • Then he must define a new JDBC Connection Pool (on the GlassfishTM Admin Console) which points to the database from step 1:

 

  • Last but not least he creates a new JDBC Resource for the pool from step 2 - e.g. call “resource2”:

5 New Ison Project​

After that preparations you are able to create a correct new Ison Project:

 

  Here you point to the new created database via the setting”JDBC Resource: resource2”.

That was it!