Currently we're in an environment that was set up with a single ISF Library. However, over the last 3 years in which we've been using this library, it has become quite bloated and oversized for a .js file.
We are looking for best practices on reducing file size. We have thought about creating service specific libraries or something along those lines.
Can anyone provide what type of approach they've used?
We've moved away from using a single ISF file for all services. Right now we've got the standard custom file which contains common ISF functions used by all services. Then we've broken out specific functionality for service categories into their own custom ISF files.
For example, all of our ISF for ID services are in their own seperate .js file. This helps break up the size of the file but also is handy when you have multiple people working on Service Design.
In relation to having multiple libraries, how do you attach all of the field level scripting for an individual service?
Do you have an automated attach routine or do you manually attach scripting?
I have been able to come up with a method to automatically attach a script library associated only with a particular service, but I'm still working on trying to update our automated attach routine to create/attach the field level functions. Any insight someone would have in this area would be
This document explains the logic to develop Tidal Enterprise
Orchestrator workflow to automate the process of creating vCenter
Resource Pool* vSphere Power CLI must be installed either on the TEO
server or vCenter* vMA can also be used to achieve the same...
IntorductionCisco Process Orcehstrator (CPO) ships with the webservices
adapter that can be used to make Web Service API call to REST or SOAP
based applications. Before a sample workflow to make SOAP API calls
using CPO, lets understand some of the fundam...