Install > Installing WebSphere Commerce > Installing WebSphere Commerce using the custom installation > Create a WCS instance > Mandatory post-instance creation tasks

Sun Java System Web Server tasks

WebSphere Commerce supports using Sun Java System Web Server 7.0 Update 4 as a Web server. While completing the following steps, refer to the sample Sun Java System Web Server 7.0 Update 4 configuration files located in the WC_INSTALL/config/deployment/webserverconfig/Sun directory.

Procedure

1. Log in to the WebSphere Application Server Administration Console.

2. Select Servers then Web servers.

3. Select webserver1.

4. Review the settings recorded in the Administration Console, and correct them based on the configuration. Apply the changes. You can safely ignore the entry in the Web server type field if it is incorrect.

5. Select Servers then Web servers.

6. Select webserver1 then Additional Properties.

7. Review the settings recorded in the Administration Console, and correct them based on the configuration. Apply the changes.

8. Regenerate the Web server plug-in.

9. Configure a Sun Java System Web Server 7.0 Update 4 trust database using the instructions provided by Sun.

10. Install a secure certificate signed by a certifying authority, according to the Sun Java System Web Server 7.0 Update 4 documentation.

    Your Web server provides a secure environment for your business transactions by using encryption technology. Encryption is the scrambling of information transactions on the Internet so that they cannot be read until they are unscrambled by the receiver. The sender uses an algorithmic pattern or key to scramble (encrypt) a transaction, and the receiver uses a decryption key. These keys are used by the SSL protocol.

    Your Web server uses an authentication process to verify the identity of the person with whom you are conducting business (that is, to make sure they are whom they say they are). This involves obtaining a certificate signed by a trusted third party called a certification authority (CA), such as Equifax or VeriSign Inc. Other CAs are available as well. To create a production key file...

    1. Request a secure certificate from a certifying authority.

    2. Set the production key file as the current key file.

    3. Receive the certificate and test the production key file.

    1. If you are already using a production key file signed by a certifying authority, you may be able to skip these steps.

    2. As you perform these steps, the browser may display security messages. Review the information in each message carefully and decide how to proceed.

11. Enable SSL using the instructions provided by Sun.

12. Ensure that you create the following virtual servers following the instructions in the Sun Java System Web Server 7.0 Update 4 documentation:

    • non-SSL communication on port 80

    • SSL communication on port 443

    • SSL communication on port 8000

    • SSL communication on port 8002

    • SSL communication on port 8004

    • SSL communication on port 8006

    • non-SSL communication on port 8007

    The port numbers must be the same as those entered during the WCS instance creation.

13. Test the installation and configuration of Sun Java System Web Server 7.0 Update 4 by opening a Web browser and going to the following URLs:

    http://SunWebServer_hostname
    http://SunWebServer_hostname:8007
    https://SunWebServer_hostname
    https://SunWebServer_hostname:8000
    https://SunWebServer_hostname:8002
    https://SunWebServer_hostname:8004
    https://SunWebServer_hostname:8006

    ...where SunWebServer_hostname is the fully qualified host name of the Sun Java System Web Server 7.0 Update 4 machine.

14. File magnus.conf is for a particular instance and must point to the instance's plugin-cfg.xml file Modify the magnus.conf file for https-host_name...

    1. If we will use Sun Java System Web Server 7.0 Update 4 as a local Web server, add the following directives to the end of the magnus.conf file for https-host_name:

       If these entries already exist in the magnus.conf file ensure that they conform to the following format.

       Init fn="load-modules" 
            funcs="as_init,as_handler,as_term" 
            shlib="WAS_Plug-indir/bin/libns41_http.so"
       Init fn="as_init" 
        bootstrap.properties=" 
            WC_PROFILE/config/cells/WC_profile_name_cell/
            nodes/webserver1_node/servers/webserver1/plugin-cfg.xml"
       

15. Review the Configure the Sun Java System Web Server to ensure that the Web server settings are correct.

16. Add the WebSphere Commerce Web aliases into each port's configuration file. Refer to the sample Sun Java System Web Server 7.0 Update 4 configuration files located in the WC_INSTALL/config/deployment/webserverconfig/Sun directory to get the list of the Web aliases and their paths.

17. By default, outside users can access any file that can be served up by Sun Java System Web Server 7.0 Update 4. For security reasons, you should restrict access to Web directories. See Sun Java System Web Server 7.0 Update 4documentation for information on restricting file and directory access. You should also refer to the sample configuration files located in the WC_INSTALL/config/deployment/webserverconfig/Sun directory to review the security settings.

18. If the Sun Java System Web Server 7.0 Update 4 is on a separate machine, refer to Remote Web server post-instance creation tasks.

19. Restart the Sun Java System Web Server.

    If you plan to use WebSphere Commerce Payments, configure an additional server within the Sun Java System Web Server 7.0 Update 4. The plugin-cfg.xml entries for both WebSphere Commerce Payments and WebSphere Commerce cannot be added to the same magnus.conf file, as these plugin-cfg.xml files do not reside in the same directory. You must create another magnus.conf file that is specific to WebSphere Commerce Payments. To create new magnus.conf file, add another server according to the Sun Java System Web Server 7.0 Update 4 documentation.

    By default, outside users can access any file that can be served up by Sun Java System Web Server 7.0 Update 4. For security reasons, you should restrict access to Web directories. See Sun Java System Web Server 7.0 Update 4 documentation for information about restricting file and directory access. In addition, you should open the obj.conf files and search for the NameTrans entries; ensure that the files in the targeted directories are protected.

+

Search Tips   |   Advanced Search