List of Component ID's in Deployed Process (Local Atom)

Document created by tommy_conway636242 Employee on Jun 1, 2017Last modified by tommy_conway636242 Employee on Jun 5, 2017
Version 2Show Document
  • View in full screen mode

If you have a local atom and a process deployed to that atom, you may want a to be able to find a list of the component ID's of each component that is deployed within that process. The process and many of the components have XML that is stored, when deployed, in the <atom_installation_directory>/processes/<process_ID> directory. The following process is a sample of how to pull in all the XML files for a certain process and pull back all component ID's.

 

Process

This process is the main process, which will pull in the XML files, send them to a sub process to filter out the component ID's, names, and version numbers, and then combine the files to get one list.

 

 

The Disk Connector pulls in the XML file from the directory mentioned above. They go the sub process which looks like below:

 

 

This sub process takes each XML file, and goes through a flow control shape to process each one individually. Each XML file is then mapped to retrieve the component ID, name and version number. The map is shown below.

 

 

The input profile contains just the information we need from the XML files and is mapped to an XML file that contains only the component ID, name, and version number. This is to make it easier to combine into one file later in the process. We then return the documents to the calling process. Back in the calling process we combine the documents on the "elements" element which has the Max Occurs value set to Unbounded and the Looping Option value set to Unique. The CompId, name, and version elements have the Max Occurs value set to 1 and the Looping Option value set to Unique. We write it to a disk directory and this gives us an output that looks like the following:

 

<Element>
   <elements>
      <CompId>0610df34-9f06-46b0-b15d-3d6f0fe005bb</CompId>
      <version>1</version>
      <name>Connection_Name</name>
   </elements>
   <elements>
      <CompId>0ead5f34-7abd-40c2-84dd-2f42f4a473f6</CompId>
      <version>2</version>
      <name>Operation_Name</name>
   </elements>
   <elements>
      <CompId>108ba535-463f-477a-a447-0c1384236843</CompId>
      <version>5</version>
      <name>XML_Profile_Name</name>
     </elements>
   <elements>
      <CompId>3d73355b-b0ff-4d2f-b78e-f36e93166ca3</CompId>
      <version>6</version>
      <name>Map_Name</name>
   </elements>

 

1 person found this helpful

Attachments

    Outcomes