Installing the SNS and SUS

The SNS, SNS Administration webpage and SUS is packaged as a single JEE application. The SNS is based on JAX-WS, the METRO web services stack, and JPA for persistency. The SNS Administration webpage and the SUS is based on JSP, Servlets and Javascript. The SNS, SNS Admin webpage and SUS is delivered as a war file to be installed in your JEE application server.

4 war files are delivered:

Installing on a generic JEE application server #

The delivered sns.war is a generic version of the SNS. This can be used to run the SNS on a JEE application server that is not otherwise detailed here.

Modules:

• JAX-WS - METRO (provided by JEE application server)
• JPA - Hibernate (provided by JEE application server)

Please follow the instructions provided with your application server on how to install an application from a war file.

The following additional items need to be configured to run the SNS:

• A JNDI Datasource with the name jdbc/sns needs to be defined in the application server
• A user with the assigned user role, sns-admin

Please refer to your application server documentation on how to set up these resources on your specific application server.

Once these steps are complete, you can point your browser at the following page to access the Admin webpage:
http://<host location>:<port>/sns/admin.sics

Installing on WebSphere #

The websphere.sns.war file is a version of the SNS which is configured for running on the WebSphere application server.

Modules:

• JAX-WS - METRO (provided by war file)
• JPA - Hibernate (provided by war file)

Rename the file to sns.war, and then install the application using the “Integrated Solution Console” for WebSphere.

The following additional items need to be configured to run the SNS:

• A JNDI Datasource with the name jdbc/sns needs to be defined in the application server
• A user with the assigned user role, sns-admin

Extra Configuration

To run the SNS correctly on WebSphere, the classloading options for the application must be changed.

From the “Enterprise Applications” menu in the “Integrated Solution Console”, select the newly installed SNS application.

From detail Properties section, select “Class loading and update detection”

Make sure the settings on the “General Properties” are as shown on the screen shot to the right and press OK (You might also need to supply a “polling interval for updated files”, enter a sensible number, for example 3600, to pass page validation)

Save the changes to the application configuration and start the application.

Once these steps are complete, you can point your browser at the following page to access the Admin webpage:
http://<websphere location>:<port>/sns/admin.sics

Known Issues on WebSphere:

• The logout button does not correctly log the user out of the application.

Installing on Tomcat WEB CONTAINER #

The delivered tomcat.sns.war is a version of the SNS which is configured to run in the Tomcat web container.

NOTE: Tomcat 10.1 or newer must be used.

Modules:

• JAX-WS - METRO (provided by war file)
• JPA - Hibernate (provided by war file)

Rename the file as sns.war.

You can either install the application using the tomcat admin console, or simply copy the sns.war file to the “webapps” folder of tomcat.

The following additional items need to be configured to run the SNS.

A JNDI Datasource with the name jdbc/sns needs to be defined in the application server.

The tomcat.sns.war war file contains a sample context.xml file which can be found in the /META-INF directory. This file details how to setup a JNDI database connection for use with the SNS.

A user with the assigned user role, sns-admin.

In the tomcat conf directory, create the file tomcat-users if it does not already exist. If the file already exists, edit it. A new <role> sns-admin needs to be defined and a user mapped to this roll. The example file below shows, shows the definition of the role, and a single user called snsAdmin which is mapped to this role.

<tomcat-users>
<rolerolename="sns-admin"/>
<userusername="snsAdmin"password="snsAdmin"roles="sns-admin"/>
</tomcat-users>

Once these steps are complete, you can point your browser at the following page to access the Admin webpage
http://<tomcat location>:<port>/sns/admin.sics

Installing on GLASSFISH JEE APPLICATION SERVER #

The delivered glassfish.sns.war is a version of the SNS which is configured to run on the Glassfish application server.

Modules:

• JAX-WS - METRO (provided by Glassfish)
• JPA - EclipseLink (provided by Glassfish)

Rename the file as sns.war

Start glassfish and connect to the admin console. Use the admin console to install the SNS war file. The following additional items need to be configured to run the SNS

A JNDI Datasource with the name jdbc/sns needs to be defined in the application server

Refer to the Glassfish documentation on how to define a JNDI database connection.

A user with the assigned user role, sns-admin

Refer to the Glassfish documentation to set up a user(s) within Glassfish that will use the SNS Admin webpage.

The glassfish.sns.war file contains the file glassfish-web.xml under the /WEB-INF folder. This file is used to configure users’ role mapping within the application. The default file is shown below, and the can be seen that the user snsAdmin has been assigned the required sns-admin role.

<glassfish-web-app>
<security-role-mapping>
<role-name>sns-admin</role-name>
<principal-name>snsAddmin</principal-name>
</security-role-mapping>
</glassfish-web-app>

Once these steps are complete, you can point your browser at the following page to access the Admin webpage:
http://<glassfish location>:<port>/sns/admin.sics