06 February 2009

Adobe Content Server 4 (ACS4) Setup Guide - Part 3

Setting Up the Configuration Files

By default, these files are named:
  • admin-conf.txt
  • fulfillment-conf.txt
  • packaging-conf.txt
And they are located, by default in: C:\config\ on Windows and /etc on Linux.

Create the folder C:\config\ and put the configuration files there.

None of the config files have any values filled in. Add in the proper values next.

First, set up the admin console configuration since it is the simplest and the others are essentially extensions of it.

Admin Console Configuration

The first two lines are about what to log and where to put that information.
The next three lines specify the type of database and the driver to be used and the path through which Content Server can find it.
The next two lines are the ID and password of the user you created when you created the database.
The last line in the file is the URL to where the admin WAR can be found, complete with the port (if it is not port 80).

When entering the serviceURL there should be no spaces before or after the URL.
And that's it, after completion it should look something like this:
  • com.adobe.adept.log.level=trace
  • com.adobe.adept.log.file=C:\acs4\log\fulfillment.log
  • com.adobe.adept.persist.sql.driverClass=com.mysql.jdbc.Driver
  • com.adobe.adept.persist.sql.dialect=mysql
  • com.adobe.adept.persist.sql.connection=jdbc:mysql://
  • com.adobe.adept.persist.sql.user=dbusername
  • com.adobe.adept.persist.sql.password=dbpassword
  • com.adobe.adept.serviceURL=http://yourdomain.com:8080/admin
You must always restart the Tomcat service after modifying the configuration files (since they are only read during the Tomcat startup), so restart Tomcat now.

You can test that the admin.war is properly configured.
Go to a browser and enter the service URL plus /statuscheck,

e.g. http://yourdomain.com:8080/admin/statuscheck

You should get all green marks, if you get errors then try the following verbose report method:


This will give you more detailed information.

The most common problem of configuration is simply mistyping an address or value.
Also check for trailing spaces or spaces around the equals sign for properties.
Double check all the values.

Starting the Admin Console

As a final test that you have the configuration for the Admin Console correct, start it up.
To launch the admin console, enter into your browser the path to the admin console,

e.g. http://yourdomain.com:8080/admin/console

Note: The client machine must have Flash Player 9 (or higher) installed to run the Admin Console application.

The Admin Console will prompt you for a password.

The default password is park345 and once you have entered that it will then prompt you to enter a new password. Note that this password is the one for the built-in distributor, as opposed to distributors that you will create.

You can think of this as the Content Server password, but it will normally be referred to as the password for the built-in distributor.

Once you have done that you will see the Admin Console.

The Admin Console isn't too interesting right now because you haven't packaged any books yet.

Fulfillment Configuration

Now set up the fulfillment configuration. The config file is basically the same information as that in the admin config file plus the properties specific to fulfillment.

The first line that differs is the URL to the actual fulfillment server:


This URL must include the port info if it is not port 80.
In this case, Tomcat is on port 8080 so we need to include this.

This URL must match exactly that which was specified when the certificate was created.
Do not use spaces before or after the equal sign, as this will cause a problem when determining if the URLs match.

The first new property specifies which of the two license-signing services Content Server will call to get licenses signed.

If you are in Canada or the US, you should specify:


Otherwise, specify


The last 3 lines are the location of the PKCS12 file, the certificate ID, and certificate password.
  • com.adobe.adept.fulfillment.security.pkcs12.file=file:///C:/ACS4/operator.p12
  • com.adobe.adept.fulfillment.security.keystore.user=operator
  • com.adobe.adept.fulfillment.security.keystore.password=password
So the final fulfillment config contents are:
  • com.adobe.adept.log.level=trace
  • com.adobe.adept.log.file=C:\ACS4\log\fulfillment.log
  • com.adobe.adept.persist.sql.driverClass=com.mysql.jdbc.Driver
  • com.adobe.adept.persist.sql.connection=jdbc:mysql://
  • com.adobe.adept.persist.sql.dialect=mysql com.adobe.adept.persist.sql.user=dbuser
  • com.adobe.adept.persist.sql.password=dbpassword
  • com.adobe.adept.serviceURL=http://yourdomain.com:8080/fulfillment
  • com.adobe.adept.fulfillment.security.licensesignURL=https://nasigningservice.adobe.com/licensesign com.adobe.adept.fulfillment.security.pkcs12.file=file:///C:/ACS4/operator.p12 com.adobe.adept.fulfillment.security.keystore.user=operator
  • com.adobe.adept.fulfillment.security.keystore.password=password
Again, the URL to the fulfillment status would be:


Or append Status?verbose=true in place of statuscheck for more info

Packaging Configuration

The packaging configuration, like the fulfillment configuration file, is the same as the admin console configuration file with the addition of the packaging-specific properties.

The service URL is of course pointing to the packaging .war file:


The next two lines specify the destination of the packaged file and how it will be deployed for download.

The baseLocation is where on the destination server's storage the book will be placed.
The baseURL determines at what apparent URL the book will be.

Note that the baseLocation has to be relative to the Tomcat instance.

The default installation of Tomcat is:

C:\Program Files\Apache Software Foundation\Tomcat 6.0

Tomcat addressing is relative to that location.

So if you want the baseLocation to be ebooks, then the baseLocation property has to be relative to the ROOT folder of the Tomcat folder,

e.g .\webapps\ROOT\

So for example, if the baseLocation is .\webapps\ROOT\media and the baseURL is http://yourdomain.com:8080/ebooks then when the book foo.epub is added it will be at the path .\webapps\ROOT\media\foo.epub and will be available (via Tomcat services) at http://yourdomain.com/ebooks/foo.epub.

Of course, this is a function of how the Apache HTTP and Tomcat services are configured, but the above is true for a normal set up.

So here are the resulting packaging-conf.txt contents:
  • com.adobe.adept.log.level=trace com.adobe.adept.log.file=C:\acs4\log\packaging.log
  • com.adobe.adept.persist.sql.driverClass=com.mysql.jdbc.Driver
  • com.adobe.adept.persist.sql.connection=jdbc:mysql://
  • com.adobe.adept.persist.sql.dialect=mysql
  • com.adobe.adept.persist.sql.user=dbuser
  • com.adobe.adept.persist.sql.password=dbpassword
  • com.adobe.adept.serviceURL=http://yourdomain.com/packaging
  • com.adobe.adept.packaging.baseLocation=.\webapps\ROOT\media
  • com.adobe.adept.packaging.baseURL=http://gort.corp.adobe.com:8080/media
Restart Tomcat one more time then check the status of the packaging service.

The URL to the packaging status would be:

Or append Status?verbose=true in place of statuscheck for more info.

Now that Content Server is working, lets package some books.

To continue click here

No comments:

Post a Comment