Creating a Widgetized Portal Site in IIS (Cobalt Staff)

If an association wishes to embed Cobalt widgetized Web Elements, they will need a widgetized portal.

The widget site must exist in IIS so that all of the relevant folders used by Web Elements can be contained and referenced in one place. The widget site is it's own standalone website, like our portal, and is linked to the data in CRM. This process leaves room for error so, if you're not familiar with doing this, speak to Frederick Zilmer, Brian Webb, Niusha Nawab, or a developer for assistance.

To create it, you'll need to take the following steps:

1) Access the server where the associations (Association A) portal folder resides. Navigate to the folder that contains that portal folder. For instance, in a RAMCO web mirror, this path would be D:\Cobalt

2) If this folder does not contain a sub-folder for Widget, create one. In RAMCO, there should always be a folder. Open that Widget folder

3) Find the folder for Association A. If there isn't one, create one. Open this folder

4) Find an example association (Association B) that has a known functioning widget site. Navigate to Association B's Widget folder. Copy every file. If you can't find an example of a functioning widget, refer to your tech lead or a support team member.

5) Navigate back to Association A's new Widget Folder and paste the copied files into that folder

6) Navigate to Association A's portal folder and copy the Cobalt.Components.Crm.BusinessObjects.dll config file from Association A's Portal bin subfolder to their Widget bin subfolder.

7) Open the IIS Manager and expand the server folder so that you see the Sites sub-folder.

8) Right click the Sites sub-folder and click Add Website


9) In the dialog box that opens, add the following values and click OK:

  -Site Name - The URL of the widget site ([association]widget.[domain] (i.e.

  -Physical Path - The directory path to the widget folder you've just created

  -Type - Https

  -IP Address - The IP of the current server (that should be the only option. If there are others, ask Frederick Zilmer)

  -Host Name - The same URL used as the Site name

  -SSL - If this option is present, it should be set to the same domain as the portal site.  


10) The site sub-folder should have refreshed to show you the site you've just created. If it doesn't try refreshing the page or navigating away and back. Right-click on the newly created site and click Bindings.

11) In the dialog box, you should see one entry for HTTPS. Click Add.

12) In the second dialog box, set the follwoing values and click OK:

  -Type - Http

  -IP Address - The IP of the current server (that should be the only option. If there are others, ask Frederick Zilmer)

  -Host Name - The same URL used as the Site name

13) Confirm that the Site Bindings dialog box shows a new entry for HTTP in addition to HTTPS.

You've now created a new widget site. You will need to generate a DNS entry for this site. Speak to Frederick Zilmer, Brian Webb, Mariah Fry or Niusha Nawab about adding an entry.

NOTE: If the association uses more than one server for their portal, you'll need to repeat these steps on each mirror

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk