diff --git a/codelabs/sap-aem-int-day-1/codelab.json b/codelabs/sap-aem-int-day-1/codelab.json
index f7c7e39a..e75d027c 100644
--- a/codelabs/sap-aem-int-day-1/codelab.json
+++ b/codelabs/sap-aem-int-day-1/codelab.json
@@ -3,7 +3,7 @@
"format": "html",
"prefix": "https://storage.googleapis.com",
"mainga": "UA-49880327-14",
- "updated": "2023-12-04T09:44:23Z",
+ "updated": "2024-02-27T12:54:40Z",
"id": "sap-aem-int-day-1",
"duration": 12,
"title": "Event Enable SAP Using SAP Advanced Event Mesh - Day 1",
diff --git a/codelabs/sap-aem-int-day-1/img/2b431a2038d0a342.png b/codelabs/sap-aem-int-day-1/img/2b431a2038d0a342.png
new file mode 100644
index 00000000..0c5c5952
Binary files /dev/null and b/codelabs/sap-aem-int-day-1/img/2b431a2038d0a342.png differ
diff --git a/codelabs/sap-aem-int-day-1/img/344390f02e5b2376.jpeg b/codelabs/sap-aem-int-day-1/img/344390f02e5b2376.jpeg
new file mode 100644
index 00000000..c16ad6a9
Binary files /dev/null and b/codelabs/sap-aem-int-day-1/img/344390f02e5b2376.jpeg differ
diff --git a/codelabs/sap-aem-int-day-1/img/5ca2c181ce044b1c.png b/codelabs/sap-aem-int-day-1/img/5ca2c181ce044b1c.png
new file mode 100644
index 00000000..1afc4475
Binary files /dev/null and b/codelabs/sap-aem-int-day-1/img/5ca2c181ce044b1c.png differ
diff --git a/codelabs/sap-aem-int-day-1/img/99322bc67aab4309.png b/codelabs/sap-aem-int-day-1/img/99322bc67aab4309.png
new file mode 100644
index 00000000..5bcbfd2c
Binary files /dev/null and b/codelabs/sap-aem-int-day-1/img/99322bc67aab4309.png differ
diff --git a/codelabs/sap-aem-int-day-1/img/a6173ca5c54628ba.png b/codelabs/sap-aem-int-day-1/img/a6173ca5c54628ba.png
new file mode 100644
index 00000000..09bd5fc2
Binary files /dev/null and b/codelabs/sap-aem-int-day-1/img/a6173ca5c54628ba.png differ
diff --git a/codelabs/sap-aem-int-day-1/img/d2944db9d11e1ea9.png b/codelabs/sap-aem-int-day-1/img/d2944db9d11e1ea9.png
new file mode 100644
index 00000000..6db3613d
Binary files /dev/null and b/codelabs/sap-aem-int-day-1/img/d2944db9d11e1ea9.png differ
diff --git a/codelabs/sap-aem-int-day-1/index.html b/codelabs/sap-aem-int-day-1/index.html
index 0dc1cb19..e840ade4 100644
--- a/codelabs/sap-aem-int-day-1/index.html
+++ b/codelabs/sap-aem-int-day-1/index.html
@@ -143,26 +143,31 @@ Create your first AEM service:
The SAP Cloud Application Programming Model (CAP) is a framework of languages, libraries, and tools for building enterprise-grade services and applications. It guides developers along a ‘golden path' of proven best practices and a great wealth of out-of-the-box solutions to recurring tasks. CAP-based projects benefit from a primary focus on domain. Instead of delving into overly technical disciplines, we focus on accelerated development and safeguarding investments in a world of rapidly changing cloud technologies.
For more information on SAP CAP, you can refer to the link : SAP Cloud Application Programming Model
To showcase the integration capability of SAP CAP and AEM, we have created a CAP based Java microservice which will publish different SAP business object events into your AEM instance. This application can be deployed in your SAP CloudFoundry space.
-1 : CloudFoundry CLI installation
-To start with, we will be installing the CloudFoundry CLI for the deployment process. Follow the steps mentioned over here Installing the cf CLI for detailed instructions on this.
-2 : Downloading the deployables artefacts
+1 : Downloading the deployable artefacts
Download the following files artefact files and save them in the same directory:
-3 : Login to CloudFoundry space
-You can log in to the SAP CloudFoundry space in your account as below :
+2 : Identify CF Domain address
+In order to deploy the simulator to your CloudFoundry space, you need to identify the domain address which is a part of the API endpoint.
-- Use the command :
cf login to log in, which will prompt for your SAP login credentials.
-- Once authenticated, the details of the default cloudfoundry space will be displayed.
+- Navigate to your SAP BTP Sub account Overview page
+- Copy the specified section of the API Endpoint in the Cloud Foundry Environment as shown below :
+
+3 : Update the manifest file
+
+- Open the manifest.yml file which you downloaded earlier in a text editor
+- Replace the placeholder text {API_ENDPOINT} on line number 12 with the value copied from the API Endpoint
+- After replacing your manifest file should look like this :
+- Save and close the file.
4 : Deploying the SAP Simulator application
-- Navigate to the directory where the above deployable artefact files are saved.
-- Run the command
cf push --random-route which will upload the jar file and use the manifest.yml for properties. Note : this command will take some time to completely execute as it uploads the jar deployable and also start the application.
-- Once the command is completely executed, run the command
cf apps to view a listing of the apps in your cloudfoundry space
-- Verify that the app capm-erp-simulation is deployed and started
+- Navigate to the CloudFoundry space where you want to deploy the application and click on the Deploy Application button as below :
+- A Deploy Application modal window will be displayed where you can browse and select the capm-erp-simulation-exec.jar and manifest.yml as below
+- Click on the deploy button Note : this action will take some time to completely execute as it uploads the jar deployable and also start the application.
+- Once the upload is completely executed, you should be able to see the application deployed and running as below :
diff --git a/markdown/sap-aem-int-day-1/img/SAP-CF-space.png b/markdown/sap-aem-int-day-1/img/SAP-CF-space.png
new file mode 100644
index 00000000..09bd5fc2
Binary files /dev/null and b/markdown/sap-aem-int-day-1/img/SAP-CF-space.png differ
diff --git a/markdown/sap-aem-int-day-1/img/cf-app-deployed.png b/markdown/sap-aem-int-day-1/img/cf-app-deployed.png
new file mode 100644
index 00000000..1afc4475
Binary files /dev/null and b/markdown/sap-aem-int-day-1/img/cf-app-deployed.png differ
diff --git a/markdown/sap-aem-int-day-1/img/cf-deploy-app.png b/markdown/sap-aem-int-day-1/img/cf-deploy-app.png
new file mode 100644
index 00000000..6db3613d
Binary files /dev/null and b/markdown/sap-aem-int-day-1/img/cf-deploy-app.png differ
diff --git a/markdown/sap-aem-int-day-1/img/cf-domain-address.jpeg b/markdown/sap-aem-int-day-1/img/cf-domain-address.jpeg
new file mode 100644
index 00000000..c16ad6a9
Binary files /dev/null and b/markdown/sap-aem-int-day-1/img/cf-domain-address.jpeg differ
diff --git a/markdown/sap-aem-int-day-1/img/original-manifest.png b/markdown/sap-aem-int-day-1/img/original-manifest.png
new file mode 100644
index 00000000..5bcbfd2c
Binary files /dev/null and b/markdown/sap-aem-int-day-1/img/original-manifest.png differ
diff --git a/markdown/sap-aem-int-day-1/img/updated-manifest.png b/markdown/sap-aem-int-day-1/img/updated-manifest.png
new file mode 100644
index 00000000..0c5c5952
Binary files /dev/null and b/markdown/sap-aem-int-day-1/img/updated-manifest.png differ
diff --git a/markdown/sap-aem-int-day-1/sap-aem-int-day-1.md b/markdown/sap-aem-int-day-1/sap-aem-int-day-1.md
index 5e97b8fb..a1a89603 100644
--- a/markdown/sap-aem-int-day-1/sap-aem-int-day-1.md
+++ b/markdown/sap-aem-int-day-1/sap-aem-int-day-1.md
@@ -203,35 +203,37 @@ To showcase the integration capability of SAP CAP and AEM, we have created a CAP
publish different SAP business object events into your AEM instance.
This application can be deployed in your SAP CloudFoundry space.
-### 1 : CloudFoundry CLI installation
-
-To start with, we will be installing the CloudFoundry CLI for the deployment process.
-Follow the steps mentioned over
-here [Installing the cf CLI](https://github.com/cloudfoundry/cli/wiki/V8-CLI-Installation-Guide) for detailed
-instructions on this.
-
-### 2 : Downloading the deployables artefacts
+### 1 : Downloading the deployable artefacts
Download the following files artefact files and save them in the same directory:
- capm-erp-simulation-exec.jar : [https://github.com/SolaceLabs/aem-sap-integration/blob/main/deployable/capm-erp-simulation-exec.jar](https://github.com/SolaceLabs/aem-sap-integration/blob/main/deployable/capm-erp-simulation-exec.jar)
- manifest.yml : [https://github.com/SolaceLabs/aem-sap-integration/blob/main/deployable/manifest.yml](https://github.com/SolaceLabs/aem-sap-integration/blob/main/deployable/manifest.yml)
-### 3 : Login to CloudFoundry space
+### 2 : Identify CF Domain address
-You can log in to the SAP CloudFoundry space in your account as below :
+In order to deploy the simulator to your CloudFoundry space, you need to identify the domain address which is a part of the API endpoint.
+- Navigate to your SAP BTP Sub account Overview page
+- Copy the specified section of the API Endpoint in the Cloud Foundry Environment as shown below :
+
-- Use the command : `cf login` to log in, which will prompt for your SAP login credentials.
-- Once authenticated, the details of the default cloudfoundry space will be displayed.
+### 3 : Update the manifest file
+- Open the manifest.yml file which you downloaded earlier in a text editor
+- Replace the placeholder text {API_ENDPOINT} on line number 12 with the value copied from the API Endpoint
+
+- After replacing your manifest file should look like this :
+ 
+- Save and close the file.
### 4 : Deploying the SAP Simulator application
-- Navigate to the directory where the above deployable artefact files are saved.
-- Run the command `cf push --random-route` which will upload the jar file and use the manifest.yml for properties. **Note : this
- command will take some time to completely execute as it uploads the jar deployable and also start the application.**
-- Once the command is completely executed, run the command `cf apps` to view a listing of the apps in your cloudfoundry
- space
-- Verify that the app **capm-erp-simulation** is deployed and started
+- Navigate to the CloudFoundry space where you want to deploy the application and click on the **Deploy Application** button as below :
+
+- A **Deploy Application** modal window will be displayed where you can browse and select the **capm-erp-simulation-exec.jar** and **manifest.yml** as below
+
+- Click on the deploy button **Note : this action will take some time to completely execute as it uploads the jar deployable and also start the application.**
+- Once the upload is completely executed, you should be able to see the application deployed and running as below :
+
## Test SAP Simulator