Installation and setup

To work with FrameMaker Publishing Server, do the following:

  1. Install FrameMaker Publishing Server

  2. Configure FrameMaker instance

  3. (Optional) Enable HTTP or HTTPS with Windows authentication (if you want to restrict access by switching on the authentication)

  4. Install a command line tool (Install a free command line tool, such as cURL, to access FrameMaker Publishing Server using the command line.)

  5. Manually install FMPS website in IIS

  6. (Optional) Enable HTTP ports for FMPS access from other network machines

  7. (Optional) Enable email

  8. Enable browse functionality through Java™ applet

    Note: For information on issues during installation, see FMPS troubleshooting

Install FrameMaker Publishing Server

To install FMPS, perform the following steps:

  1. Run the FMPS installer. The following Installation Options dialog appears:

    1. Select Adobe FrameMaker 2019.

    2. Select Adobe FrameMaker Publishing Server Components

      The installer also installs Microsoft deploy, registers IIS and its components for FMPS use, and installs basic website - the application settings of that website need to be edited manually in IIS.

    3. If you want to change the default install location, click the Browse icon next to the Location field and select a new destination.

    Important:

    On Windows 10 operating system, you might have to deploy the site manually. Follow the steps mentioned in the section

    Manually install FMPS website in IIS.
  2. Unzip the following WebServerUI.rar file.The default location of the WebServerUI.rar file is:

    Program Files\Adobe\Adobe FrameMaker Publishing Server Core 2019\www \WebServerUI.rar

    Important:

    The contents of the WebServerUI.rar file must be extracted within the same (www) folder.

  3. In the Internet Information Services (IIS) Manager, under Sites > fmps15> Application Settings (Under ASP.NET), change the following settings:

    1. Debug: Set the value to true to allow debugging.

    2. DebugLog: Enter path of the debug log that gets populated with error messages.

    3. FMPSBaseDir: The directory that would contain all tasks-related data.

    4. FMPSDomain: The domain name of FMPS. Use the network domain the machine belongs to or workgroup name if the machine is not on a domain.

    5. FMPSHelpDataEnabled: Set this to true to enable Server Help to be viewable by any user.

    6. FMPSPassword: Password associated with the user name entered in FMPSUserName.

    7. FMPSSchFolder: This folder contains FMPS scheduled tasks.

    8. FMPSUserName: user name for accessing FMPS (do not add the domain name here)

      Note: For running the tasks, user should be logged into the system using the account being set up as FMPSUserName.
  4. Go to Application pools > fmps15 > Advanced Settings > Process Model > Identity > Custom Account and set credentials as follows:

    1. User name: Enter <domain>\<username> keeping them same as the details entered in the step 3.

    2. Password: Enter the password you entered in step 3.

    3. Confirm Password: Re-enter your password.

  5. In a browser, open the website http://localhost:6234/index.html.

    Note: 6234 is the default port. You can configure a different port, in which case you should replace 6234 in all the examples in this document with the configured port number.

    The browser displays FMPS website's index.html page.

Configure FrameMaker instance

To optimize the performance of FrameMaker in automated publishing tasks, make the following changes to FrameMaker configuration. These changes are essential to run scheduled tasks on FMPS and modify the behavior in the following ways.

FMPS ignores unresolved cross-references, unresolved text insets, and missing graphics.

Enable HTTP or HTTPS with Windows authentication

  1. Open Web.config file from the following location:

    Program Files\Adobe\Adobe FrameMaker Publishing Server Core 2019\www

  2. To enable Windows authentication over HTTP, locate the following lines and uncomment them:

    <endpoint address="fmserver/v1" binding="webHttpBinding" contract="Server.IWebService" behaviorConfiguration="webhttp" bindingConfiguration="securehttp" />

    <endpoint address="" binding="webHttpBinding" contract="Server.IWebPage" behaviorConfiguration="webhttp" bindingConfiguration="securehttp" />

  3. To enable Windows authentication over HTTPS, locate the following lines and uncomment them:

    <endpoint address="fmserver/v1" binding="webHttpBinding" contract="Server.IWebService" behaviorConfiguration="webhttp" bindingConfiguration="securehttps" />

    <endpoint address="" binding="webHttpBinding" contract="Server.IWebPage" behaviorConfiguration="webhttp" bindingConfiguration="securehttps" />

    Note:

    By default the code is commented using the <!-- and --> tags. Remove the comment tags to use the code in the Web.config file.

  4. In the Internet Information Services (IIS) Manager, go to Sites > fmps15, select Authentication (under IIS) and enable Windows Authentication.

