First some background: Each Enterprise based Smart Mover Task will automatically log into the required server if the running Process has not already done so. This is known as an “implicit” log in. And when an “implicit” log in was used, when the Task finishes then it will automatically log out of that server. You do not need to include an Enterprise Logout Task. In fact, you really never need to use the Enterprise Logout Task because Smart Mover will automatically log out of all Enterprise servers used during each Process at the end of that Process.
So there are 2 situations where you actually want or need to use the Enterprise Login Task.
1. If your Process includes multiple Enterprise Tasks that access the same server then you can save some time and reduce some server load by starting the Process with an Enterprise Login Task. This way each Enterprise Task will not issue an implicit log in and out.
2. The Enterprise Login Task has the option to save the log in response received from the server… which is an xml file that includes attributes of your Enterprise server including Brands, Issues, Categories, Users, etc… Using XSL Transformations and other techniques that data can then be used in subsequent Tasks.