I'm trying to develop a Orion admin mashup on fiware lab (noida) node for my local Orion instance.I have download a Orion admin mashup from this link: [https://store.lab.fiware.org/#/offering/540] and after that upload it on my wirecloud instance and then enter my Orion(NGSI server URL,NGSI tenant/service & NGSI scope)and my NGSI Type browser,NGSI browser are working fine but my NGSI Subscription browser widget not working giving the below error:
Exception details TypeError:
this.ngsi_connection.getAvailableSubscriptions is not a function.
I also attached a screenshot of my mashup you can see in this
link:https://imgur.com/a/ApN1NnC.
But when i upload the same mashup(orion admin) on Wirecloud Global instance with same local orion then it working perfectly fine and NGSI Subscription browser also working fine as you can see in the screenshot in this link:https://imgur.com/a/IqPa2Y5. But same mashup with same configuration not working on my fiware lab Node.Can anybody help me how to resolve it?
Wiring Screenshot :https://imgur.com/a/Qs3xxq7
Error Screenshot: https://imgur.com/a/mNoDXAV
thanks in advance.
Sorry the FIWARE's Lab Store portal (i.e. https://store.lab.fiware.org) is outdated. You can find an updated version of the Orion Admin Mashup (now renamed to Context Broker Admin Mashup) in this repository:
https://github.com/wirecloud-fiware/context-broker-admin-mashup/releases
Related
I am trying to publish the Azure APIM developer portal - it is enabled for user/pass - authentication. We haven't customized it and are just trying to get it to work.
When I click publish and go to view the portal in a different browser I get the following message
"This is a home page of the Developer portal - an automatically generated, fully customizable website for publishing your API documentation where consumers can discover APIs, learn how to use them, request access, and try them out.
The content hasn't been published yet. You can do so in "Developer portal" section of your API Management Service in the Azure portal. Learn more."
When I go back to the Portal publish page, it resets to show "Publish" as if nothing has happened?
Are there any logs or anything I can test to get this to work?
BTW - the Legacy portal works 100%.
Thank you.
I have Created the APIM instance and added the HTTP Trigger API from Function App and published the developer portal by enabling the CORS option also.
Next, I have created the user and given all APIs Level access in the APIM Instance and opened both deprecated and legacy portal in different browser, logged in with the non-administrative user:
You can see logs of all activities in the Activity log of APIM Instance:
To see the Function App API imported in the APIM Instance, you have to add that API to the products subscribed by that user:
Published the developer portal again with new changes:
Activity Logs:
Result:
You can check each log activity from the Activity log to see complete details whether the operation publish or other is succeeded and how much time it took to complete.
I want to ask about the Deployment of Forge API by Azure.
I had done it through the resource from Learn Forge, and it seems to work smoothly on the local site, but when I try to publish it, Although it shows permission
after I sign in, it shows 400 error refused, how can I do this for this error?
This is typically caused by an incorrect callback URL for the 3-legged authentication workflow.
When you develop your application locally, you typically set the callback URL (both in your application's code and in https://forge.autodesk.com/myapps) to something like http://localhost:3000/api/forge/callback/oauth).
However, when you deploy your application to Azure, AWS, Heroku, or any other cloud hosting provider, the callback URL must be updated accordingly. For example, if you deploy your application as an Azure Web App, the callback URL could look something like https://my-cool-app.azurewebsites.net/api/forge/callback/oauth. And again, you'll have to change the URL both in https://forge.autodesk.com/myapps, and in your Azure Web App settings.
We did a new release of the development portal in the Azure API Management and it showed the following message:
Creating a new revision or changing revisions will automatically update the portal to the latest version of the software. Content saved in the administrative version of the portal will not be changed.
Which caused that in my portal it now shows me in the box in the transaction detail section all the information to request the authorization token with oauth 2.0
How can I hide the authorization element so that it does not show in my portal for security reasons?
The new Authorization section in the API reference pages surfaces only public information required for clients to authenticate against your API. It doesn't show the secret configuration of your OAuth server. This information has always been publicly accessible, now we just visually render it. If, for some reason, you need to hide the public OAuth server details, you can remove the authorization server configuration from your API Management service. Keep in mind that it will also affect the test console.
If you still consider it a problem, please open a GitHub issue in the developer portal repository: https://aka.ms/apimdevportal and precisely describe your concern.
We have an Azure API Management Service that uses a custom domain. We have it added to the custom domain section of the service, and have a certificate uploaded too.
The certificate has recently expired so we went to the blade and updated the certificate. However, when we hit the API the browser is still serving the old certificate, so we are getting an invalid cert error.
Does anyone have any idea why it might be holding onto the old cert?
After long support calls the issue turned out to be a fatal flaw with that version of the APIM. We had no option but to recreate the APIM and redeploy our APIMs. Microsoft assured us that new instances of the APIM wouldn't have the same problem.
The JBoss AS Admin Console has a "configuration" tab for ESBs deployed on the server.
http://docs.jboss.org/jbossas/6/Admin_Console_Guide/en-US/html/Administration_Console_User_Guide-Updating_Resource_Configurations.html
It says that this is available for "resources that support configuration", but it is greyed out for an ESB service that I have written.
How can I make my service support configuration?
Without code changes to the ESB RHQ plugin, that's not really possible. The jbossesb RHQ plugin controls what's displayed there and there's nothing in your service configuration to allow run-time configuration through the admin-console.
If you're interested in changing that, you'd have to change the following files :
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/tools/jonplugin/src/main/java/org/jbosson/plugins/jbossesb/ServiceComponent.java
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/tools/jonplugin/as5/src/main/resources/META-INF/rhq-plugin.xml
Or submit a JIRA with a request of what service properties that you'd like to see configurable at runtime under JBoss ESB in the JBoss JIRA issue tracker :
https://issues.jboss.org/