Skip to main content
P
PG_107588144-Participant
4-Participant
April 1, 2025
Solved

Load KepServerEx project to remote server using Configuration API

  • April 1, 2025
  • 1 reply
  • 672 views

Hello,

 

I'm calling, from my computer, the Configuration API of a remote KEPServerEx instance (version 6.16, running in a host).

My .opf file is stored in the local computer.

 

I wonder if there is a way to use load this file in the KEPServer instance.

I feel like the file needs to be stored locally on the server when using the /config/v1/project/services/ProjectLoad endpoint.

 

Thank you

Best answer by AKshara

You're correct that the .opf file needs to be stored locally on the server when using the /config/v1/project/services/ProjectLoad endpoint. To load your .opf file into the remote KEPServerEx instance, follow these steps:

  1. Transfer the .opf file to the server: Use a method like SCP (Secure Copy Protocol) or any other file transfer tool to move the .opf file from your local computer to the server where KEPServerEx is running.
  2. Verify the file location: Ensure the .opf file is placed in a directory that KEPServerEx can access. This directory should be recognized as valid by KEPServerEx1.  https://www.ptc.com/en/support/article/CS316445

  3. Use the Configuration API: Once the file is on the server, you can call the /config/v1/project/services/ProjectLoad endpoint with the appropriate parameters to load the project file. The endpoint will require the path to the .opf file on the server.

    Here's an example of how you might structure the API call:

    {
    "ProjectFilePath": "C:\\path\\to\\your\\project.opf"
    }
    Make sure to replace "C:\\path\\to\\your\\project.opf" with the actual path to your .opf file on the server.

     

    If you encounter any issues or need further assistance, feel free to ask!

1 reply

A
AKshara14-AlexandriteAnswer
14-Alexandrite
April 1, 2025

You're correct that the .opf file needs to be stored locally on the server when using the /config/v1/project/services/ProjectLoad endpoint. To load your .opf file into the remote KEPServerEx instance, follow these steps:

  1. Transfer the .opf file to the server: Use a method like SCP (Secure Copy Protocol) or any other file transfer tool to move the .opf file from your local computer to the server where KEPServerEx is running.
  2. Verify the file location: Ensure the .opf file is placed in a directory that KEPServerEx can access. This directory should be recognized as valid by KEPServerEx1.  https://www.ptc.com/en/support/article/CS316445

  3. Use the Configuration API: Once the file is on the server, you can call the /config/v1/project/services/ProjectLoad endpoint with the appropriate parameters to load the project file. The endpoint will require the path to the .opf file on the server.

    Here's an example of how you might structure the API call:

    {
    "ProjectFilePath": "C:\\path\\to\\your\\project.opf"
    }
    Make sure to replace "C:\\path\\to\\your\\project.opf" with the actual path to your .opf file on the server.

     

    If you encounter any issues or need further assistance, feel free to ask!

Terms & ConditionsCookie settingsAccessibility statement