2- Create Environments for Testing
- How to create a private environment
- How to create a shared environment
Prerequisites
- You have completed the previous tutorial in the Joule Studio CodeJam Mission, Open and Explore the SAP Build Lobby.
Joule studio has different types of environments to guide the development of your projects:
-
Private Environment: Each developer can set up a private environment, which is designed to provide a “sandbox” or safe, isolated space for experimenting with your Joule Studio projects. It is used to run the current project without being influenced by other deployed projects. The key advantages are:
-
Safely experiment with new agent logic, skills, and actions.
-
Test conversations during design time (before deployment).
-
Test projects without needing to create new releases or deployments.
-
-
Shared Environment: Allows different lines of business to deploy their projects to separate areas, each with specific permissions and different destinations and other settings.
-
Production Environment: Agents and skills in the production environment are run in the central Joule instance along with all other built-in or custom skills and agents.
So the flow of development would be something like this:
-
You create a private environment.
-
You create 2 shared environments for any line of business: one for testing, and one for production.
-
You set the environment designated for production to expose to production any Joule Studio artifacts deployed to that environment (there is a toggle in each environment to do this).
-
You develop a Joule Studio project and test it inside your private environment.
-
You deploy it to your test shared environment for the LOB and test it there.
-
When ready, you deploy it to the production environment, which will automatically expose it to the production Joule.





