In this tutorial, you will deploy your project to your shared environment.
In a production setting, you would create two shared environments, one for testing one for production. The one for production you would change the settings so any projects deployed to it are exposed in the production Joule.
Step 1Release project
โ
Open your project, and make sure it is saved.
Click Release in the upper right.
Release
Since this is your first release, the dialog will show the version as 1.0.0. You can add a release note if you want.
Click Release.
Click Release
After the project is released, you will see a success message at the top of the screen.
New release
Step 2Deploy project
+
Navigate to the released version by clicking Show project version.
New release
You will now see a button to deploy the project.
Deploy button
Click Deploy.
In the Choose an Environment dialog, select your shared environment you created at the start of the CodeJam.
Click Deploy.
Deploy
Select the environment variables, the same as when you did tested, just you do not have to select a private environment.
Field
Value
GetFromGTT
Select gttGetService destination
PostToGTT
Select gttwriteservice destination
Click Deploy.
Deploy variables
When complete, you will see a success message at the bottom and new deployment at the top.
Deploy finished
Step 3Test in shared environment
+
In the SAP Build Lobby, go to Control Tower > Environments.
Shared environment
Open your shared environment by clicking it (not the private environment).
Shared environment
In the Projects tab, which should be selected automatically, you will see the projects deployed to this environment.
You should see the project you just deployed.
Projects
Since this is a Joule-related project, open the Joule tab.
The Joule tab may be hidden under the More button.
More
Here you will see all the Joule Studio projects deployed to this environment.
Joule tab
Click Launch.
This launches in a new browser tab Joule for this environment, meaning you can prompt for all the projects in this environment.
Joule instance
Go ahead and test again the prompts for the your logistics agent.
Step 4Explore how to send to production
+
We will not deploy to the shared Joule for this project, but still you should know how that would be done.
Inside your environment, there is a setting to tell Joule Studio to send your skills and agents to Joule. If you enable the switch, all projects in the environment are made available in production to people with permission to this environment.
Production
In a production setting, you would create:
A test shared environment, whose projects would not be sent to Joule (toggle off).
A production shared environment, whose projects would be sent to Joule (toggle on).
IMPORTANT: Please do not turn this setting on.
Red button
Step 5Questions to ponder
+
What do environments allow you to do?
What are the authorizations available in an environment? See Share an Environment.
Share feedback on this tutorial or join the conversation in SAP Community.
Submit detailed feedbackDiscuss in Community
Steps
Step 1 of 5
1. Release project2. Deploy project3. Test in shared environment4. Explore how to send to production5. Questions to ponder
Joule
AI Notice
Joule is an AI assistant. Generative AI may produce inaccurate, incomplete, or biased information. Always verify important details before acting on them.
Conversations are sent to SAP-hosted large language models for processing. Do not include personal data, credentials, or confidential information in your messages.
Joule's responses are based on the SAP tutorial catalog and may not reflect the latest product changes. For authoritative guidance, consult the linked tutorials and official SAP documentation.