Setting up web front end

Setting up the Internet module (Internet Administration Console) (Obsolete since Product 360 8.0)

This chapter is obsolete since Product 360 8.0. For reasons of compatibilty to Product 360 versions < 8.0 this chapter is still remaining in Product 360 version 8.0 documentation.

The procedure for setting up the Internet module is as follows:

  1. Start the Tomcat server if it is not already running.

  2. Start the Internet module using the OPAS_xob.exe program from the oxobjsrv directory in your local Product 360 - Media Manager installation.

  3. Navigate to Presettings > Presettings and, in the subsequent window, go to the Master 1 tab. Make the following settings on this tab:

    • Should a log be kept?

    • Time contingent for user in minutes controls the timeout for users who are logged into the Internet module.

      A value of 30 minutes is recommended.

    • Max. number of displayed records per search defines the number of hits a search will return.

      A value of 500 is recommended.

    • Max. data quantity in MB that may be transmitted via the module defines how many Megabytes of data can be downloaded using the Internet module. Downloading of larger volumes of data terminates with an error message.

      A value of 100 is recommended.

    • Should the e-mails be sent with the Pipeline module?: If you activate this setting, e-mails are sent using the Pipeline module rather than the Internet module.

    • URL of dindex page for workflow e-mail processing: In some e-mails, paths to the dindex page are specified in order to enable direct access to the web application.

      This setting should only be made after the Tomcat server has been configured. There you can copy the path to the page from the web browser and enter the prefix d before index.

    • Should previews of job components be generated via the pipeline?

      To relieve the load on Internet module you can use the Pipeline module to generate previews.

    • Should MEDIAS previews be cached?: If you activate this option, previews of MEDIAS objects are buffered, which means that they do not have to be retrieved from the content and media database each time they are called up.

      This speeds up the page layout process in the web application.

  4. Go to the Master 2 tab:

    • Under Station number of this computer, enter the local Product 360 - Media Manager workstation number.

    • It is recommended that you enable communication with the Session Manager.

    • Enter the IP address of this computer.

    • Under Port of this computer, define a port range, e.g. 85-94.

    • Specify a port to communicate with the Session Manager (default 81).

    • Path to the working directories of this computer: Click on the relevant button to select the directory. It is recommended to use UNC paths.

      The directory is part of the Web application (Windows: C:\OpasGWebServer\workdir). If necessary, enable this directory in the network.

    • Max. time limit for a TCP/IP packet (in seconds) is set to 5 seconds by default.

    • Sleep time between the individual requests (in ms) is set to 10 milliseconds by default.

    • Integrate watermark starting from which pixel dimension is set to 150 by default.

      This setting determines the image size in pixels above which a watermark will be integrated.

  5. Click on Save to save your entries.

  6. You have to restart the Product 360 - Media Manager Internet module.

You can call up the Product 360 - Media Manager web front end using http://<IP address of Tomcat computer>:8080/opas/index.jsp.

Setting up the Session Manager (Obsolete since Product 360 8.0)

This chapter is obsolete since Product 360 8.0. For reasons of compatibilty to Product 360 versions < 8.0 this chapter is still remaining in Product 360 version 8.0 documentation.

The Session Manager is part of the Web application and, after installation, is located in the directory e.g. C:\OpasGWebServer\XOBSessionManager.

  1. In the file server.xml in the directory [XOBSessionManager]\conf, adapt the following values:

    1. <ServerPort value="81"/>: Depending on the free port or the port to be used.

    2. <WebPort value="8089"/>

    3. <LogLevel value="7"/>

    4. <server IP="192.168.25.170" Port="82" Prio="5" Active="Y"/>

    5. <server IP="192.168.25.215" Port="86" Prio="2" Active="N"/>

      The priority Prio allows more powerful computers to be utilized more intensively. 1 is the highest priority, 20 the lowest.

      The Internet module can be activated and deactivated using Active.

      Under IP enter the IP address of the computer on which you want to install the Internet module.

  2. Save all your entries.

  3. Start the Session Manager using startup.bat.

You can also start the Session Manager as a Windows service; refer to Run Product 360 - Media Manager server modules as a Windows service.

You can query the status of the Session Manager under http://localhost:[Port for info page]/ in your browser.

Adapt the file Base.cfg so that the Web application submits your queries via the Session Manager.