Administration guide > Secure the deployment environment > Tutorial: Integrate WebSphere eXtreme Scale security with WAS > Module 2: Configure WebSphere eXtreme Scale to use WAS Authentication plug-ins


Secure the deployment environment > Tutorial: Integrate WebSphere eXtreme Scale security with WAS > Module 2: Configure WebSphere eXtreme Scale to use WAS Authentication plug-ins >

< Previous | Next >


Lesson 2.4: Install and run the sample

After authentication is configured, you can install and run the sample application.


Create a shared library for the EmployeeData.jar file

  1. In the WebSphere Application Server administrative console, open the Shared Libraries page. Click Environment > Shared libraries.

  2. Choose the cell scope.

  3. Create the shared library. Click New. Enter EmployeeManagementLIB as the Name. Enter the path to the EmployeeData.jar in the classpath, for example, samples_home/WASSecurity/EmployeeData.jar.

  4. Click Apply.


Install the sample

  1. Install the EmployeeManagement.ear file.

    1. To begin the installation, click Applications > New application > New Enterprise Application. Choose the detailed path for installing the application.

    2. On the Map modules to servers step, specify the appCluster cluster to install the EmployeeManagementWeb module.

    3. On the Map shared libraries step, select the EmployeeManagementWeb module.

    4. Click Reference shared libraries. Select the EmployeeManagementLIB library.

    5. Map the webUser role to All Authenticated in Application's Realm.

    6. Click OK.
    The clients run in the s1 and s2 servers in this cluster.

  2. Install the sample XSDeployment.ear file.

    1. To begin the installation, click Applications > New application > New Enterprise Application. Choose the detailed path for installing the application.

    2. On the Map modules to servers step, specify the xsCluster cluster to install the XSDeploymentWeb web module.

    3. On the Map shared libraries step, select the XSDeploymentWeb module.

    4. Click Reference shared libraries. Select the EmployeeManagementLIB library.

    5. Click OK.
    The xs1 and xs2 servers in this cluster host the container servers.

  3. Restart the deployment manager. When the deployment manager starts, the catalog server also starts. If you look at the SystemOut.log file of the deployment manager, you can see the following message that indicates that the eXtreme Scale server properties file is loaded.

    CWOBJ0913I: Server property files have been loaded: 
    /wxs_samples/security/catServer2.props.
    

  4. Restart the xsCluster cluster. When the xsCluster starts, the XSDeployment application starts, and a container server is started on the xs1 and xs2 servers respectively. If you look at the SystemOut.log file of the xs1 and xs2 servers, the following message that indicates the server properties file is loaded is displayed:

    CWOBJ0913I: Server property files have been loaded: 
    /wxs_samples/security/server2.props.
    

  5. Restart the appClusters cluster. When the cluster appCluster starts, the EmployeeManagement application also starts. If you look at the SystemOut.log file of the s1 and s2 servers, you can see the following message that indicates that the client properties file is loaded.

    CWOBJ0924I: The client property file {0} has been loaded.
    

    You can ignore the warning messages regarding the authenticationRetryCount, transportType, and clientCertificateAuthentication properties. The default values are be used because the values were not specified in the properties file. If you are using  WebSphere eXtreme Scale v7.0, the English-only CWOBJ9000I message displays to indicate that the client property file has been loaded. If you do not see the expected message, verify that you configured the -Dobjectgrid.server.props or -Dobjectgrid.client.props property in the JVM argument. If you do have the properties configured, make sure the dash (-) is a UTF character.


Run the sample application

  1. Run the management.jsp file. In a web browser, access http://<your_servername>:<port>/EmployeeManagementWeb/management.jsp. For example, you might use the following URL: http://localhost:9080/EmployeeManagementWeb/management.jsp.

  2. Provide authentication to the application. Enter the credentials of the user that you mapped to the webUser role. By default, this user role is mapped to all authenticated users. Type admin1 as your user ID and admin1 as the password. A page to display, add, update, and delete employees displays.

  3. Display employees. Click Display an Employee. Enter emp1@acme.com as the email address, and click Submit. A message displays that the employee cannot be found.

  4. Add an employee. click Add an Employee. Enter emp1@acme.com as the email address, enter Joe as the first name, and Doe as the last name. Click Submit. A message displays that an employee with the emp1@acme.com address has been added.

  5. Display the new employee. Click Display an Employee. Enter emp1@acme.com as the email address with empty fields for the first and last names, and click Submit. A message displays that the employee has been found, and the correct names are displayed in the first name and last name fields.

  6. Delete the employee. Click Delete an employee. Enter emp1@acme.com and click Submit. A message is displayed that the employee has been deleted.


Lesson checkpoint

You installed and ran the sample application. Because this tutorial uses WebSphere Application Server integration, you cannot see the scenario when a client fails to authenticate to the eXtreme Scale server. If the user authenticates to the WebSphere Application Server successfully, eXtreme Scale is also successfully authenticated.

< Previous | Next >