Updating from base fork

Integrations/301-IntegrationsLab.md

@@ -15,7 +15,22 @@ In this exercise, we will:
 
 #### Navigating Oracle Integration Cloud Service ####
 
-1. [Sign in](sign.in.to.oracle.cloud.md) to [https://cloud.oracle.com/sign-in](https://cloud.oracle.com/sign-in). First select your datacenter then provide the identity domain and credentials of **Integration Cloud Service \(ICS\)**. After a successful login you will see your Dashboard. Find the **integration** services tile and click the hamburger icon. In the dropdown menu click `Open Service Console`.
+1. On completion of previous Microservices lab, we can logout from Cloud Dashboard before proceed this lab exercise.  
+On the top right corner of dashboard, click on your username and then click `Sign Out`.
+
+![](images/301/00.logout.png)
+
+2. Click `Confirm` button to signout.
+
+![](images/301/00.logout.confirm.png)
+
+3. Sign in to Cloud again from [https://cloud.oracle.com/sign-in](https://cloud.oracle.com/sign-in), first select your datacenter then provide the identity domain and credential of **Integration Cloud Service \(ICS\)**.  
+
+**Alternatively  you can access thru the Access Document - Integrations Lab section provided by instructor.**  
+
+(**\*Notice**: The identity domain and credential of this Integrations Lab is **DIFFERENT** from those you were using in JavaApps Lab and Microservices Lab previously. Please check carefully with detail provided by instructor)  
+
+After a successful login you will see your Dashboard. Find the **integration** services tile and click the hamburger icon. In the dropdown menu click `Open Service Console`.
 
 ![](images/301/01.dashboard.png)
 
@@ -41,7 +56,7 @@ In this exercise, we will:
 
 The navigation pane provides you with access to all the development features in the Oracle Integration Cloud Service.
 
-[Procced to Next - 302: Define Connections for CRM Customer Activity Service and REST Service Exposure](302-IntegrationsLab.md)
+[Procced to Next - 302: Import and Define Connections for CRM Customer Activity Service and REST Service Exposure](302-IntegrationsLab.md)
 
 or
 

Integrations/302-IntegrationsLab.md

@@ -1,129 +1,135 @@
 # ORACLE Cloud Test Drive #
 -----
-## 302: Define Connections for CRM Customer Activity Service and REST Service Exposure ##
+## 302: Import and Define Connections for CRM Customer Activity Service and REST Service Exposure ##
 
 ### Introduction ###
 This tutorial demonstrates how to:
-- Define ICS connections for a REST trigger service exposure and invoke an external SOAP service
+- Import and define ICS connections for a REST trigger service exposure and invoke an external SOAP service
 
 ### About the Exercise Today ###
 In this exercise, we will:
-- Using the web-based click and configure techniques to define ICS connection resources: **SOAP** and **REST** respectively.
+- Using the web-based click and configure techniques to import and define ICS connection resources: **SOAP** and **REST** respectively.
 
 ### Prerequisites ###
 - Oracle Public Cloud Service account including Integration Cloud Service
+- An Integration Archive File (IAR) name as `XXX_ICS_INTMGT_01_lab.iar` distributed by instructor
 
-#### Define SOAP Connection for CRM Customer Activity Service ####
+#### Import Integration Cloud Service Project Artifact ####
 
-1. Go to **Connections** Summary Page by click on the `Connection` green icon.
+1. Go to **Integrations** Summary Page by click on the `Integrations` blue icon.
 
-![](images/302/01.home_conn.png)
+![](images/302/01.home_integrate.png)
 
-Alternatively, you can go to **Connections** Summary Page by click the hamburger icon at the top left corner, click `Designer` and then `Connections`
+Alternatively, you can go to **Integrations** Summary Page by click the hamburger icon at the top left corner, click `Designer` and then `Integrations`.
 
 ![](images/302/02.home_hamburger.png)
 
 ![](images/302/03.home_hamburger_designer.png)
 
+![](images/302/01.home_hamburger_integrate.png)
+
+2. Click `Import` on the top right corner, the **Import Integration?** dialog window appears. Click `Browse` button.
+
+![](images/302/02.integration_import.png)
+
+3. Browse and open your machine local directory to select the *IAR* file provided by instructor previously, then click `Import` button.
+
+![](images/302/02.integration_import1.png)
+
+4. You should find a green dialog text area about **Integration was imported successfully** and the newly imported entity named **XXX_ICS_INTMGT (1.0)** shown on the integration list.
+
+![](images/302/02.integration_import2.png)
+
+You have successfully imported a set of partial pre-built artifacts. We will walk-thru what has been built and complete the remaining part.  
+
+#### Define SOAP Connection for CRM Customer Activity Service ####
+
+5. Go to **Connections** Summary Page by click the hamburger icon at the top left corner, click `Designer` and then `Connections`.
+
 ![](images/302/04.home_hamburger_connections.png)
 
-2. In the home page of **Connections**, click `Create` button on the top left corner, the **Create Connection - Select Adapter** dialog window is shown.  
-   You could see different types of connection adapters are available, such as *Sales Cloud, E-Business Suite, Twitter, Salesforce and more*. However in this lab exercise, we will create a simple *SOAP* connection to connect a CRM Customer Activity Service interface.  
-   Now, do a search by entering `SOAP` in the search text box, then click `Select` button in the **SOAP** adapter connection box like below.
+6. In the home page of **Connections**, you should be able to locate the newly imported connection entities named as **XXX_CRM_CustomerService** and **XXX_ICSINTMGT_ProcessOffer** respectively.
 
-![](images/302/05.connection_create.png)
+![](images/302/05.connection_import.png)
 
-3. A new dialog window **Create New Connection** is shown, enter the following information to create our first *SOAP Connection*:
-    * **Name:** Provide an unique and easily identified *Connection* Name, such as <Your Short Name\_<System_Name>\_<Service_Name>. In our example, this is **KD_CRM_CustomerService**, while *KD* is short name of *Kelvin Durant*.
-	* **Identifier:** The **Identifier** will be automatically filled-in while you type the **Name** above, however you can provide another unique identifier, suggest include your short name as prefix.
-	* **Role:** Select **Invoke** from the drop-down list. (We are going to *Invoke* this service only)
-	* **Description (Optional):** You can leave it empty or enter any meaningful text to describe this *SOAP Connection*.
+7. Next, on the row of **XXX_CRM_CustomerService** Connection, click the hamburger menu icon at the right side and select `Edit` like below.
 
-![](images/302/06.connection_new.png)
+![](images/302/05.connection_import1.png)
 
-4. Click `Create` button, the **SOAP Connection** page with your provided **Name** is shown.
+8. The **XXX_CRM_CustomerService** Connection detail page is shown. As stated, this is a *SOAP* protocol based connection which will *Invoke* a service endpoint. We are going to define this connection detail.
 
 ![](images/302/07.connection_initial.png)
 
-5. Scroll down to **Connection Properties** section, click `Configure Connectivity` button, the **Connection Properties** dialog window is shown. Fill in the **WSDL URL** by providing **Property Value** in the format of:
+9. Scroll down to **Connection Properties** section, click `Configure Connectivity` button.
+
+![](images/302/05.connection_import2.png)
+
+10. The **Connection Properties** dialog window is shown. Fill in the **WSDL URL** by providing **Property Value** in the format of:
     * **http://\<Your Java Cloud Service Instance IP Address\>/crm/CustomerServicePort?WSDL**  
-	*\*If you forget your JCS instance IP address, [Click Here!](../Java%20Apps/java.cloud.md)*  
+	*\*If you forget your JCS instance IP address, [Click Here!](../../Java%20Apps/java.cloud.md)*  
 	Leave other properties **empty** as they are optional and not required in this lab exercise.
 
 ![](images/302/08.connection_properties.png)
 
-6. Click `OK` button to save changes made.  
-    Scroll down to **Security** section, click `Configure Security` button, the **Credentials** dialog window is shown.  
-    From **Security Policy**, select `No Security Policy` from the drop-down list. Although *Basic Authentication* and *Username Password Token* are supported, we skip to use no security policy which is used by the lab exercise.
-
-![](images/302/09.connection_security.png)
+11. Leave other property settings unchanged. Click `OK` button to save changes made.  
+Notice that `No Security Policy` is selected as this is required by the endpoint interface.  
 
-7. Click `OK` button to save changes made.  
-    From the **SOAP Connection** page, click `Test` from top right corner, the test **Confirmation** dialog window is shown.  
+12. From the top of **SOAP Connection** page, click `Test` from top right corner, the test **Confirmation** dialog window is shown.  
 	Click `Validate and Test` button.
 
 ![](images/302/10.connection_test.png)
 
-8. You should find a green dialog text area about **Connection was tested successfully**.
+13. You should find a green dialog text area about **Connection was tested successfully**.
 
 ![](images/302/11.connection_testresult.png)
 
-9. Next, click `Save` from top right corner.
+14. Next, click `Save` from top right corner.
 
 ![](images/302/12.connection_save.png)
 
-10. Similarly you should find a green dialog text area about **Connection was saved successfully**.  
+15. The **Save Changes?** dialog window appears to warn about reactivating integrations, just click `Save` to confirm and close the dialog.
+
+![](images/302/12.connection_save1.png)
+
+16. You should find a green dialog text area about **Connection was saved successfully**.  
     Click `Close` to exit and back to **Connection** Summary Page.
 
 ![](images/302/13.connection_saveresult.png)
 
-11. A *SOAP Connection* to CRM Customer Service was made and ready to be \*invoked\*.  
+17. A *SOAP Connection* to CRM Customer Service was updated and ready to be \*invoked\*.  
 
 #### Define REST Connection for ICS Service Exposure ####
 
-Now we are going to create another *REST* connection.  
+18. Now we are going to update the **XXX_ICSINTMGT_ProcessOffer** connection.  
     However, this time the *Connection* is **NOT** to \*invoke\* any endpoint service, but instead it is a *\*trigger\** which is being called by a front client, i.e. A mobile client *triggers* to this *REST* connection service.  
 
 	Make sure you are still on **Connections** Summary Page. If not, follow step 1 previously.  
+	On the row of **XXX_ICSINTMGT_ProcessOffer** Connection, click the hamburger menu icon at the right side and select `Edit` like below.
 
-	Click `Create` button on the top left corner, the **Create Connection - Select Adapter** dialog window is shown.  
-	Enter search text `REST` in the search text box, then click `Select` button in the **REST** adapter connection box like below.
-
-![](images/302/14.connection_create1.png)
+![](images/302/14.connection_rest.png)
 
-12. A new dialog window **Create New Connection** is shown, enter the following information to create our *REST Connection*:
-    * **Name:** Provide an unique and easily identified *Connection* Name, such as <Your Short Name>\_<System_Name>\_<Service_Name>. In our example, this is **KD_ICSINTMGT_ProcessOffer**, while *KD* is short name of *Kelvin Durant*.
-	* **Identifier:** The **Identifier** will be automatically filled-in while you type the **Name** above, however you can provide another unique identifier, suggest include your short name as prefix.
-	* **Role:** Select **Trigger** from the drop-down list. (We are going to *Trigger* this service only)
-	* **Description (Optional):** You can leave it empty or enter any meaningful text to describe this *REST Connection*.
-
-![](images/302/15.connection_new1.png)
-
-13. Click `Create` button, the **REST Connection** page with your provided **Name** is shown.  
-   This time, the page is more simpler due to the *Trigger* type connection.
+19. This time, the **XXX_ICSINTMGT_ProcessOffer** Connection detail page is shown and is more simpler due to the *REST Trigger* type connection.
 
 ![](images/302/16.connection_initial1.png)
 
-14. On **Security** section, click `Configure Security` button, the **Credentials** dialog window is shown.  
-    From **Security Policy**, the default and only available option is `Basic Authentication` from the drop-down list. This is the minimal security policy required by ICS.  
-	Click `OK` button to save changes made.
-
-![](images/302/17.connection_security1.png)
-
-15. From the **REST Connection** page, click `Test` from top right corner.  
+20. From **REST Connection** page, click `Test` from top right corner.  
     You should find a green dialog text area about **Connection was tested successfully**.
 
 ![](images/302/18.connection_test1.png)
 
-16. Next, click `Save` from top right corner.  
-    You should find a green dialog text area about **Connection was saved successfully**.  
+21. Next, click `Save` from top right corner.  
+Similarly, the **Save Changes?** dialog window appears to warn about reactivating integrations, click `Save` to confirm and close the dialog again.
+
+![](images/302/20.connection_save2.png)
+
+22. You should find a green dialog text area about **Connection was saved successfully**.  
     Click `Close` to exit and back to **Connection** Summary Page.
 
-[](images/302/19.connection_save1.png)
+![](images/302/19.connection_save1.png)
 
-17. Two *Connections* are just made ready, the **SOAP Connection - \*Invoke\* to CRM Customer Service** and **REST Connection - \*Trigger\* to ICS for Process Offer** respectively.
+23. Two *Connections* are just made ready, the **SOAP Connection - \*Invoke\* to CRM Customer Service** and **REST Connection - \*Trigger\* to ICS for Process Offer** respectively.
 
-[Procced to Next - 303: Create an Integration - An Orchestration Integration Flow](303-IntegrationsLab.md)
+[Procced to Next - 303: Complete an Integration - An Orchestration Integration Flow](303-IntegrationsLab.md)
 
 or