Operation test
This page concerns the OnPremises option.
With the "Software as a Service" option, no server installations by the customer are necessary.
To check the installation, the various applications can be called up individually.
TIP
For the most common problems, solutions are listed on the Troubleshooting page.
Admin/Dashboard
If the steps in primedocs Server Commissioning have been followed, accessing the dashboard via the browser should work.
HealthMonitor
The HealthMonitor provides information on the state of the OneOffixx server applications and data.
The information is conveniently displayed in the dashboard. For this purpose https://your-url.local/datasourceadminapp/HealthMonitor can be called. This page also lists further information about the HealthMonitor.
The HealthMonitor can also be accessed directly via https://your-url.local/HealthMonitor/v1/status or https://your-url.local/HealthMonitor/v1/status/detailed (authentication required according to configuration in OneOffixx.config). However, this information is not conveniently displayed when called with the browser. See https://your-url.local/datasourceadminapp/HealthMonitor for more information.
Client
For testing purposes, the OneOffixx Client should be installed. This is best done on another machine, but can also be done on the server as well. Prerequisite for a client test on the server: The OneOffixx server applications must be accessible from the same URL as from the outside. If they are only accessible via localhost, the test might fail. This can be tested by calling https://your-url.local/service in the browser – a primedocs logo should be displayed.
The .msi file can be obtained from the dashboard in the Downloads tab.
During the installation of the client the "custom installation" should be selected. During module selection, all modules can be deselected, since there is usually no Office installed on the server anyway. In the installer, the service URL (e.g. https://your-url.local/Service/primedocs.svc) as well as client id and client secret must be specified (except in the "WithoutIdS" option, where client id and client secret are not required).
If the client can successfully log on to the service and data is synchronized, the installation was successful.
Test server applications with browser
All server applications respond to requests from the browser in one way or another. The URLs are listed below:
| Application | URL | Expected result in browser |
|---|---|---|
| Service | https://your-url.local/service | Web page displaying only the OneOffixx logo |
| DatasourceAdminApp | https://your-url.local/datasourceAdminApp | Forwarding to IdentityServer for standard option, IIS Windows authentication prompt for "WithoutIdS" option |
| HealthMonitor | https://your-url.local/healthmonitor/v1/status | Simple 0, 1, 2, or 3 (no website) |
| AddressService | https://your-url.local/addressservice/swagger | Swagger UI web page |
| WebApi | https://your-url.local/webapi/swagger | Swagger UI web page |
| AdminApp | https://your-url.local/adminApp | Forwarding to IdentityServer |
| App | https://your-url.local/app | Forwarding to IdentityServer |
| Connect | https://your-url.local/connect | Web page with description of API |
| IdS/IdentityServer | https://your-url.local/ids/Account/Login | Web page with login form |
| IdSWindowsAuth | https://your-url.local/idswindowsauth/Home/Error | Web page with error message. Alternatively try .../idswindowsauth/Account/Login: IIS Windows authentication prompt |
TIP
If you have any questions or problems, we are happy to help – simply contact our support team.