Re: Port selection
Venkateswara R Puvvada <[email protected]>
| Newsgroups | gmane.network.open-pegasus.general |
|---|---|
| Message-ID | <OF3B7005A4.7C280D47-ON65257930.001BB36C-65257930.001EEC10@in.ibm.com> |
Vitezslav, Some runtime config options are fixed and hidden in release builds. httpPort is part of those config options. http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/*checkout*/pegasus/doc/BuildAndReleaseOptions.html?rev=1.24.2.1 If there is a requirement to run multiple cimservers on a single system, use Pegasus PEGASUS_FLAVOR option which makes httpPort and httpsPort visible/ not fixed. http://www.openpegasus.org/pp/uploads/40/21277/PEP350_MultiCIMOM.htm PEP 290 was not implemented. There was a debate to use HTTP Host header to identify target host instead of using the port. Venkat From: Vitezslav Crhonek <[email protected]> To: "[email protected]" <[email protected]> Date: 20/10/2011 20:56 Subject: Port selection Hello, Is there any possibility to set own http/https port values? I see httpPort and httpsPort options, but it seems that these options are disabled: $ cimconfig -g httpPort Specified property name was not found. CIM_ERR_NOT_FOUND: Configuration property "httpPort" Is there any way how to enable them? (Probably some env. variable during build time?) I'm also curious what happened with PEP #290: http://www.openpegasus.org/pp/upreviews/40/2362/orig/PEP290.html Because this feature would be useful in some situations. Best regards, Vitezslav Crhonek