文件列表:

HTTPSReference.md (4032, 2023-09-26)
NetworkRequirements.md (1730, 2023-09-26)
OperationsReference.md (4946, 2023-09-26)
ParameterReference.md (14620, 2023-09-26)
QuickStart.md (5953, 2023-09-26)
fiskaltrust DE ByoDC TestCall.postman_collection.json (5685, 2023-09-26)
how-to-fiscal-cloud-connector.md (2530, 2023-09-26)
how-to-multiple-installations.md (1073, 2023-09-26)
howto-single-instance.md (1906, 2023-09-26)
images/ (0, 2023-09-26)
images/ByoDC-Loadbalancer.png (72239, 2023-09-26)
images/ByoDC-Quickstart-0-DockerConfig.png (152556, 2023-09-26)
images/ByoDC-Quickstart-1-Namespace.png (12770, 2023-09-26)
images/ByoDC-Quickstart-2-AddRepo.png (40284, 2023-09-26)
images/ByoDC-Quickstart-3-Install.png (227240, 2023-09-26)
images/ByoDC-Quickstart-4-Browsertest.png (42286, 2023-09-26)
images/ByoDC-Quickstart-5-CashboxConfig.png (55670, 2023-09-26)
images/ByoDC-Quickstart-6-QueueConfig.png (98234, 2023-09-26)
images/ByoDC-Quickstart-7-3-Echo.png (153577, 2023-09-26)
images/ByoDC-Quickstart-7-4-Initial-Operation-Receipt.png (428137, 2023-09-26)
images/ByoDC-Quickstart-7-5-POS-Receipt.png (602012, 2023-09-26)
images/ByoDC-Quickstart-7-6-TSE-Info.png (756609, 2023-09-26)
images/ByoDC-Quickstart-7-PostmanCollection.png (60282, 2023-09-26)
images/ByoDC-Quickstart-8-PostmanResponse.png (80556, 2023-09-26)
images/HowToFCC-SCU-Configuration.png (22202, 2023-09-26)
images/fiskaltrust-ByoDC-Architecture-Overview.png (541884, 2023-09-26)
images/fiskaltrust-ByoDC-Echo-Postman.png (55300, 2023-09-26)

