Main features of Deployment V2

• Deployment occurs on the element (Gateway, Message, etc.) level
• Deployments can occur independently (easier for multiple users in one environment)
• Visual changes to channels and elements noting completeness and status
• Certificates, lookup tables, partners and documents they now auto-deploy upon saving

Walkthrough Deployment V2

Q Create a new channel, enable and deploy it

The first step to create and deploy a new channel is to create and configure all the channel components (Gateway IN, Message IN, Transformation, Message out and Gateway out).

Once you created, configured and saved each single channel component, a pop-up notification will appear to notify you that your channel is ready to be activated once you hover the cursor over the channel status label which will be "INACTIVE" in this case as shown below:



Now, it is the time to activate your channel, this is by pressing on the below highlighted button.



Once you pressed on this button, only this channel will be enabled and deployed, see below.





Thus, the channel is active and ready for message processing. 

Q Disable a channel

If you want to disable any channel, all what you need to do is to open the channel and press on the below highlighted button, see below.





Thus, this channel is off and is not ready anymore for message processing.

P.S.

If you are unable to deploy, hovering over this icon  will also tell you what part of your channel is incomplete so that you can fix it.

Q One update and deploy within a single channel

When you make a single change to an enabled channel, you will see a notification of the pending change ready to deploy, see below.





Clicking on the “Deploy updates” will allow you to run a deployment for only the elements with changes.

In this case, I have only changed the gateway IN component, accordingly clicking on “Deploy updates” will just deploy the change on gateway IN, see below.



In case you really need to deploy this change, you will need to just press confirm and make sure you selected the needed change for deployment.







P.S.

Please notice that when gateway IN configuration is changed, its icon has been changed to the new status icon related to element change ready to deploy, see below.





Q multiple updates and deploy within a single channel

When you make multiple changes to an enabled channel, you will see a notification of the pending changes ready to deploy, see below.





Clicking on the “Deploy updates” will allow you to run a deployment for ALL the elements with changes.

In this case, I have changed the gateway IN and gateway out component, accordingly clicking on “Deploy updates” will deploy the change on these two components, see below.





By clicking on “Confirm” all the checked changes will be deployed.

P.S.

You can choose the element subjected to next deployment by check or uncheck the check box related to this change, see below.







In this case, by clicking on “confirm”, only the highlighted changes will be deployed.

Q multiple update and deploy within a multiple channel

When you make multiple change to multiple enabled channel, you will see this notification Deploy update(s) of the pending changes ready to deploy in each channel. In the channel overview tab, by clicking on “Deploy Pending” you will see all the changes within all the channels in your environment.







By clicking “confirm” all the changes in this list will be deployed and you have the right to uncheck the change you don’t need to deploy.

P.S.

Once clicked on “Deploy Updates” or “Deploy Pending” the deploy list for this channel will appear as seen below, and there will be two options to select the group by of updates:





None: Contains the list of elements (Gateway In/Out, Message In/Out, Transformation)







Channel: Contains the list of channel(s), It will be one channel in case of “Deploy Updates” within the channel elements and it will include all the deployable channels in case clicking on “Deploy pending” button on the main channels over view page.







Deployment List Properties 

On the deploy list there is two groups as mentioned:

• Channel

This lists the deployable channels and it has the below properties:

• Check box: To select the channels you want to deploy (In case of no check found this means this channel has change that is shared with another channel which will be on the list too, and we can check these changes by clicking on ( ) in show details.
• Type: Here it will be channel as per the group.
• Action: It describes the action that will affect the channel after deployment:

1. Deploy: this means the channel will start and On.
2. Update: This means the channel is already in production but have some updates will be pushed to production.

• Last update date: Shows the date of last change within the channel.
• Show details: On clicking on the ( ) a list of the changes within the channel will appear, it will have the same properties as the main deploy list.  



• None

This lists the deployable changes/addition over all channels like gateways In/Out, Message In/Out transformation, routing, notifications, etc, and here below its properties:

• Check box: To select the change you want to deploy including the channels.
• Type: The type of change like routing, channel, gateway In/Out,,,, etc .
• Action: it describes the action that will affect the change listed after deployment

1. Deploy: This means the change will start in case of new additions.
2. Update: Push the updates done to production.
3. Undeploy: In case of a previous used Gateway In /Out or transformation or Message In/Out that will be no longer used by any channel.

• Last update date: Shows the date of last change within the channel.
• Used In: Shows this change is used in which channel or gives a list of the channels used in in case affects more than one channel. 

Element Notification 

There are 4 notations that describe the element properties and next action:

• Circled arrows: This indicate that the element had some changes which will take effect once deployed.





• The correct sign: This means that this element is deployed, and no changes happened to it after deployment.





• The plus sign: This means that this element still needs to be implemented.







• The exclamation mark: This indicates that there is still some missing configuration on this element and it won’t be deployed.