-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pass objects from service now to Archi #3
Comments
Hi, I provided the configuration file "sample_snow-import_plugin_ini_file.ini" that is self documented. Did you have a chance to have a look at it ? Best regards |
Thanks for your reply Herve 91 - this is what I am using in the ini file ... I am able to connect to service now however I am not seeing anything in Archi ... +++++++Ini I am using +++++++++++++++++++++ Generic Archi elements properties ApplicationComponentsarchi.elements.cmdb_ci_appl.archi_class = "ApplicationComponent" +++++++archimate-import-servicenow +++++++++++++++++++++ |
In fact, the configuration file is a way to construct the web service URL and for each response, create (or update) an Archi element. So what you can do to debug, is to manually connect to the web service URL generated by the proxy, and check what ServiceNow returns. If it returns zero line, then the UrL is not correct and the configuration file must be updated to change the URL. You may also get an error message that my plugin may fail to catch ... Please let me know ... |
Thanks Herve - I checked and I am getting the response from the URL is I manually connect through the browser. My service now link does not need proxy authentications, so I left PROXY section of ini file commented , would that cause an issue ? |
No issue. The proxy information needs to be filled in if you've got a proxy only :-) |
Hi Herve91,
Is there a step by step document on this which can Guide us how to pass the objects from Service Now to Archi.
I saw "Read Me" document but that does-not instruct how to map.
Any help here is much appreciated
The text was updated successfully, but these errors were encountered: