Update config.js #678

[MayankSingh-NEC]

Need to add some config for Scorpio Broker.
Also I've proposed some changes in node-lib repo for iotagent-json integration with Scorpio broker issue 1325.

[mapedraza]

The agents are Context Broker agnostics. No information given about the broker used, and adding information of multiples brokers (Orion, Orion-LD, Stelio or Scorpio) would add lot of noise to the agent config file. This specific port depends on each deployment, at leat in the Orion case, since you can deploy the broker in different ports, so we don't see adding this information is relevant for the user.

Additionally:

• This issue is not related with issuing commands from the scorpio context broker is not working #678 as you mention in the issue title
• Fix for issue 1325 iotagent-node-lib#1326 is not related with those changes you propose in this PR

For all those reasons this PR should be closed

[MayankSingh-NEC]

Hi @mapedraza , could we create separate documents

The agents are Context Broker agnostics. No information given about the broker used, and adding information of multiples brokers (Orion, Orion-LD, Stelio or Scorpio) would add lot of noise to the agent config file. This specific port depends on each deployment, at leat in the Orion case, since you can deploy the broker in different ports, so we don't see adding this information is relevant for the user.

Additionally:

• This issue is not related with issuing commands from the scorpio context broker is not working #678 as you mention in the issue title
• Fix for issue 1325 iotagent-node-lib#1326 is not related with those changes you propose in this PR

For all those reasons this PR should be closed

Hi @mapedraza , just to acknowledge for the new user. Could we create a separate documents for the iotagents integration
with Scorpio CB and propose relevant changes in their config.

& I've raised this issue #1325, to give fix for iotagent integration with Scorpio boker using postgress db, Now it's working fine, but the fix I've proposed for,

Before fix:

1. It always creates database with the lower case.
2. Giving "fiware-service" -> "Robots" will create db with "Robots" but also it'll create separate db as "robots".
3. This was conflicting earlier with the Scorpio CB. Gives as a result "Resource Not Found".
4. Scorpio CB is case sensitive,

After fix:

1. It will create with the same db whatever given in the "fiware-service".
2. This will create only one db.
3. No separate db are created.
4. It is working fine with Scorpio CB and also for Iotagents (not case sensitives).

[fgalan]

As explained at at https://thinking-cities.readthedocs.io/en/latest/multitenancy.html (*), regarding the service:

If uppercase characters are used, they are converted to lowercase.

What does the functionality you are changing in PR telefonicaid/iotagent-node-lib#1326 is exactly that, to convert the fiware-service to lowercase.

As I commented in another issue what NGSI-LD specification says about case sensitiveness in service ?