Admin Dashboard for document publication is a spring boot application and React JS SPA. This dashboard has capability to publish a document directly to production.

What is document?

    Document is a set of information in the form of HTML/XML/Multi Page (Rich Html)/PDF. It could contain product installation steps, troubleshooting guide, Product details etc.

Who has access for Admin Dashboard?

    It’s admin portal, not exposed to anon users, It needs login and based on user roles and content organization, documents can be viewable and publish to main portal.

What could be the state of a documents in dashboard?

Documents could be in multiple state such as PENDING, RELEASE CONDIDATE, PUBLISH, UNPUBLISH, AVAILABLE, DELETED.

Admin Dashboard for document publication is a spring boot application and React JS SPA. This dashboard has capability to publish a document directly to production.

What is document?

    Document is a set of information in the form of HTML/XML/Multi Page (Rich Html)/PDF. It could contain product installation steps, troubleshooting guide, Product details etc.

Who has access for Admin Dashboard?

    It’s admin portal, not exposed to anon users, It needs login and based on user roles and content organization, documents can be viewable and publish to main portal.

What could be the state of a documents in dashboard?

Documents could be in multiple state such as PENDING, RELEASE CONDIDATE, PUBLISH, UNPUBLISH, AVAILABLE, DELETED.

Admin Dashboard for document publication is a spring boot application and React JS SPA. This dashboard has capability to publish a document directly to production.

What is document?

    Document is a set of information in the form of HTML/XML/Multi Page (Rich Html)/PDF. It could contain product installation steps, troubleshooting guide, Product details etc.

Who has access for Admin Dashboard?

    It’s admin portal, not exposed to anon users, It needs login and based on user roles and content organization, documents can be viewable and publish to main portal.

What could be the state of a documents in dashboard?

Documents could be in multiple state such as PENDING, RELEASE CONDIDATE, PUBLISH, UNPUBLISH, AVAILABLE, DELETED.

The KM-Doc-Service-Rest Application connects to KMDB for the purpose of delivering data to drive the document display.  This service is a boot/swarm application within the km repo (services).

Why we need this feature?

This service replaces the use of 1.0 doc display and 2.0 Media Storage for documents.

Doc Service REST API end-point details

1. Metadata Retrieval End Point
2. Payload Retrieval End Point (Dynamic Publishing End Point)
3. Attachment Payload Retrieval End Point (Dynamic Publishing End Point)
4. Doc View Count Retrieval End Point
5. Doc Products Retrieval End Point
6. Save Feedback End Point
7. Feedback questions and Ratings Retrieval End Point

The Doc display web application is developed using spring boot and Grommet framework. This module is used to display the HTML and PDF documents in HPESC portal for troubleshooting a issue related to HPESC software, driver, patch etc. This module also enables the users to provide feedback related to a document.

Doc display Web replaces the use of 1.0 doc display. This application is used in HPESC portal to view a document. 2.0 doc-display has below advantage over 1.0 doc-display

Loading documents from CDS# to KMDB

As part of Digital support experience project, document on-boarding system has been redesigned and developed with new age technologies. In this architecture, we have created new application for document loading (from CDS# etc sources) to load documents to the new KM data base. This application is called km-doc-loader module in the KM repo. This application runs as spring boot application in swarm-based environment. Doc Service REST API end-point details

Doc-loader-rest API details : republish, reset subscription, upload, publish

Km-Doc-Ingester Functionalities details

This service is a boot/swarm application within the km repo which imports metadata about documents from Gluster and stores in KMDB.

Why we need this feature?

This service will load the data into KMDB.

1. Read data from Kafka topic
2. CV Mapping
3. Retry publishing
4. Notification service

:  Patch storage and Integration in Portal

Patch Storage Rest service API is Spring boot/swarm based application in hpesc-patch repository. This API is used to download patch file(s) in raw or in format of zip, gzip and tar(from Gluster FS). This application has public and protected endpoints. Public endpoints are free content which do not need authorization code to download patch(es) but Protected endpoints are required authorization code to download patch(es).

Why do we need this feature?      

To facilitate the customers to download patches, This service will be used. This application is migration of the FFS servers and it's code repository.

Patch-storage-rest API details

1. List the public patches file(s) and path.
2. Download patch file.
3. Validate user and get authorization code with roles.
4. Provide capability to download a single patch binary after validation of user authorization code.
5. Provide capability to download a set of patch binaries after validation of user authorization code.