Has anyone configures oslc server for Windchill RV&S (formerly Integrity Lifecycle Manager.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Has anyone configures oslc server for Windchill RV&S (formerly Integrity Lifecycle Manager.
My oslc server is giving response while scheme is https but not when scheme is http. Below is my production.json. For http the request does not even go to server, as i dont see any logs on oslc.log. The https works fine (Tested through postman).
{
"ilm": {
"scheme": "http",
"host": "localhost",
"port": "7001",
"baseContext": "/rws/odata/ptc/ilm",
"strictSSL": false,
"docStudioContext": "/extended-web-ui/items/item"
},
"oslc": {
"scheme": "https",
"host": "localhost",
"port": 3001,
"context": "/oslc/r",
"storageImpl": "ldp-service",
"services": "./config/defaultServices.json",
"contentType": "JSON",
"sslPrivateKey": "server.key",
"sslCertificate": "server.cert",
"useClientAuthForSSL": false,
"allowedOrigins":"http://localhost:8080,http://localhost:80,http://localhost:84"
}
}
My intent is that i want to consume these services in Thingworx. Any help would be appreciated.
- Labels:
-
Requirements & Validation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi,
Are you working on getting the Windchill PDMLink and Windchill RV&S (Integrity Lifecycle Manager) integration working?
Have you reached out to Technical Support?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
I have not reached out to tech support yet. I am trying to pull data from integrity by thingworx and same with PDM. For PDM it is quite easy given that you have lot of guides available but for integrity it is little tricky. When i make a rest request from thingworx with oslc url it gives me "Certificate for <localhost> doesn't match..." Link . The article mentions that this error has been fixed in latest version but i still see error. I don't want to create certificate. I think if http starts working than this issue will automatically be fixed.
