On this tabbed page, you can specify the server name, certificate, and ports for the cache server :
- Key
Hostname of the cache server without a domain. It determines the name of the configuration block
[server:<hostname>]inpappcache.cfg.- DNS Name
Name, under which the service will later be accessible; also the list of allowed CORS origin hostnames (multiple names separated by commas). This entry can be changed. If a matching certificate for this name is already stored on the computer, it will be found automatically. Alternatively, instead of the hostname, you can enter the display name of a certificate preceded by @ (e.g., @PAPPCACHE ).
- Certificate
For the cache server, a separate certificate must be issued for the respective computer so that the clients trust the connection . In PARTadmin, a certificate signing request (CSR) , which is forwarded to your own CA or the domain administrator . The signed certificate is then imported. The private key must be accessible on the machine — the same requirements apply as for the regular app server.
- Ports
By default, these are the same as the ports used by the app server (HTTP 9020, HTTPS 9022), since typically only the hostname is changed.
- HTTP/2
The use of HTTP/2 via ALPN negotiation is configurable— just like on the main server.
![[Note]](https://webapi.partcommunity.com/service/help/latest/pages/en/partsolutions_admin/doc/images/note.png) | Note |
|---|---|
A prerequisite for starting the service is that a valid certificate is displayed for the specified hostname. The service should not be started until after you click Save. | |
After the initial configuration, the AppServer and AppServer Cache must be restarted once; after that, the cache reloads the configuration every 60 seconds, provided that something has changed. This allows for further administration to be carried out entirely via PARTadmin, even without logging in to the cache server itself—for example, if it is operated at a remote location.