Out of the box, SuperWEB2 is configured to connect to an instance of SuperSERVER and SuperADMIN running on the same machine as the Tomcat server. In most production situations, these will typically be installed on separate machines, in which case you must configure the connection between SuperWEB2 and the instance running SuperADMIN Server.
- Follow the standard installation instructions for SuperWEB2.
- Run Tomcat at least once so that the contents of the SuperWEB2 War file get extracted to the <tomcat_home>\webapps directory.
Open the file <tomcat_home>\webapps\webapi\WEB-INF\data\.repository\administrationServerCatalog.xml in a text editor.
Make a backup copy of this file before making any changes.
Locate the following section of the file:XML
<sa:administrationServer id="defaultprofile"> <sa:host corbaport="9230" registryport="9234" rmiport="9231">localhost</sa:host> <sa:configServer protocol="http" host="localhost" port="9000" basePath="/v1/config" /> </sa:administrationServer>
localhostwith the hostname of the machine running SuperADMIN Server. You may also need to change the port numbers if you are running on non-standard ports.
To avoid potential DNS issues, you should ensure you use a fully qualified domain name wherever possible,
Save the changes to administrationServerCatalog.xml and restart Tomcat.
If you are using the Open Data API, then be aware that this has its own instance of the administrationServerCatalog.xml file, located in <tomcat_home>\webapps\webapi#rest#v1\WEB-INF\data\.repository
You must also apply these changes to that version of the file too (the Open Data API will not use SuperWEB2's instance when determining which SuperSERVER instance to connect to).