The Red Hat Ecosystem Catalog is the official source for discovering and learning more about the Red Hat Ecosystem of both Red Hat and certified third-party products and services.
We’re the world’s leading provider of enterprise open source solutions—including Linux, cloud, container, and Kubernetes. We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.
IBM Cloud Pak for Automation V20.0.2 - IBM FileNet External Share
The following information was extracted from the containerfile and other sources.
Summary | You can securely share documents that are stored in your FileNet P8 repository with external users by using the IBM Content Navigator external share feature. When configured, your users can select documents in FileNet P8, share the document links with external users who can then view and download the documents that are shared with them |
Description | The Universal Base Image is designed and engineered to be the base layer for all of your containerized applications, middleware and utilities. This base image is freely redistributable, but Red Hat only supports Red Hat technologies through subscriptions for Red Hat products. This image is maintained by Red Hat and updated regularly. |
Provider | IBM Corporation |
The following information was extracted from the containerfile and other sources.
Repository name | IBM® FileNet External Share |
Image version | 3.0.7 |
Architecture | amd64 |
Exposed ports | ["9443/tcp" "9080/tcp"] |
User | 50001 |
Working directory | JAVA_/opt/ibm/java/jre |
kubectl create secret
command.
$ kubectl create secret docker-registry admin.registrykey --docker-server=cp.icr.io --docker-username=cp --docker-password="<API_KEY_GENERATED>" --docker-email=<USER_EMAIL>
Note: The
cp.icr.io
value for the docker-server parameter is the only registry domain name that contains the images.
Note: Use “cp” for the docker-username. The docker-email has to be a valid email address (associated to your IBM ID). Make sure you are copying the Entitlement Key in the docker-password field within double-quotes.