Delete ALL text from this file that appears before -----BEGIN CERTIFICATE. Your document should contain only certificate information within this email. After you delete extra text, save this file inside your temporary directory as TEXT and filename "mycert.der".
To configure OAS 4.0.8 listener with your SSL files, go to OAS 4.0.8 Node Manager page (Usually on port 8888). Click on "OAS Manager".
Wait for the Java Applet menu to load and expand -> Website40 Site -> HTTP listener - WWW -> Security -> SSL.
Type in first ROW of data
1. a. Cert Label – mycert
2. b. Cert File - Enter path and name of your certificate received. For example: C:\SSL\mycert.cer
3. c. Dist Name File - Enter path and name for servname.der. For example: C:\SSL\servname.der
4. d. Private Key File - Enter path and name for privkey.der. For example: C:\SSL\privkey.der
5. e. CA [1] Dir - Enter a temporary path. This is not used, but you must supply a valid path. For example: C:\tmp.
6. f. CRL Dir - Enter a temporary path. This is not used but you must supply a valid path. For example: C:\tmp.
7. Click "Apply" to save changes.
To configure the Network section for WWW listener, go to HTTP listener -> WWW -> Network. Add a new ROW of information:
1. a. Address - Use same information as DEFAULT ROW. For example: ANY.
2. b. Port - Type port 443 here. SSL port 443 by DEFAULT.
3. c. Security - Pick SSL from pull-down menu.
4. d. Host Name - Use same information as DEFAULT ROW.
5. e. Base Directory - Use same information as DEFAULT ROW.
6. f. Log Info Directory - Use same information as DEFAULT ROW.
7. g. Authentication - Use same information as DEFAULT ROW. (NONE)
8. h. Certificate Label - Type "mycert". This is the same name used on Step #17 above. This entry maps Step #17 with Step# 18.
9. Click "Apply" to save changes.
Now, you are ready to recycle OAS for changed to take place. Go to Website40 Site or First Icon on Your Java Applet menu. Click on "Select All" radio button. Click on the (Reload) button in toolbar. This will properly shut down and restart all OAS processes in the right order.
If everything starts successfully, then try to access your secure page. SSL runs on HTTPS protocol, URL format may look like:
https://myhost.yoursitename.com[2]
Try to access that page in your browser. You should get a browser warning stating that you are entering a SECURE site. Just click OK. Secure page should come up.
If you get errors while trying to start WWW listener after making these changes, then check your NT Event Log or svwww.err file. Both logs will point out what is going wrong. Some common mistakes for SSL configuration include incorrect filename spellings and directory structures, problems with certificate file because of copy/pasting, etc. Log files tend to give very specific information in that case for debugging.