Click Retrieve from port.  2. Specify the Box host name URL in the format  <<subdomain>>.app.box.com . For example, in the  3. Host field, enter  ecmsup.app.box.com , and in the Port field, enter  443 . If your Box environment  does not use a subdomain, just enter  app.box.com . Provide an alias name, for example,  ecmsup.app.box.com . 4. Click Retrieve signer information . This action must succeed. The web server must be able to connect  5. to  app.box.com  and  api.box.com . Save the certificate and save your changes.  6. Repeat the steps by using the additional host name  api.box.com  with an alias of  api.box.com . 7. Click Retrieve signer information . 8. Save the certificate and save your changes. 9. Log on to the WebSphere Integrated Solutions Console. 1. Select Servers > Server Types > WebSphere Application Server . 2. Click the appropriate server, for example, server1. 3. Under Server Infrastructure, click Java and select Process Management > Process Definition. 4. Under Additional Properties, click Java Virtual Machine. 5. Click the Configuration tab. 6. Under Additional Properties, click Custom properties. 7. Click New. 8. If you cannot configure access to external Box resources through HTTPS directly from WebSphere  Application Server due to firewall restrictions, consider configuring WebSphere Application Server to use  an existing internal internet proxy server, where available. To do so, complete the following steps:  Figure 2. Example of imported Box SSL signer certificate You must import the signer certificate from each of the two external Box resources (app.box.com and  api.box.com). When this task is successful, it also establishes that the IBM Content Navigator server can  access the external Box resources. The web server must be able to make SSL connections to these Box  external resources (app.box.com, api.box.com, and dl.boxcloud.com). Figure 2 shows the WebSphere console page for Signer Certificates. 4 How to Successfully Integrate IBM Content Navigator with Box