Fist off we’ll need to import the SSL certificate in order for IIS to be able to use it.
Installing the certificate is a one-time procedure if you are using a wildcard certificate as it is shown in the example below. If you plan on using individual certificates for each Fully Qualified Domain Name, this process will need to be repeated for each certificate.
Launch the MMC by clicking on the Start button then typing in mmc and hit Enter. In the window that pops up, click on File in the upper left hand corner, then select Add/Remove Snap-in.
In the Available snap-ins window pane on the left locate and select Certificates, then click on the Add button in the middle.
Select Computer account when prompted on the next screen.
As we are doing this from the server on which the portals will be running, we’ll select Local Computer on the next screen.
The Certificates snap in will now appear in the Selected snap-ins window pane on the right. Click the OK button.
Next, you’ll want to expand the Certificates section, as well as Personal, then right click on Certificates and select All Tasks and finally click on Import.
Navigate to the certificate file (usually a .pfx file) and if prompted, enter in the certificate password (defined at the time of the export).
You can accept the default values in the wizard, including importing extended properties. Lastly, allow the certificate to be imported into the currently selected (Personal) certificate store.
Click the Finish button to complete the process. You’ll see a window pop up saying that the import was successfully completed.
After importing, you should see something like this.
Note that the WMSvc-[Hostname] certificate will already be present in the certificate store. Do not delete or alter it as it is used for Windows Management security.
We are now ready to start deploying the Infor10 ERP Business Portal. Installation files for Infor SyteLine portals can be downloaded from www.inforxtreme.com. In our particular example we will be installing Infor10 ERP Business Portals 8.03 build 18.104.22.168. Run the executable as an administrator.
At the Select Features portion of the setup check the boxes next to Portal and/or Content as well as Portal Manager, then click Next.
On the Portal Content page, select Customer Portal, then click Next.
On the next screen titled Web Applications, select the radio button next to Create new Web Application, and press the Next button.
Next, supply the credentials for the application pool and Sharepoint to use for the application. In our example we’ve been using domain/slportaladmin.
In this example we will assume that you do not want to allow the Portal Admin pages to be accessible from external hosts, therefore we’ll use the canonical machine name for the admin site (PORTAL in this case). Since there may be many portals installed on a single machine, we will use a port other than 80 by choosing the Advanced button. In the example below, we’ll start with port 8010. Should you need to install additional portals just increment the port number as you see fit.
For the public facing web site you’ll want to provide a FQDN of your choosing and select to use SSL. No advanced options are required.
Commit your selections by clicking on the Install button.
Once the installation has been completed successfully and the portal has been deployed, we’ll need to bind the appropriate SSL certificate to this newly created site in IIS running on the PORTAL server.
Launch the Internet Information Services (IIS) Manager control panel MMC console. Expand the tree view on the left, until you see the Sites and find the new “Internet” site corresponding to the new portal.
Highlight the customer facing site (the one with the – Internet suffix). Click on Bindings in the Actions window pane on the right.
Highlight the existing binding on port 443 and click on Edit.
Use the SSL certificate dropdown to select the appropriate certificate. Make sure that the hostname reference is correct, then click the OK button.
At this point, the portal should be functional with SSL. Patches, updates or modifications could be applied to the portal, and should not impact the certificate binding.