This step assumes that you have successfully installed the JDK5, SJSAS, JWSDP, MySQL, configured the JDBC driver and created the StrongKey schema in MySQL. If not, please finish that before continuing with this step. It also assumes that you have downloaded the StrongKey distribution and extracted it into a directory called /usr/tmp. If you have extracted the distribution in a different directory, substitute that directory for /usr/tmp.

It also assumes you have extracted the skcl.zip file and the etc.zip file into the /usr/local/etc/symkey directory.

1

Using a browser, log into the Admin Server console using the Admin ID and password you chose during installation.

If your ID and password were correct, you will see the Application Server's administrative interface.

2

Click on Applications and then Enterprise Applications in the left-hand pane of the Admin Server. If the Enterprise Applications item is already visible on the menu, then just click on it.

You should see a form for Enterprise Applications, with a Deploy... button as follows:

3

Click on the Deploy... button. You should see a Deploy Enterprise Application form as follows:

4

Either type in /usr/tmp/symkey/symkey.ear in the File To Upload field, or click on the Browse.. button and navigate to this file and select it.

Click on the Next button at the top to continue. You should see a more detailed form.

Ensure that the Application Name field says symkey

Ensure that the Virtual Servers field says server

Ensure that the Status field is checked to indicate Enabled.

Your form should look like the following:

5

Click on OK to continue.

After a few minutes – exactly how long it takes will depend on the capability of the machine on which you are deploying the application – you will see the Enterprise Applications form showing the symkey application, and the Enabled column will state true (as follows):

6

Click on Application Server on the sidebar on the left.

You should see the main panel display a number of tabs.

7

Click on the tab marked JVM Settings

You should see a form displayed with a sub-menu and the JVM General Settings form.

8

Click on the sub-menu Path Settings item

You should see a form with the title JVM Classpath Settings

9

Go down to the section marked Classpath Prefix:

10

Insert your cursor before the first character of the first line and press the Enter key on your keyboard.

This should insert a blank line at the top of this field.

11

Add the following text in the blank line

${com.sun.aas.installRoot}/domains/domain1/applications/j2ee-apps/symkey/jaxb.jar

Please be aware that this is all a single, unbroken line and that the parentheses surrounding com.sun.aas.installRoot are not regular parentheses, but curly braces.

Your form should look like the following:

12

Click on the Save button.

You should see the form respond with New values successfully saved and a Restart Required at the top-right corner of the browser.

But don't restart the server yet! You have one more task to finish before restarting the Application Server.

13

In a shell terminal/Command Prompt window, change directory to the /usr/local/sjsas82/domains/domain1/config directory, using:

cd /usr/local/sjsas82/domains/domain/config

Windows uers can use Windows Explorer to navigate there.

14

Make a copy of the /usr/local/sjsas82/domains/domain/config/server.policy file as follows:

cp /usr/local/sjsas82/domains/domain/config/server.policy /usr/local/sjsas82/domains/domain/config/server.policy.orignal

Bear in mind that this is one, unbroken line, with spaces between the two file names.

Windows users can use Explorer to create a copy of the file.

15

Append the contents of the /usr/local/etc/symkey/server/server.policy file to the end of the server.policy file in the /usr/local/sjsas82/domains/domain/config directory,

cat /usr/local/etc/symkey/server/server.policy >> /usr/local/sjsas82/domains/domain/config/server.policy

Notice the two >> symbols in the cat command. A single (>) will replace the original contents, but two (>>) will append the new contents to the original.

Windows users may use WordPad to perform this operation. Make sure that the file is stored as text and not in Rich Text Format.

The following contents should be at the end of /usr/local/sjsas82/domains/domain/config/server.policy

// These permissions apply StrongAuth's StrongKey product

grant {

permission java.security.SecurityPermission "authProvider.SunPKCS11-NSS", "getSignerPrivateKey";

permission java.util.logging.LoggingPermission "control", "";

};

16

Restart the Application Server using:

asadmin stop-domain

and then following it with

asadmin start-domain domain1

17

On Linux, navigate to the /usr/local/sjsas82/domains/domain1/logs directory and type in the following in a shell window, to see the last few lines of the Application Server log. Keep this window open so the running log is visible to you through the remainder of steps of the installation/testing process:

tail -f server.log

If you see a message stating “All ejb(s) of [symkey] loaded successfully!|#]”, everything is OK.

18

You have successfully deployed the StrongKey EAR.