On-premise Thingworx Server

[sean_textree]

We have a on-premise thingworx server. 

The Experience Service is installed and operated on the Thingworx Server.

I have three questions.

1. Can I lock permissions on published projects?

For example, user must authenticate when scanning a thingmark.

2. Where is the location of the thingmark image file on the local server?

3. Can I change the location of a project that is published to the Experience Service?

[dupatel · Accepted solution]

@sean_textree  Please review the details below -

1. Can I lock permissions on published projects? -- You can set project configuration -> Info-> Access --> Requires Authentication and then publish.

2. Where is the location of the thingmark image file on the local server?The ThingMark itself is not published with the project and only the vuforia target is published.

3. Can I change the location of a project that is published to the Experience Service? Configuration parameter- reps.store in ES configuration.json Default path on Linux: /srv/ptc/studio-es/reps Windows: C:\ptc\studio-es-store\reps 

-Durgesh