Teamcenter-Aurora integration overview
Aurora architecture
| Component | Description and Purpose |
|---|---|
| Aurora Client (Web Start) | This is the version of the Aurora client that is started using Java Web Start. A session-specific URL is provided to the user to start the Aurora client and to automatically connect to the specified session. The user need not install the Aurora client separately. |
| Aurora Client | This is the Aurora client version that can be separately installed from the Aurora installable rather than using Aurora Web Start. Using this, the user can initiate a new Aurora session or connect to a running Aurora session. This is an optional component. |
| Aurora API Client | This is the non-interactive client that is provided to enable the integration with Teamcenter. The API client is used by Teamcenter-Aurora Connector to exchange the data between Teamcenter and Aurora. |
| Aurora Web Start | Aurora facilitates launching its client application using JNLP (Java Network Launch Protocol). This is hosted on the web server, which allows the user to start the Aurora client software for the Java Platform directly from the internet using a web browser. |
| Aurora Meta Server | When a user starts a new Aurora client, it initially connects to the Aurora metaserver. The metaserver checks the user permission and connects to a valid Aurora server session. If an Aurora server session is not running, it starts a session. |
| Aurora Server | The Aurora server executes all the requests from the client and broadcasts the response back to all the clients connected to that server session. |
| Database | This is an optional component. It is used by the Aurora server session to load or save the data from the database. |
| File | If the database component is not configured, the user can save the model as a file in a file system. |