The Public Access front end client can be installed to a separate new stand-alone web application separate from the Public Access server.
To install thePublic Access front end client to a stand-alone web application:
- In IIS Manager, create a new website to install the Public Access front en client application to. For example, PublicAccessClient.
- Copy the ..\ PublicAccessServer\!samples\assets folder and all its contents from the build directory to the physical root directory of the new website. For example, C:\inetpub\wwwroot\PublicAccessClient.
- Copy the ..\PublicAccessServer\_obpa\ folder and all its contents from the build directory to the physical root directory of the new website.
- Copy the ..\PublicAccessSever\!samples\styles.css file from the build directory to the physical root directory of the new website.
- Copy the ..\ PublicAccessServer\!samples\sample-cq folder and all its contents from the build directory to the physical root directory of the new website.
- From the newly copied PublicAccessClient\sample-cq folder, open the obpa-config.json file in a plain-text editor.
-
Within the api object, the value of the url key must be set to the URL of the
Public Access API. Specifically, this URL is the virtual path to the directory
containing the Public Access bin folder, with /api appended. For example, “url”:
“https://example.gov/PublicAccessServer/api”.
Note:
If the API will be hosted on a separate server with a different domain or sub-domain as the front-end client, refer to Cross-Origin Resource Sharing (CORS) for further configuration instructions.
- Save and close the obpa-config.json file.
- From the newly copied PublicAccessClient\sample-cq folder, open the index.html file in a plain-text editor such as Notepad.
- Within the OBPA files section, the value of the src URL must be updated to reflect the change in folder structure. Specifically, one directly level should be removed. For example, src=“../_obpa/obpa_dependencies.js” src=“../_obpa/obpa_app.js".
- Save and close the index.html file.
-
If Full Text Search is to be used, copy the ..\
PublicAccessServer\!samples\sample-ft folder and all its contents from the build
directory to the physical root directory of the new website. Make the same
corresponding edits to the PublicAccessClient\sample-ft files as described in
steps 6 through 11 above.
Note:
The sample-cq and sample-ft folder names can be changed to be appropriate for their usage. For example, CourtDocumentSearch. Additionally, those folders can be copied at the same directory level and used to add additional pages to the web site for other public search use cases. See Front-End Client Configuration for further instructions on configuring page level settings.
- In IIS Manager, create a new application pool for Public Access.
-
Configure the following in the Advanced Settings for the application pool:
- Set the .NET CLR Version to v4.0.
- Set Enable 32-Bit Applications to False.
- Set Managed Pipeline Mode to Integrated.
- Right-click the website you want to add Public Access to and select Add Application.
-
Configure the following in the Add Application dialog
box:
- Enter an Alias for the application. For example, PublicAccessClient.
- Assign the Public Access Application pool you created to the application.
- In the Physical path field, enter the path of the ..\PublicAccessClient\ folder which you create at the physical root directory of the website. For example C:\inetpub\wwwroot\PublicAccessClient.