Note:

If you do not enable authentication, there is no need to pass the authentication-related parameters while accessing FMPS through APIs. For more information, see Working with FMPS using the APIs.

Enable HTTP or HTTPS without Windows authentication

  1. Open Web.config file from the following location:

    Program Files\Adobe\Adobe FrameMaker Publishing Server Core 2019\www

  2. To use HTTP without Windows authentication, locate the following lines and uncomment them:

    <endpoint address="fmserver/v1" binding="webHttpBinding" contract="Server.IWebService" behaviorConfiguration="webhttp" />

    <endpoint address="" binding="webHttpBinding" contract="Server.IWebPage" behaviorConfiguration="webhttp" />

  3. To use HTTPS without Windows authentication, locate the following lines and uncomment them:

    <endpoint address="fmserver/v1" binding="webHttpBinding" contract="Server.IWebService" behaviorConfiguration="webhttp" bindingConfiguration="securehttpswoauth" />

    <endpoint address="" binding="webHttpBinding" contract="Server.IWebPage" behaviorConfiguration="webhttp" bindingConfiguration="securehttpswoauth" />

    Note:

    By default the code is commented using the <!-- and --> tags. Remove the comment tags to use the code in the Web.config file.

  4. In the Internet Information Services (IIS) Manager, go to Sites > fmps15, select Authentication (under IIS) and disable Anonymous Authentication.

Install a command line tool

Install a command line tool, such as cURL, to pass commands to FMPS. cURL is a freeware command line tool.

Manually install FMPS website in IIS

If FMPS fails to install the IIS website, you can execute the deploy command to install the website. To manually install the FMPS website, log in as Administrator and complete the following steps:

  1. Go to FMPS installation folder.

    (Program Files\Adobe\Adobe FrameMaker Publishing Server Core 2019\deploy)

  2. Run the deploy.bat file in administrator mode with the following syntax:

    deploy.bat addsite -sitename <newsite> -port 6234 -physicalpath "<path>" addpool[or setpool] -poolname <newpool>

    In this command, provide values for newsite, path, and newpool.

    In the following example, the FMPS site is added to an existing pool:

    deploy.bat addsite -sitename fmps15 -port 6234 -physicalpath "C:\Program Files\Adobe\Adobe FrameMaker Publishing Server Core 2019\www" setpool -poolname fmps15

Enable HTTP ports for FMPS access from other network machines

To allow Win Server (example) for port access 6234, check if the HTTP ports for FMPS access from other machines is enabled. If it is not, enable the HTTP ports for FMPS access.

  1. Click Start, type Firewall.cpl, and then click OK.

  2. Click Advanced Settings.

  3. Check if an inbound traffic rule is already enabled or not. If it is not, then perform the following steps:

    1. Right-click Inbound Rules on the left pane.

    2. If a new rule by the name FMPS Port Open exists and is checked, the ports are already enabled and you do not need to go ahead with this task. If such a rule is not visible, create a new rule by following rest of this task.

    3. Select New Rule.

    4. Select Port.

    5. Under Specific Local Ports, enter your port number (Default is 6234. All the examples in this document use the port as 6234. If you have set the port to something else, replace 6234 in the examples with your port number).

    6. Continue clicking Next until the end of the wizard. Name the rule when prompted.

  4. Check if your port is now accessible - if required, restart the Windows Firewall service (under Services).

Enable email

Complete the following steps to enable email notifications of tasks (such as “Run successful” and “Run failed.”):

  1. Open server.ini file from the following location:

    Program Files\Adobe\Adobe FrameMaker Publishing Server Core 2019\

  2. Locate the Server flag and set its value to your mail server (Example: inner-relay-1.corp.abc.com).

    Note: Now you can specify email IDs for notifications while creating tasks.

Enable browse functionality through Java™ applet

Important: As Google has discontinued the support for NPAPI, which is used by the browse functionality, we recommend using alternates to the Chrome browser.
Note: You need to have the latest JRE installed on your client machines to use this functionality.

When you launch the FMPS website, the browser prompts you for permission to run Java applet. Allow the browser to run the Java applet to enable browse functionality in FMPS.

Otherwise, while opening various files in FMPS, enter the path and name of the files manually.


August 22, 2018

Legal Notices | Online Privacy Policy