In addition to connecting to Altium Concord Pro through Altium NEXUS, and interfacing to it primarily through the Explorer panel and Components panel (for direct interaction with the managed components therein), you can also connect to it through a dedicated browser interface. In fact, connection in this way is more than just a connection to Altium Concord Pro itself. Rather it is a connection into the Altium Concord Pro server platform, with access to management interfaces for the various services available as part of the wider Concord Pro installation. Indeed, with some of these services, your only interaction with them is through this browser-based interface.
Accessing the Interface
To access your Altium Concord Pro installation through its browser interface, use a preferred external Web browser and type the address for Altium Concord Pro in one of the following formats:
http://localhost:<PortNumber> - if accessing from the same computer on which Concord Pro is installed.
(e.g. http://designerhome:9780, or http://localhost:9780, for an instance of Altium Concord Pro installed using the default port assignment). You will be presented with a Sign-in page.
Depending on your browser, you can drop the http:// part, and simply enter <ComputerName>:<PortNumber>, or localhost:<PortNumber>.
Sign in through the browser interface using the same Altium Concord Pro credentials used to connect through Altium NEXUS. For a newly installed Altium Concord Pro instance, there is a default administrative user with the credentials:
While the default admin user could be left for general entry to Concord Pro by administrators, it is a good idea to change the First Name, Last Name and Username to something more meaningful for your organization. And it's definitely a good idea to change the default password from admin to something only known/passed to authorized administrators - otherwise everyone could access Concord Pro as an administrator!
If you want to sign in using your Windows login credentials - taking advantage of Concord Pro's support for Windows Authentication - enable the Use Windows Session option.
Access Altium Concord Pro, and its associated platform services, through a preferred external Web browser. Roll the mouse over the image to see the effect of successfully signing in to the interface.
The interface provides a number of key technologies and services, and can be coarsely divided into two groupings, as shown in the following image, and listed thereafter.
The overall browser interface can be divided into two distinct sets of interface elements - those accessible in general by all users of Altium Concord Pro, and those accessible only by Concord Pro Administrators.
Interface elements that can be accessed by any Concord Pro user. Note that some sub-elements may be admin-only, and they will be highlighted in the detailed sections that follow. To access a page, click on its name within the left-hand navigation tree.
Interface elements that can only be accessed by a Concord Pro Administrator. A single, administrative user is provided, admin. This user, and any additional user, is bestowed administrative powers by membership to the role Administrators. To access a page, choose the required entry within the Admin section of the left-hand navigation tree.
The following additional elements are contained in the banner area, at the top of the interface:
Use the button located at the far left of the banner to toggle the view of the left-hand navigation tree between its Compact and Full modes.
The logo (next to the button) essentially verifies the type of managed content server you are working with (Altium Concord Pro).
At the far right of the banner, an entry reflects the user that is currently signed into Concord Pro, along with a picture (if defined), and the active page currently being viewed. The drop-down menu associated with the entry provides a control for logging out of Concord Pro.
The Notifications control () will flag any notifications - click this to access your Stream page, from where you can browse and read these notifications. Many such notifications can also be sent from Concord Pro through its email notifications service. For more information, see Configuring Server Email Notifications.
In addition, and for administrators only, the Health Monitor control () will flag a count of any warnings and errors detected by the server's Health Monitor. Click this to access the Health page of the interface.
General Access Interface Elements
The following sections summarize the elements of Concord Pro's browser interface that can be accessed by all users of Altium Concord Pro - both administrators and standard users.
This page provides quick reference information, tailored to, and relevant for, the Concord Pro user who is currently signed in through the interface.
Example content for a user on their Home page.
The page presents two lists:
My Projects - this is a graphical listing of managed projects that have been created by the signed-in user, complete with 3D image of the PCB (where available), name, and last modified date/time. The most recently created project appears at the top-left of the list. Double-click on a project entry to access the detailed management view for that project, in a separate tab. When accessed from the My Projects area, this view enables you to browse and comment on the source design itself, courtesy of Web Review functionality. For more detail on using this view, see Management of a Specific Project.
Click the button to access a menu of commands for the project:
Edit - use this command to access the Edit Project window, from where you can change the name and description for the project, as well as add server parameters (parameters that are added to a managed project and stored on the server-side).
Share - use this command to access the Manage Permissions window, from where access permissions for the project can be modified as required.
Delete - use this command to remove the project from Concord Pro (you will be asked to confirm).
Recent Activity - this is very much a reflection of the real-time notifications found on the Stream page of the interface. Each message includes a link to the entity affected by the event, on the relevant page of the interface. The most recent event appears at the top of the list.
This area provides the interface to the Identity Service (IDS), to define applicable service access, through specification of users and roles.
Access and manage the users of your Altium Concord Pro installation.
Controls are spread over the following sub-pages:
Users - use this page to create and manage a list of users; people who are to have access to Altium Concord Pro and/or the associated technologies installed with it.
Roles - use this page to create and manage a list of roles; roles allow you to further organize your users according to, for example, the particular section of the organization in which they are involved, or the design team they are in. Roles also make the sharing of Concord Pro content, and the configuration of other served technologies, more streamlined.
LDAP Sync - use this page to configure and run an LDAP Sync task. This allows an administrator of your Altium Concord Pro installation to leverage the network domain’s existing username and password credentials, so that user credentials do not have to be created manually one at a time on the Users page. When setup correctly, the Users page will automatically populate with user credentials, enabling any user listed to sign into Concord Pro using their regular corporate network username and password.
Sessions - use this page to quickly assess which of your users are currently signed into Altium Concord Pro. Provision is made for an administrator to terminate a user's access to Concord Pro by effectively 'killing' their active session, thereby freeing connections to the Server for use by others.
Two administrative users are provided with a new Altium Concord Pro installation - admin and System. The former, which is visible from the Users page, allows you to quickly get access to Concord Pro as an administrator. Once you have added other users, you can keep and edit the admin user (change its name and password for example), or delete it. The System user, which is not visible from the Users page, is used for all background tasks (including LDAP Sync, and Notifications). This user is permanently online.
Only an administrative user has full access to management controls. While a non-administrative user can browse Users and Roles, they cannot access LDAP Sync or Sessions. And while management of users by a non-administrative user is not generally possible, they are able to change the profile of their own user - including changing username and password, and uploading a photo.
This page provides the interface to the Projects service, to create and manage design projects in a central location, in a CAD-centric way, and share those projects for team collaboration as required. The page lists all projects that have been made available to Concord Pro, and which are shared with the currently signed-in user. Managed projects target the development stage of the project lifecycle, simplifying the creation and ongoing workflow for version controlled projects. From here you can create new projects, and open and manage existing ones. From this interface, a project can also be shared, or rather its access permissions configured.
The beauty of managed projects is that they are version controlled by default, and can be collaboratively worked upon without having to worry about shared drives, servers, agreements etc.
Prior to creating a new managed project, or converting an existing non-managed project, ensure that a Design Repository exists in which to store that project, and all future projects. Design Repositories are centrally managed as part of Altium Concord Pro, through its local Version Control service. A new installation of Altium Concord Pro provides a single Git-based design repository - Versioned Storage - for accommodating all of your managed design projects. If you have upgraded your Server from Altium NEXUS Server 1.0 (or Altium Vault 3.0), then use of SVN repositories will also be enabled, so that you can continue to use your previous (and established) design flow. In this case, you can continue to create repositories through the local Version Control service (SVN-only), or connect to external repositories (SVN or Git).
Centralized design project management - all part of your Altium Concord Pro installation.
A project created through this interface, or through Altium NEXUS, will initially be available to the designer who created it, and all Administrators for that Altium Concord Pro installation, in terms of full Read/Write access. The project will also be shared publicly, for Read-only access, to all users of Altium Concord Pro. Control accessibility - who a project is shared with, and therefore who has access to it - by configuring its permissions.
You can also access a manufacturing orientated CAD-centric view of the project, opened by selecting the required project and clicking the control above the listing of projects, or by double-clicking directly on the required project entry in the list. The Projects Management page for that project opens in a new browser tab incorporating the CAD-centric interface, which offers Design, Manufacturing and BOM view options:
Design - display and navigate source project design documents, view design object properties and place review comments. This view uses the Web Review interface. This view is for the latest version of the source project data, rather than a specified release from that project, and so could be considered to be a work-in-progress (WIP) view.
Manufacturing - view the releases for the project. Access is provided for opening a release, which will be presented on a separate tab through a Manufacturing Portal. From this portal you can view and navigate the released Assembly and Fabrication data, inspect the BOM, and ultimately download the data into a manufacturing Build Package.
BOM - view the source project's Bill Of Materials information.
Accessing the CAD-centric Projects Management page for a project. Here, the Design, Manufacturing and BOM views of the interface are shown. The Manufacturing view provides further access to a Manufacturing Portal, from which a manufacturing Build Package can be downloaded.
This page gives you access to the structure of Altium Concord Pro, and is similar in presentation and layout to that of the Explorer panel. From here, you will be able to browse the folders and Items within Concord Pro. And although you can't create or edit Items from within the browser interface (you can remove them), you are able to create and edit folders, and so build Concord Pro's structure, without having to be connected to it through Altium NEXUS.
You can also define sharing from this interface - controlling who is able to see what content in Concord Pro, and whether other users can simply view a folder and its content, or also edit it (effectively releasing design data into it). A single Altium Concord Pro installation can be partitioned into various effective 'zones' of content, but with controlled permissions, the content can be made selectively visible, or hidden, as required - giving the right people, the right access, to the right data.
Content can also be downloaded from Concord Pro, directly from this interface.
Browse and define the structure of your Altium Concord Pro installation, as well as defining access and being able to download content.
Concord Pro Administrators will be able to see and manage all Server content. For a shared user of Altium Concord Pro (non-admin), only those folders that have been shared - i.e. the user has permissions to access - will be accessible when the user signs in to that instance of Concord Pro.
Non-administrative users can only share a folder they have created.
This page provides a live feed of event notifications, applicable to, and relevant for, the Concord Pro user who is currently signed in through the interface. The page can be accessed in two ways:
By clicking the Stream entry within the left-hand navigation tree - this will list all notifications.
By clicking the Notifications control (), at the top-right of the interface. This will list all unread notifications (the number next to the Notifications control reflects the number of currently unread messages in the stream).
Example content for a user on their Stream page.
Each message in the stream carries similar information:
The name of the user whose action has resulted in the event.
The time the event happened (in terms of how many minutes, hours, days, weeks, months, or years have elapsed since the event occurred).
An automated message describing the event. A link is also included to the entity affected by the event. This can be:
A Managed Project (on the Projects page of the interface).
A Component Item Revision (on the Explorer page of the interface).
A Part Request (on the Part Requests page of the interface).
An optional user-added note, where available, that gives extra information.
The most recent event appears at the top of the list.
By default, all notification types are presented (unless accessed from the Notifications control, in which case only unread notifications will be listed). To change this, click on the All control and choose a particular notification type to display. Supported notification types are:
Projects (Project Create)
Projects (Project Update)
Projects (Project Delete)
Projects (Project commits)
Projects (Revision State Change)
Projects (Access Rights Add)
Projects (Access Rights Remove)
Components (Component Create)
Components (Revision State Change)
Library (Library Synchronisation Start)
Library (Library Synchronisation Complete)
Use the Mark as read control, to the right of a notification, to mark it as read. This removes that message from the unread list, and also from the number of unread messages indicated next to the Notifications control. To quickly clear the unread status from all messages, click the Mark All as Read control, at the top-right of the list.
This page enables you to create and manage requests for new managed components. An engineer can simply put in a request for one or more parts to be created, and get notified when that request has either been completed, and the component(s) made available, or rejected (and why). The requestor supplies as much key information to support their request as possible (manufacturer and part number(s), description(s), any relevant datasheet (PDF or URL)). Stub Component Items can even be created that the librarian can then run with (and finish off).
You'll need to specify which role (or roles) should be used to fulfill the role of Librarians for your organization. In essence, you are configuring a set of users of Concord Pro, that can be assigned to a part request. This is performed by an Administrator, through the Admin - Settings - Vault - Part Requests - Librarians Role page of Concord Pro's browser interface.
Adding a new part request through Concord Pro's browser interface. Hover over the image to see the form presented to receive the details of the request.
Initially, a part request is visible to the original requestor, and all members of the nominated librarian role(s). Once the request has been assigned to a particular librarian, only the requestor and that librarian will see it, and receive notifications about it.
Upon creation of a part request, the requestor, members of the Librarian role, and Concord Pro Administrators, will receive notification in their message stream, on the Stream page of Concord Pro's browser interface (and summarized on the Home page of that interface). In addition to the these event notifications, email notifications will also be received - providing the Email Notifications feature is enabled. This is performed by an Administrator, on the Email Notifications page (Admin - Settings - Email Notifications) of Concord Pro's browser interface.
Admin-Only Interface Elements
The following sections summarize the elements of Concord Pro's browser interface that can only be accessed by Administrative users of Concord Pro - those who are part of the Administrators role. Access to these elements is through the dedicated Admin area of the left-hand navigation tree.
If signed into Concord Pro as a non-administrative user, the Admin area of the tree will be hidden.
This page (Admin - Settings) provides a collection of sub-pages for configuration of options relating to various features and services provided by, and through, an Altium Concord Pro installation.
The Settings area - part of the admin-only pages within Concord Pro's browser interface.
When changing any settings, be sure to click the button, at the top-right of a page.
The left-hand side of the page provides a navigation tree with which to quickly access various sub-pages of settings. The following pages are available:
General - use this page to change the Name and Description for Concord Pro.
AltiumLive Credentials - when using the Private License Service through Concord Pro, these credentials allow the Private License Service (PLS) to communicate directly with your Altium account for the initial acquisition of your company licenses. Credentials must also be entered in order to access and obtain initial licensing for Concord Pro itself, from the Altium Cloud.
Session Lifetime - use this page to enter a value for the IDS Session Lifetime (in hours). This is how long a Concord Pro user has to remain connected, in a single session, when using a seat of the applicable Client Access License (Altium Concord Pro CAL). By default, the session lifetime is 24 hours.
License Manager - this page provides settings relating to using the Private License Service, and selection of its mode. A pre-set suitable default value is used for the Altium Cloud portal URL (http://portal2.altium.com/?cls=soap).
Email Notifications - this page provides settings to enable and configure Concord Pro's email notifications feature. This facility flags a variety of events to key stakeholders, relating to Component Items, Managed Projects, and Part Requests.
Vault - not a page, but rather a structural entry for gathering together settings related to specific functionality within Concord Pro itself.
Part Requests - a structural page to gather the following sub-pages related to the Part Request feature:
Librarians Role - use this page to specify which role (or roles) should be used to fulfill the role of Librarians for your organization. In essence, you are simply configuring a set of users of your Altium Concord Pro instance, that can be assigned to a part request. If you installed Concord Pro with sample data, then the sample role Librarians will already be prefilled here.
Custom States - use this page to customize opened and closed states for the Part Request feature.
Lifecycle Definitions - use this page to define and manage your Concord Pro's lifecycle definitions, complementing the ability to do this through Altium NEXUS. Providing better visibility of the states and transitions involved, each lifecycle is built in a graphical way, showing at-a-glance the flows involved.
Permissions - this page provides a single option that allows managed components to be deleted from Concord Pro, even if they have been placed on a design document.
Components - use this page to define default target folders in which new models should be created, when creating a new Component Item. To change a default folder, click the button. The Vault Explorer window will appear with which to choose the desired new default target release folder for that model type. Once chosen, click OK to close the window and return to the Components page, with the applicable field updated with the new folder path.
Projects - use this page to specify the default path (within Concord Pro's folder structure) for newly-released projects. You can also define default sharing permissions for new projects, so that the right users and/or roles have access to those projects from the moment they are created.
MCAD CoDesigner - this page provides a control to enable component recognition between the ECAD and MCAD domains, when using the ECAD-MCAD CoDesign feature. This facilitates recognition and therefore 1-1 mapping of components on either side, through the use of a dedicated Company Component ID. This ID is used for identifying components/items/parts within a company/team. This could be PartNumber, ManufacturerPartNumber, or an internal Item_ID (in a PDM/ERP). By having recognized (mapped) components, it means that components placed on the PCB on the MCAD side (Linking native ECAD & MCAD components) can be switched out for the native Altium PCB Footprints when the design is pulled into Altium NEXUS. Conversely, the recognition means that those native ECAD models (Altium PCB Footprints) are recognized when the design is pushed back to the MCAD side, and the MCAD software switches to use its native models.
Use the MCAD Company Component ID and ECAD Company Component ID fields to enter the parameter name being used to identify components in your MACD software and Altium NEXUS, respectively. By default, these fields are populated with the parameter name PARTNO. These fields are required if the Enable Components Recognition by Company Component ID option is enabled. If one or both are left blank, the button will be disabled.
This page (Admin - VCS) provides the interface to the Concord Pro installation's local Version Control Service, for managing the SVN-based Design Repositories that designers in the organization can validly access and use while working on design projects. Repositories can be created through this service, or external repositories can be connected to.
A new installation of Altium Concord Pro provides a single Git-based design repository for accommodating all of your managed design projects - and that's it! This avoids any setup and complexity regarding Concord Pro's local Version Control service. You have a single design repository - Versioned Storage - for all your designers to access and release into. As such, the VCS page of Concord Pro's browser interface becomes purely informational - you cannot add a new repository, and the single Git repository cannot be modified in any way, nor deleted. If you have upgraded to Altium Concord Pro from Altium NEXUS Server 1.0 (or Altium Vault 3.0), then use of SVN repositories will also be enabled, so that you can continue to use your previous (and established) design flow. In this case, you can continue to create repositories through the local Version Control service (SVN-only), or connect to external repositories (SVN or Git).
The browser-based interface to Altium Concord Pro's local VCS service.
This page (Admin - Part Providers) enables you to define a list of Part Sources - facilitating centralized supply chain management, with designers across the entire organization using the same approved list of Suppliers, with which to source supply chain intelligence for parts used in their designs.
The available Part Sources in Concord Pro are:
Altium Parts Provider - an aggregate supplier data service that provides access to live component information from a comprehensive range of parts suppliers. This Part Source is installed by default.
The Altium Parts Provider settings that are established in Altium Concord Pro will override those in Altium NEXUS (through the installed Altium Parts Provider extension) when a user signs in to Concord Pro.
Custom Database Parts Provider - for situations where parts supply data needs to be accessed from a local database, such as a company’s internal parts database, Concord Pro's Custom Database Parts Provider feature offers interface connectivity for all common database systems (directly, or via an ODBC or OLE-DB interface). The connection can be established manually, through a nominated interface and connection string, or by using Concord Pro's Connection Wizard. Any number of such connections can be defined.
A database connected to by the Custom Database Parts Provider interface system must be locally available to Altium Concord Pro - that is, the database itself must be located on the PC that hosts Concord Pro. In addition, for Altium NEXUS to be able to interface to any parts database connection that has been setup in Concord Pro, the Custom Database Parts Provider extension must be installed as part of your Altium NEXUS installation (which it is by default).
The actual supply chain intelligence - comprising Manufacturer (and part number), Supplier (and part number), Description, Pricing and Availability - is sourced from Concord Pro's local Part Catalog and the relevant Part Source.
Each Altium Concord Pro instance has its own dedicated Part Catalog. This is a managed local part catalog database, dedicated to the management and tracking of manufacturer parts and their associated supplier parts. The catalog is installed as a service (Part Catalog Service), provided through the Altium Concord Pro platform, and works only with Altium Concord Pro. The local Part Catalog stores items representative of actual Manufacturer Parts, along with one or more items representative of Supplier Parts - the incarnations of those Manufacturer Parts, as sold by the Suppliers/Vendors. Each Supplier Part is a reference to an item in a parts database - either the aggregate parts database of the Altium Parts Provider (which itself interfaces to, and gathers the parts from, enabled Suppliers), or a linked local parts database.
Enabling required Suppliers and determining Location/Currency ranges for the Altium Parts Provider. This is the default Part Source for Altium Concord Pro. You can also add any number of links to internal company parts databases.
This page (Admin - Health) provides a web-based Health Monitor. The page delivers a visual summary of the state of the host machine, and the Concord Pro storage system.
The Health page provides an instant view of the status and health of your Concord Pro installation, and the system on which it is installed.
As well as the quick visual summary of the server's health, the page also provides the following functionality:
Ability to generate a status report for sending to Altium's Support (and ultimately Altium's Developers). To do so, click on the Generate part of the Generate status report for support team text, in the Status area of the page - the necessary reports will be generated and collated in a single Zip archive (vault_status_report_<Date>.zip) and downloaded to your browser's default download folder.
Ability to download all log files - containing Error and Warning entries from all of the server’s available Log files, and which are normally located in the \ProgramData\Altium\ConcordProData\logs folder. To do so, click the Download all logs link, in the Logs section of the page. The files will be collated into a single Zip archive (AllLogs.zip) and downloaded to your browser's default download folder.
Use the Clear logs link (located at the bottom of the Logs section of the page) to archive, then delete all existing log files. The archive (logs_<Date>.zip) will be stored in the \ProgramData\Altium\ConcordProData\logs.archive folder.
To manually refresh the status of your server, click the refresh status link, in the Status area of the page. The health of your server and system will be checked and the page refreshed with the current state accordingly. The date and time reflect the last time the server health was checked.
Note that after initial install of Altium Concord Pro, initial check of server health takes about 5 minutes after accessing the Health page. You can perform a manual refresh to perform the check sooner. Subsequent automatic checking is carried out every 4 hours.
The Altium Concord Pro installation also includes a Health Monitor that can be launched as a standalone tool - on the computer hosting Concord Pro - using the desktop shortcut that is created when Concord Pro is installed. Alternatively, the Health Monitor tool can be found in the \Program Files (x86)\Altium\Altium Concord Pro\Tools\HealthMonitor folder as the avhealth.exe executable. Note that the folder also includes a simplified command-line tool: avConsoleHealth.exe. In this standalone variant, the Health Monitor operates as an independent entity that queries Concord Pro and its host system, and is therefore able to deliver crucial data and information even in the unlikely event that Concord Pro is not fully functioning. For more detailed information regarding this standalone tool, see Health Monitor.
This page (Admin - Licenses) provides the interface to obtain and manage licenses - both for the licensing of Concord Pro itself, and also for serving to client machines over the local network, through the appropriately configured Private License Service (PLS).
Use the various tabs within the Licenses area to obtain, manage, and assign licensing for Concord Pro, and for serving to your local network through the PLS. And use the various reports that are available to keep an eye on license usage.
Three tabs are available:
Licenses - provides a listing of all licenses currently available. At least two licenses will be required to actually license Altium Concord Pro (Altium Concord Pro and Altium Concord Pro CAL). Other licenses can be added for serving through the PLS. Licenses can be acquired either From cloud (choose from a list of licenses available to your company from the Altium portal), or From file (import existing alf license files from disk).
Roles - provides the ability to assign licenses to Roles of Users (or groupings of users). In Local PLS mode, the Concord Pro PLS can selectively offer software licenses that have been assigned to a specific Role. By default (unless otherwise specified), all licenses acquired by Concord Pro are assigned to theAll Users Role, and therefore available to any User that connects to the PLS.
Reports - the Private License Service includes a range of license usage monitoring and reporting features that can be used to audit how licenses are used within an organization. This is useful for ensuring that the best use is being made of the available license seats, for anticipating future license requirements, and to determine the usage of individual Users. A range of reporting options are available, accessed by specific sub-tabs. Depending upon the type of information that's required for each report, the associated reporting filters can be applied to tailor the results to include specific Licenses, Roles, Users, and time periods. There is also an option to export the current report to disk in CSV format, compatible with Microsoft Excel and other spreadsheet applications, for administration and accounting purposes.
This page (Admin - Component Sync) provides the interface to the Component Sync Service. It is from here that you define the connection to an enterprise system instance, including configuration file, and enable/configure synchronization of your enterprise system components with those in Concord Pro.
With the interface set up and working, features and functionality are provided that cater for the uni- or bi-directional synchronization of your component data between your instance of Altium Concord Pro and your enterprise system instance. Configuration allows you to specify which parameters are mastered in which system. In addition, Item parameters enable you to update a Component Item's properties in Concord Pro (configurable per field), without having to formally release a new revision of that Component Item.
Altium Concord Pro does not offer full PLM integration - this level of integration is only available through Altium NEXUS. Note also that synchronization of Part Choice data is unidirectional - from the enterprise system to Altium Concord Pro only.
To create a new interface instance, click the button. As many instances can be defined as required, to interface your Altium Concord Pro installation to various different enterprise system instances. For example, your components might reside in one instance, or perhaps different divisions are using different instances (of the same or differing enterprise system). Each instance must be uniquely named and have a configuration file. To test the connection for a defined instance, click the button.
Sample configuration files are provided - click the Download sample configuration link to obtain the zip file ConfigurationSamples.zip. This zip contains basic configuration files for Windchill, Arena and Agile PLM systems. Modify these to suit your company's requirements.
Add and configure the interface to your company's enterprise system. With a valid connection, you can schedule synchronization of components between that system and your Concord Pro instance.
Synchronization of components between Concord Pro and the connected enterprise system instance - or to be more specific, their parametric data - is very flexible, and involves the following:
Configuring the synchronization for each component type. This involves:
Determining the direction of synchronization.
Determining which components are involved, and where new components are to be created.
Configuring parameter mapping.
Performing the synchronization.
The first item is handled in the configuration file used for the connected enterprise system instance. The synchronization itself can be performed on-demand, from the Component Sync page of Concord Pro's browser interface, and/or can be scheduled - automated synchronization at periodic intervals, defined when configuring the connection to the enterprise system instance.
To set up scheduled synchronization requires you to provide valid credentials (for your enterprise system). Click the button and enter your User name and Password into the subsequent System Credentials window. Without valid credentials, scheduled synchronization will remain in the OFF state. On-demand synchronization will also not be possible.
This page (Admin - Status) provides status-related information for Concord Pro, and quick access to log files. It is presented over three regions:
Installed Services - providing version information for the current Altium Concord Pro installation.
Path to database and files - providing information about the installation paths for the database and data, including the type of database being used by Altium Concord Pro.
Logs - providing information about the installation path to log files. For each distinct service, click on the associated icon to download a zip containing the relevant set of log files.
The Status page provides installation details, as well as log files for the various services.