# fiskaltrust.Middleware - Bring your own Data Center ### Problem description: You have a distributed architecture of your point of sale system and therefore you are not able to connect a tse device directly to your pos-terminal. An on site (branchoffice) installation of the fiskaltrust.Middleware is not possible or would not be efficient. ### Solution proposal: By providing a standardized hardware platform by the customer, fiskaltrust.Middleware using a cloud-tse can be brought to the datatcenter directly where the receipt generation process of a distributed point of sale system occurs. This can be devlivered by a predefined Kubernetes Namespace which can be deployed by a Helm-Chart. fiskaltrust provides a "Backend POD" Docker image and Helm-Charts to deploy your own environment. ## Architecture Overview  ## [helm chart](https://github.com/fiskaltrust/product-de-bring-your-own-datacenter/blob/master/https://github.com/fiskaltrust/helm-charts/tree/master/bring-your-own-datacenter) ## Requirements * Kubernetes cluster > v1.22 * helm > v3.0 * Network Connection Matrix and used IP Scopes can be found at [Network Requirements](https://github.com/fiskaltrust/product-de-bring-your-own-datacenter/blob/master/NetworkRequirements.md) ## Quickstart A brief step-by-step guide to get ByoDC up and running on your Docker Desktop can be found [here](https://github.com/fiskaltrust/product-de-bring-your-own-datacenter/blob/master/QuickStart.md) ## Installation ### Install Emissary Ingress Install emissary ingress v3.x. Please follow the [official installation instructions](https://github.com/fiskaltrust/product-de-bring-your-own-datacenter/blob/master/https://www.getambassador.io/docs/emissary/3.6/topics/install/helm). ### Create Namespace Connect to your Kubernetes cluster and create the `bring-your-own-datacenter` namespace. ```sh kubectl create namespace bring-your-own-datacenter ``` ### Add helm repository First add the fiskaltrust helm repository. ```sh helm repo add fiskaltrust https://charts.fiskaltrust.cloud/ ``` Update helm repository ```sh helm repo update ``` > ***Note:** You can also skip this step, clone this repo and use the path to the `Chart.yaml` file as repo in the following commands.* ### Configure values You can view all configurable values by running the following command. ```sh helm show values fiskaltrust/bring-your-own-datacenter ``` This will output a `values.yaml` file containing all of the default values. You can create a file `config.yaml` and override the values you need. ### Install chart You can install the chart like this: ```sh helm install bring-your-own-datcenter fiskaltrust/bring-your-own-datacenter --namespace bring-your-own-datacenter -f config.yaml ``` Leave out `-f config.yaml` to install it with default values. > ***Note:** If you use a local repo you will have to run `helm dependency update` before installing.* ## Updating Please see the [Migration Guide](https://github.com/fiskaltrust/product-de-bring-your-own-datacenter/blob/master/https://github.com/fiskaltrust/helm-charts/blob/master/bring-your-own-datacenter/MIGRATION.md) for update instructions of specific versions. If the version is not listed in the Migration Guide you can update the chart like this: ```sh helm repo update helm upgrade --install bring-your-own-datcenter fiskaltrust/bring-your-own-datacenter --namespace bring-your-own-datacenter -f config.yaml ``` > ***Note:** The backend Pods will automatically update to the newest minor Middleware version. If this behaviour is not wanted you can set the [`byodc.image.tag` Parameter](https://github.com/fiskaltrust/product-de-bring-your-own-datacenter/blob/master/./ParameterReference.md#section-byodc) in your `config.yaml` to a specific version (e.g. `1.3.29-buster`). ## Uninstallation ```sh helm uninstall bring-your-own-datacenter --namespace bring-your-own-datacenter kubectl delete namespace bring-your-own-datacenter ``` ## Supported Configurations ## Queues * MySQL ## SCUs * FiskalyCertified * [SwissbitCloud](https://github.com/fiskaltrust/product-de-bring-your-own-datacenter/blob/master/#Host-FiscalCloudConnector-instances-in-Bring-your-own-Data-Center) ## Parameter Reference All Parameters and values you can use in "values.yaml" can be found [here](https://github.com/fiskaltrust/product-de-bring-your-own-datacenter/blob/master/ParameterReference.md) ## HTTPS Reference How to deal with SSL Certificates on the Ambassador endpoint can be found [here](https://github.com/fiskaltrust/product-de-bring-your-own-datacenter/blob/master/HTTPSReference.md) ## API Reference ByoDC uses [swagger](https://github.com/fiskaltrust/product-de-bring-your-own-datacenter/blob/master/https://swagger.io/) to provide [OpenAPI](https://github.com/fiskaltrust/product-de-bring-your-own-datacenter/blob/master/https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md) service definitions of the exposed API. The API Explorer can be found at the `/swagger` endpoint and the OpenAPI definition at `/swagger/v1/swagger.json`. ## Operations Reference Collection of OPS related topics and QnAs [here](https://github.com/fiskaltrust/product-de-bring-your-own-datacenter/blob/master/OperationsReference.md) ## Host FiscalCloudConnector instances in Bring your own Data Center Bring your own Data Center can be configured to host FiscalCloudConnector instances in kubernetes. More details can be found [here](https://github.com/fiskaltrust/product-de-bring-your-own-datacenter/blob/master/how-to-fiscal-cloud-connector.md). ## Minimal installations In scenarios where only very few CashBoxes are operated and high availability is not a crucial factor, it's also possible to host a standalone instance of the BYODC container. More details can be found [here](https://github.com/fiskaltrust/product-de-bring-your-own-datacenter/blob/master/howto-single-instance.md). ## Multiple installations in one cluster If you want to run multiple different ByoDC installations on the same cluster you will need to install the Emissary Ingress in both namespaces. More infos can be found [here](https://github.com/fiskaltrust/product-de-bring-your-own-datacenter/blob/master/how-to-multiple-installations.md).

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：