There are two installation guides for the Web Monitor. With and without a DMZ server.

images/download/attachments/44072997/Web_Monitor_1-version-3-modificationdate-1592895516279-api-v2.png

Installation Example with DMZ

If external partners and employees get remote access to the Web Monitor and you have a DMZ server, it makes sense to use the described installation option. If the Web Monitor is only used internally by your employees, it might rather make sense to install it on the Lobster_data server and only access it locally. In any case, the data for the Web Monitor is only stored once and is kept up to date by a log replication service with the help of an internal log event listener. To be able to do that, the log replication service needs a database on the DMZ server (or you allow access to the Lobster_data database on the internal network). Files (e.g. job input files, not the configuration files!) are not replicated, but ordered 'on demand' with messages on port 8020 and delivered to the Web Monitor via DMZ server from the Lobster_data Integration Server.

Create a Database on the DMZ Server

In this example, we assume a MySQL database. Please create a new database webmon and a database user on the DMZ server. This database has to be accessible via TCP/IP from the Lobster_data server and the database user has to have appropriate permissions. Insert the following segment in file ./etc/database.xml on the DMZ server.

Example:

<Call name="initPool">
    <Arg>
        <New class="com.ebd.hub.services.database.DatabaseSettings">
            <Set name="alias">webmon</Set>
            <Set name="allowGrowing">True</Set>
            <Set name="database">jdbc:mysql://127.0.0.1:3306/webmon</Set>
            <Set name="driver">com.mysql.jdbc.Driver</Set>
            <Set name="user">dummy</Set>
            <Set name="password">OBF:1wtm1xtz1w8v1xtj1wus</Set>
            <Set name="minSize">2</Set>
            <Set name="idleTime">300000</Set>
            <Set name="sqlCommand">select 1 from dual</Set>
         <Set name="rollback">True</Set>
         <Set name="caching">True</Set>
         <Set name="catalogName">webmon</Set>
        </New>
    </Arg>
</Call>

Adjust File ./etc/startup.xml

Now insert the following segment in configuration file ./etc/startup.xml on the DMZ server.

Example:

<Call name="addApplication"><Arg>
    <New class="de.lobster.webmon.apps.WebMonitor">
        <Set name="alias">webmon</Set>
        <Set name="remoteHost">192.168.0.99</Set>
        <Set name="remotePort">8020</Set>
        <Set name="mailSender">some_user@example.com</Set>
		<Set name="mailSenderForPassword">some_user@example.com</Set>
        <Set name="retainHeaderLogs">999</Set>
        <Set name="cleanUpTime">2</Set>
    </New>
</Arg></Call>

Important notes: Please use the IP of your Lobster_data server instead of the IP 192.168.0.99. Parameter retainHeaderLogs sets the number of days (integer) header logs are kept. Detail logs are kept as long as they are kept in Lobster_data. Parameter cleanUpTime configures the time (24 hours, integer) at which outdated entries shall be deleted.

Note: Make sure to include the following segment in file ./etc/startup.xml on the DMZ server, otherwise, it will not be possible to recover passwords via email!

<Call name="addApplication"><Arg>
    <New class="com.ebd.util.net.mail.HubStartupConfiguration">
        <Call name="setMailSettings">
            <Arg>mail.lobster.de</Arg>
            <Arg type="int">25</Arg>
            <Arg>info@lobster.de</Arg>
            <Arg>my_password_obfuscated</Arg>
        </Call>
    </New>
</Arg></Call>

Adjust HTML Start Page (Flex Client)

You will find template index.html in folder ./webapps/root/webmonitorFlex' on the DMZ server. Feel free to adapt it to your corporate identity.

Note: Please notice the comments explaining the settings.

Example:

...
<script type="text/javascript" src="assets/swfobject.js"></script>
<script type="text/javascript">
<!-- For version detection, set to min. required Flash Player version, or 0 (or 0.0.0), for no version detection. -->
var swfVersionStr = "10.0.0";
var xiSwfUrlStr = "playerProductInstall.swf";
var flashvars = {};
 
