I'm trying to get UUID for the VMware VM using Python vCenter API.
I'm reading GET VM API doc here. which says It should be there in the response but when I run get API I don't get identity in the response. Anyone has any idea why it's not returning identity in the response payload?
"identity": {
"bios_uuid": "string",
"instance_uuid": "string",
"name": "string"
}
API I'm using https://{api_host}/rest/vcenter/vm/{vm}
The full name of that set of properties is "guest identity" which will also mean that VMware Tools are installed and running at the time of the call.
Related
I just installed WSO2 3.2.0 and Analytics 4.4.0 on the same machine using repositories on Debian 9.
Everything looks fine except the analytics Dashboard that I can't access for. According to the documentation here, I have to go on this url https://check.mydomain.com:9643/analytics-dashboard but all I got is this error :
Problem accessing: /analytics-dashboard. Reason: Not Found
I followed these steps to set up my domain name and enable analytics :
nano /usr/lib/wso2/wso2am/3.2.0/repository/conf/deployment.toml
[server]
hostname = "check.mydomain.com"
[apim.analytics]
enable = true
And I replaced every "localhost" string by ${server.hostname}
I followed these steps to start Analytics, API Manager and Dashboard :
service wso2sp-4.4.0-worker start
service wso2am-3.2.0 start
service wso2sp-4.4.0-dashboard start
Every service is fine regarding
service wso2sp-4.4.0-worker status
service wso2am-3.2.0 status
service wso2sp-4.4.0-dashboard status
Every other urls are working :
https://check.mydomain.com:9443/admin
https://check.mydomain.com:9443/carbon
https://check.mydomain.com:9443/devportal
https://check.mydomain.com:9443/publisher
Analytics is enabled and I can see subscription options on Publisher settings
Nothing happends on logs when I wisit https://check.mydomain.com:9643/analytics-dashboard
tail -f /usr/lib/wso2/wso2am/3.2.0/repository/logs/http_access_.2020-11-18.log
tail -f /usr/lib/wso2/wso2am/3.2.0/repository/logs/wso2carbon.log
tail -f /usr/lib/wso2/wso2sp/4.4.0/wso2/worker/logs/carbon.log
tail -f /usr/lib/wso2/wso2sp/4.4.0/wso2/dashboard/logs/carbon.log
Any help would be very appreciated, thanks.
You need to use wso2am analytics setup to configure analytics with the API manager. But I think now you are trying to use wso2 stream processor to configure the analytics and it's not supported with wso2am 3.2.
Follow the [1]documentation to download and set up the analytics.
You need to manually download the wso2am-analytics-3.2.0.zip.
if you follow the quick setup make sure wso2am-analytics-3.2.0 and wso2am folders locate in the same place. (since you installed apim via the apt installer you need to manually put anlytics setup in /usr/lib/wso2/wso2am/ folder and correctly set the path to API manager am_db in wso2am-analytics-3.2.0/conf/dashboard/deployment.yaml---> AM_DB -> jdbcUrl)
If you follow the standard setup no need to worry about the locations of wso2am pack and wso2am-analytics pack.
[1] https://apim.docs.wso2.com/en/latest/learn/analytics/configuring-apim-analytics/
How do I check which version of WSO2 API Manager I'm currently running in my RHEL 7 machine?
in the logs, you can check, when all the logs are loaded at the end it shows which version is of the API manager
\wso2am-3.0.0\bin>wso2server.bat --version
Result:
WSO2 API Manager v3.0.0
WSO2 Carbon Framework v4.5.1
The easiest way is to request it to the endpoint available for this porpouse and it is usually used for health checking:
curl -X GET https://localhost:9443/services/Version
Response:
<ns:getVersionResponse xmlns:ns="http://version.services.core.carbon.wso2.org">
<return>WSO2 API Manager-2.6.0</return>
</ns:getVersionResponse>
There is a version.txt file in the <AM_HOME>/bin directory. You can refer to this file as well.
I am using WSO2 API Manager (1.8) and WSO2 BAM server(2.5.0) . I have done the
following configurations for getting statistics.
Configurations in :
https://github.com/Prasanthmv/Wso2/blob/master/configurations/all.doc
After that I started BAM and AM, but the following error appears :(I have
pushed the error in github):
AM error
BAM error
Why this error is showing, is my configuration
correct?
Here's documentation on how to set up API Manager / BAM integration: https://docs.wso2.com/display/AM180/Publishing+API+Runtime+Statistics
Alternatively, you can use WSO2 API Cloud (SaaS version of API Manager) in which everything is preconfigured and works out of the box.
According to the carbon logs, You must be using windows 7.
Therefore,
This could be due the BAM cannot execute cygwin commands. Please try to install Cywin into C drive and make sure no space in file path and append "C:\cygwin64\bin" to the windows PATH (using "Edit the system environment variables").
When I try to config throttling with domain type in WSO2 ESB 4.0.3 for services ECHO.
I tried to send the soap message from client to server via command line:
curl --data-binary #soaptest.xml -H 'Content-Type: text/xml;charset=UTF-8' "http://dc2nix2d11:8282/services/echo"
But I still get the result although I set access deny for the domain of client machine.
I try to do the same config throttling with IP type and it's work.
Maybe Throttling does not work with domain type in WSO2 ESB 4.0.3 ?
Please help me to fix this issue.
This is an known issue. It's already fixed in next ESB release
If you are using service hosting feature on WSO2 ESB you could alternatively use recently released WSO2 AS 5.1.0 which support for domain based throttling to host your services till the next ESB version get released.
I am trying to do something rather simple. That is, using one of Siebel's prebuilt ASIs with a web service interface.
On the Siebel client, I navigated to "Inbound Web Services", and changed the status of one of the services to "Active".
I am using Siebel V 7.5.3
I import the WSDL file into SoapUI, and try to run the request, but still get the error:
There is no active Web Service with operation named
'http://siebel.com/asi/:SiebelQuoteQueryById'.(SBL-EAI-04313)
Am I missing something? Could this be a permissions problem?
Solved by restarting the server.
Navigate to "Server Administration" -> "Enterprise Operations". Use the bottom pane (the default displayed "Enterprise Servers" tab) to restart the server.