Re: Port selection

No, the established convention is that each company is supposed to subclass with their name in it.
It is wrong to have multiple servers running or allow a provider class conflict.

If one arranges a private special port, it no longer is "Common" in CIM, and then you might as well just open a socket and communicate directly.

 
Kirk Augustin
11821 NW McNamee Rd
Portland, OR 97231


HM: 503-289-4356
WK: 503-744-8841


>________________________________
>From: "Hwang, Johnny" <[email protected]>
>To: Kirk Augustin <[email protected]>; Vitezslav Crhonek <[email protected]>; [email protected]
>Sent: Thursday, October 20, 2011 9:33 AM
>Subject: RE: Port selection
>
>
>Re Kirk: No, sometimes you need to change the ports if you’re running several different cimservers when running several providers from different companies on the same computer. The way you change it is by cimconfig –p –s httpPort=1234
> 
>But back to your question. I don’t see any specific env vars needed to be set regarding httpPort and httpsPort. These are what we have:
>PEGASUS_ROOT
>PEGASUS_HOME
>PEGASUS_PLATFORM
>PEGASUS_REPOSITORY_MODE
>PEGASUS_CIM_SCHEMA
>OPENSSL_HOME
>PEGASUS_HAS_SSL
>PEGASUS_ENABLE_SLP
>PEGASUS_EXTERNAL_SLP_HOME
>PEGASUS_OPENSLP_HOME
>PEGASUS_USE_EXTERNAL_SLP
>CMPI_PLATFORM (on Linux)
>PEGASUS_ENABLE_CMPI_PROVIDER_MANAGER (on Windows)
> 
>Also check the following cimconfig variables: enableHttpConnection and/or enableHttpsConnection should be set to true. 
> 
>Speaking of environment variables, are there any centralized documentation for which compile env vars are available for which Pegasus version? PEP 237 is horribly outdated. 
> 
>From:Kirk Augustin [mailto:[email protected]] 
>Sent: Thursday, October 20, 2011 9:09 AM
>To: Vitezslav Crhonek; [email protected]
>Subject: Re: Port selection
> 
>Probably not a good idea.
>First of all, ports are reserved and handed out by standards committee, and you should not be using ports arbitrarily.
>Second is that all clients and servers possibly connecting have to agree.
>It is not one build, but all the builds of all the systems that might be involved.
>The whole point is to have a well established common port.
>It is not normally desirable to have any port variation.
>Nor can I imagine any advantage to it, other than if there is a protocol variation, such as SSL.
>So first tell us why you think you would want to use a different port?
> 
>Kirk Augustin
>11821 NW McNamee Rd
>Portland, OR 97231
>HM: 503-289-4356
>WK: 503-744-8841
>
>________________________________
>
>From:Vitezslav Crhonek <[email protected]>
>To: "[email protected]" <[email protected]>
>Sent: Thursday, October 20, 2011 7:44 AM
>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
>
>
>
>
>