<!-- Optional CSS file to modify the design of the application.
If this entry does not exist, file "assets/WebMonitorStyle.css" will be loaded.
If that file does not exist either, the Lobster standard design is loaded.
-->
flashvars.styleCSS = "assets/MyWebMonitorStyle.css";
          
<!-- Alternatively, an SWF file can be loaded to modify the design.
If this entry does not exist, file "assets/WebMonitorStyle.swf" will be loaded.
If both the CSS and SWF file exist, the SWF file will be loaded first and then 
the CSS file. Parts might be overwritten if necessary.
-->
flashvars.styleSWF = "assets/MyWebMonitorStyle.swf";        
             
<!-- Optional image file that is shown on the login screen. If it does not exist,
file "assets/welcome.png" will be used. If that file does not exist either, the
standard image file will be used.
-->
flashvars.welcomeImage = "assets/welcome.png";
                 
var params = {};
params.quality = "high";
params.bgcolor = "#eefbf2";
params.allowscriptaccess = "sameDomain";
params.allowfullscreen = "true";
var attributes = {};
attributes.id = "FlexWebMonitor";
attributes.name = "FlexWebMonitor";
attributes.align = "middle";
swfobject.embedSWF(
"FlexWebMonitor.swf", "flashContent",
"100%", "80%",
swfVersionStr, xiSwfUrlStr,
flashvars, params, attributes);
<!-- JavaScript enabled so display the flashContent div in case it is not replaced
with an SWF object. -->
swfobject.createCSS("#flashContent", "display:block;text-align:left;");
</script>
...

Set Up Lobster_data Server (with DMZ)

File ./etc/database.xml on the Lobster_data server also has to contain the alias webmon and the URL has to be the URL (external not local) of the DMZ server.

File ./etc/startup.xml (with DMZ)

The section for the Web Monitor in file ./etc/startup.xml on the Lobster_data server is similar to the section for the Web Monitor in configuration file ./etc/startup.xml on the DMZ server, with the exception that the argument remoteHost has to stay empty!

Example:

<Call name="addApplication"><Arg>
    <New class="de.lobster.webmon.apps.WebMonitor">
        <Set name="alias">webmon</Set>
        <Set name="remoteHost"></Set>
        <Set name="remotePort">8020</Set>
        <Set name="mailSender">info@lobster.de</Set>
        <Set name="retainHeaderLogs">999</Set>
        <Set name="cleanUpTime">2</Set>
    </New>
</Arg></Call>

Please also insert the following line in the section for the configuration of Lobster_data (<Call name="addApplication"><Arg><New class="com.ebd.hub.datawizard.app.DataWizardSetup">).

<Set name="webMonitorAlias">webmon</Set>

This will activate the replication of log entries and install a subscriber on the Lobster_data server for file requests (messages) of the DMZ server.

Installation Without DMZ

If you want to use the Web Monitor without a DMZ, the file ./etc/startup.xml on the Lobster_data server has to be configured as described in the previous chapter.

Instead of alias webmon please use the alias that is used as logAlias for Lobster_data (default is hub)! Do not use the entry <Set name="webMonitorAlias">webmon</Set>

Additionally, there is no argument remoteHost allowed in entry webmonitor!

Note: So there is no log replication happening here.

Testing the Web Monitor

images/download/attachments/44072997/Web_Monitor_5_EN-version-1-modificationdate-1568171458000-api-v2.png

Please open your browser and type in the URL http://<IP_of_Lobster_data_or_DMZ>. Instead of Lobster_data, choose the Web Monitor. The direct link is http://<IP_of_Lobster_data_or_DMZ>/WebMonitor2.

You can also directly enter your login data in the direct link with http://<IP_of_Lobster_data_or_DMZ>/WebMonitor2/?user=<user>&password=<password>&language=en

You will see the page above. Initially, the user and password will be admin (also see section Quick Guide Web Monitor).