Hi Suba, 

The Database ID will be the 2 digit identifier that you set registering / creating a dataset in CM. 

The Web Client Workgroup Server URL will be the name or alias of the Workgroup Server that you would like to use to facilitate user connections to the CM Web Client. 

Hi Subha,

Yes - the dataset ID is obtained from Enterprise Studio and is typically the ID of the dataset that this particular instance of the Web Client should connect to

For my own install, the ID is 45

For Server URL, if this machine is also a workgroup server, you can put localhost

This option would allow your website to connect to that dataset via a DIFFERENT workgroup server if needed.

You can always change these details after install by going into the WebClient directory and modifying the hprmServiceAPI.config

-Scotty

Hi,

Thank you. I have the given the hostname of my Workgroup Server box as the Server URL. 

Since I am pretty new in the Content Manger Product Suite, I have another question (may be a naive one). 

As I can see, i will probably be able to access the Content Manager through the URL -  'localhost:80/ContentManager'. (I am getting some IIS role issue while accessing the above URL. But I think can be resolved by installing the required roles)

But if I am trying the url  'HOSTNAME_OF_WORKGROUPSERVER:80/ContentManager' I am getting a 404 error. Am I missing something here?

Thanks in advance. 

Plesae check hprmserviceapi.cfg to confirm WorkgroupServer name is correct. It should be the workgroupserver name. Please see below and replace XXXXXX with the workgroupserver name.

  <workgroupServer workPath="C:\Micro Focus Content Manager\ServiceAPIWorkpath" name="XXXXXX" alternateName="" />

Once you have checked the above, also have a look at your bindings in IIS

If you don't have HTTPS bindings then you will need to do

servername:port/ContentManager to access (no S)

E.g. If you have a binding listing on http port 80 can do

Also make sure your bindings aren't listening for a particular hostname, e.g. if your binding is set to be listing for hostname of 'company.abc.com' then you wont be able to access it via localhost in the browser 

In my own bindings, I can only access http via localhost, where https has no hostname set so will work for any incoming hostname.

-Scotty