 |
Now the central service PARTapplicationServer can also be used for PARTsolutions and replaces the SearchServer. Up to now it only had been used for CADENAS Apps, PARTcommunity Mobile and for a while as PARTserver backend. Now the same technique is used for PARTsolutions. The user can search catalogs as usual, even if the catalog server is located at another company site. There is only ONE DATA directory.
User cases for the PARTapplicationServer:
Used by CADENAS App (PARTapplicationServer is located on CADENAS site).
Used by PARTsolutions V9.8 in order to avoid distribution and synchronization of catalog data (PARTapplicationServer is located at company site).
In the future PARTsolutions can also use the CADENAS catalog server. In this way customers can save maintenance expenditure. (Supplier catalogs on the CADENAS-PARTapplicationServer and own parts on an inhouse PARTapplicationServer.)
Access from third party systems such as PDM systems for example to the inhouse PARTapplicationServer, in order to show additional information.
Access from third party systems such as CAD systems for example to the CADENAS website PARTapplicationServer, in order to directly show CADENAS content from there.
Using the PARTapplicationServer results in the following advantages:
Replication of $CADENAS_DATA is obsolete
The larger the catalogs database, the more time exposure is needed for the replication.
As of V9.08 catalog data does not have to be replicated to other locations. The replication can be omitted, because the PARTapplicationServer is much faster. If, however, it should also prove advantageous, caching via SQUID is possible at secondary locations in addition.
Using the PARTapplicationServer makes it possible to only install catalogs at one location and all clients - regardless at which location - access this one PARTapplicationServer.
In so far link speed and latency play a role and thus caching. Caching holds downloaded parts as long as they are obsolete.
The two following figures compare the multisite installation structure up to V9.07 and as of V9.08:
Higher security - No user access to $CADENAS_DATA
The new concept leads to higher security: Direct, file based access to geometries is no longer possible. There is no direct access to $CADENAS_DATA anymore. Thus users do not have to have access rights for $CADENAS_DATA.
Direct access to $CADENAS_DATA only by administration
Administrative applications like PARTadmin directly access the 23d-libs directory with writing permission further on, because these have to perform changes there.
PARTapplicationServer also at Single workstation installation
The PARTapplicationServer is also used for Single workstation installation (automatically started with
pdatamgr.exe). This is advantageous, because then the search is outsourced and nevertheless can be used by all programs on the respective computer (PARTdataManager and Seamless for example). Thus more free memory is available, which again enhances the search speed.Settings are performed in PARTadmin.
Please perform the AppServer client configuration in PARTadmin -> category AppServer client.
Catalog browsing and search with AppServer
As of PARTsolutions V9.08 there is only ONE central data directory.
All access (catalog browsing and search) is processed via PARTapplicationServer - regardless from which location.
Thus select this option, if PARTsolutions is used remotely without synchronization of catalog data.
Using the local AppServer is advantageous compared to
pdatamgr.exe. This is running on 64Bit, whereby possible memory problems are avoided.The local AppServer is only used for searching, not for catalog browsing.
The AppServer is automatically started and exited together with PARTdataManager. If Seamless is also started, then Seamless uses the already running application.
In the status bar, right below, an AppServer icon is displayed.
Technical details on the PARTapplicationServer are found under PARTapplicationServer-Installation.