defining endpoint for services in 2025 software

[[ca...]]

Hello everyone,

I am trying to create a service for some basic inspection tasks. In the documentation, it says that there should be  some endpoint where the service functions will  be accessible.

When I use the gom.api.math or gom.api.test which are currently in documentation, it says that there isn't any module named of gom.api.math or gom.api.test.

How can I solve this problem?

Thanks,

Canset

[[Ma...]]

Hi Canset,

Please be aware that the services require ZEISS INSPECT 2025 or later.

Did you try the example from zeiss-inspect-app-examples/AppExamples/misc/ServiceExample at main · ZEISS/zeiss-inspect-app-examples?

A service consists of multiple parts:

• The service definitions in metainfo.json
• The service scripts
• The script calling a service function

The service has to be started via Apps-> Manage Services...

Best regards,

Matthias

 

[[ca...]]

Hello Matthias,

Yes, I am fully aware of that and checked the documentations that you shared before.

When I changed the endpoint to gom.api.meshing, the problem is solved.

Maybe I don't have gom.api.test or gom.api.math module or the problem could be related with licence.

My question is  what changes when I changed to module to gom.api.meshing and what is the point of using endpoints from different modules?

Thanks,

Canset

Edited April 9

[[Ma...]]

Hi Canset,

You can name the endpoints as you like. Their purpose is to provide a structure for naming and grouping services.

As far as I know, there is no relation between the endpoints and Python package or gom API names, except that you have to ensure that there are no clashes within the Python namespace (maybe the names used in the example are that good in this regard).

Aside from this, you just have to make sure that the endpoint names are used consistently between the service definition and the script calling the API.

Best regards,

Matthias

 

[[ca...]]

Hello Matthias,

Thanks for your help. I solved the problem with using a different name for the endpoint. I guess there is a clash just like you mentioned before.

Thanks,

Canset