Contact our corporate or local offices directly.
Parent page: Altium NEXUS Server
Altium facilitates the ability for an organization to copy the content they need from a source server, and deliver it to a second target server – a process referred to simply as Server Data Acquisition.
By acquiring design content, ownership is placed firmly in the hands of the receiving organization, who are free to make local modifications and maintain the content as they desire moving forward. And by keeping a link between the acquired data and its original source, intelligent handling of the data can be performed. So for example, if down the track, a change is made to a design item in the source server, the target server has the ability to update to that new revision, resynchronizing with the 'mother ship' as it were. And no matter if additional releases have been made to an item locally, there is always the possibility to revert to a previous revision from the source server – all by keeping a link back to the item's original source, or Origin.
Data Acquisition is delivered as a service through the Altium NEXUS Server platform. The Data Acquisition service is installed as part of the Altium NEXUS Server installation.
Verification that the Data Acquisition service is running can be performed from the Windows Internet Information Services (IIS) Manager panel – accessed from Window's Administrative Tools window. Simply check to confirm the following Application Pool is in the
Altium NEXUS Server – Data AcquisitionService
The following image provides a higher-level, graphical illustration of the data acquisition concept. The principles of data acquisition depicted are the same, regardless of the type of data being acquired.
The following Item types can be acquired from a source server, into a target server, using the Data Acquisition feature:
Things to take into consideration when acquiring data:
Draft), as determined by the assigned lifecycle definition for the target Item. Any lifecycle history for the source Item revision will be ignored.
Related page: Using the Content Cart
Acquisition is performed using the Content Cart dialog which is accessed from within the Explorer panel. While browsing the source server from which you wish to obtain data, right-click on an Item Revision that you'd like to acquire and choose the Operations » Add to Content Cart command from the context menu. You can add one or more selected Item Revisions, or even a folder of Items (which will load the cart with the latest revision of all Items in that folder).
Use the Content Cart to acquire all the data content you need. The process of acquiring data Items from a source server can be summarized in the following steps:
Transfer new revision and item. While the default acquisition options (see point 3 above) are applied during this preparation phase, the properties of individual target Items can be modified if required. To do so, select an Item in the list and click the button.
Acquired data points back to its original source. This ancestral link information can be seen by changing the aspect view for the target Item revision to its Origin aspect view. The information is available only when the Origin (source) server is available and connected – see point 1 above.
For those who would like to know about the data transfer mechanisms behind the Data Acquisition process, the following section provides more insight into the basic procedural flow employed by the feature, and the general scenarios encountered when managing data acquisition.
The following image takes a closer look at the mechanics of acquiring data from a source server. It illustrates the procedural flow involved, to essentially copy a chosen revision of a source item between the nominated source and target servers.
As can be seen, the procedure essentially boils down to three distinct stages, ensuring that the data is transferred between servers whilst maintaining its integrity:
In the previous section, the basic flow of acquisition was seen. To effectively manage the acquisition of data, the relative history of both the source and acquired items is tracked, so that the relevant acquisition actions are available to the designer through the acquisition management interface.
The following sections take a look at the general scenarios encountered when managing data acquisition. In each case, the state of the acquired data – in terms of target Item and any revisions – is compared with its original source Item and its revisions.
In this scenario, no revision of the source Item has been acquired previously. A source Item revision is to be acquired into the initial revision of a new target Item. The new target Item and revision is created as part of the acquisition setup.
In this scenario, a revision of the source Item has been previously acquired. The source Item has subsequently been modified, leading to a later revision being available. In this case, a new revision of the existing target Item would be created, to acquire the later source Item revision.
So in practice, even though the latest revision may have been acquired to a different target server Cart folder, the system imports the new revision into the existing Component Item. That component now has the new revision available, which will be detected automatically when a project that uses the component is opened – indicated by an
Out of date status in the Properties panel, Item Manager or ActiveBOM document.
In this scenario, the latest revision of the source Item has already been acquired – there is nothing further to acquire.
Contact our corporate or local offices directly.