Embed Size (px)
Citation preview
Page 1 of 22
IBM FileNet Content Manager on the AWS Cloud
Quick Start Reference Deployment
January 2020
(last update: April 2020)
Kevin Trinh, Vincent Le, Abraruddin Khan, Matt Vest and Sivaji Yara
IBM Digital Business Automation team
Vinod Shukla and Jim McConnell, AWS Quick Start team
Visit our GitHub repository for source files and to post feedback,
report bugs, or submit feature ideas for this Quick Start.
Contents
Overview .................................................................................................................................... 2
IBM FileNet Content Manager on AWS ................................................................................ 3
Cost and licenses .................................................................................................................... 3
Architecture ............................................................................................................................... 5
Planning the deployment .......................................................................................................... 7
Specialized knowledge ........................................................................................................... 7
Technical requirements ......................................................................................................... 7
Deployment options ...............................................................................................................8
Deployment steps ...................................................................................................................... 9
Step 1. Sign in to your AWS account ...................................................................................... 9
Step 2. Obtain an IBM FileNet Content Manager license ..................................................... 9
Step 3. Download the Oracle SQL client and JDBC driver ................................................. 10
Step 4. Launch the Quick Start ............................................................................................. 11
Parameters for deploying IBM FileNet Content Manager into a new VPC ..................... 12
Amazon Web Services – IBM FileNet Content Manager on the AWS Cloud April 2020
Page 2 of 22
Step 5. Test the deployment ................................................................................................. 17
Check the deployment completion status ........................................................................ 17
Create the FileNet P8 components URLs ........................................................................ 18
Log in to the FileNet P8 environment .............................................................................. 19
Best practices for using IBM FileNet Content Manager on AWS ........................................... 19
Security .................................................................................................................................... 19
Troubleshooting ...................................................................................................................... 19
Send us feedback .................................................................................................................... 20
Additional resources .............................................................................................................. 20
AWS account ....................................................................................................................... 20
Document revisions ................................................................................................................. 21
This Quick Start was created by the IBM Digital Business Automation team in collaboration
with Amazon Web Services (AWS).
Quick Starts are automated reference deployments that use AWS CloudFormation
templates to deploy key technologies on AWS, following AWS best practices.
Overview This Quick Start reference deployment guide provides step-by-step instructions for
deploying a production-ready instance of IBM FileNet Content Manager version (version
5.5.4) on the AWS Cloud into a virtual private cloud (VPC) spanning multiple Availability
Zones for high availability. IBM FileNet Content Manager enables enterprise users to
manage content and documents, perform transactional content processing, and build and
integrate content services into applications.
This Quick Start is for those who want to use Amazon Elastic Compute Cloud (Amazon
EC2), Amazon Elastic File System (Amazon EFS), Amazon Elastic Kubernetes Service
(Amazon EKS), and AWS CloudFormation to launch Kubernetes and IBM FileNet Content
Manager in their container environment.
This deployment uses the Amazon EKS Architecture Quick Start as a foundation for a fully
managed, highly available, and certified Kubernetes-conformant control plane for FileNet
Content Manager.
Amazon Web Services – IBM FileNet Content Manager on the AWS Cloud April 2020
Page 3 of 22
IBM FileNet Content Manager on AWS
IBM FileNet Content Manager enables you to create business applications with embedded
content services, including content governance and lifecycle management, external file
sharing, content collaboration, video streaming and more from a single content solution.
The core of the solution includes repository services for capturing, managing, and storing
digital assets. Multiple repositories, called object stores, can be created and managed
through federated governance capabilities within a unified system to provide consistency,
increased information quality, and enterprise-wide compliance.
Object stores can be configured to store content in a database, a file system, and storage
devices that support an Amazon Simple Storage Service (Amazon S3) application
programming interface (API).
IBM FileNet Content Manager uses a range of AWS services and features, including:
Security groups
Amazon EC2
Amazon EFS storage
Amazon EKS
AWS CloudFormation
Elastic Load Balancing
After deployment, you can configure and extend FileNet Content Manager for your specific
business applications and use cases. For more information about IBM FileNet Content
Manager, see IBM FileNet Content Manager.
Cost and licenses
You are responsible for the cost of the AWS services used while running this Quick Start
reference deployment. There is no additional cost for using the Quick Start.
The AWS CloudFormation template for this Quick Start includes configuration parameters
that you can customize. Some of these settings, such as instance type, will affect the cost of
deployment. For cost estimates, see the pricing pages for each AWS service you will be
using. Prices are subject to change.
Amazon Web Services – IBM FileNet Content Manager on the AWS Cloud April 2020
Page 4 of 22
Tip: After you deploy the Quick Start, we recommend that you enable the AWS Cost
and Usage Report to track costs associated with the Quick Start. This report delivers
billing metrics to an S3 bucket in your account. It provides cost estimates based on
usage throughout each month and finalizes the data at the end of the month. For
more information about the report, see the AWS documentation.
This Quick Start requires licenses for IBM FileNet Content Manager.
You must also provide an entitlement key in order to download the FileNet Content
Manager containers. Obtain a key from the Container Software Library.
The Quick Start templates provision an Oracle database instance using the License Included
service model. Information about the costs associated with this service model is available at
Oracle Licensing Considerations.
Page 5 of 22
Architecture Deploying this Quick Start for a new virtual private cloud (VPC) with default parameters
builds the following IBM FileNet Content Manager environment in the AWS Cloud.
Figure 1: Quick Start architecture for IBM FileNet Content Manager on AWS
The Quick Start sets up the following:
A highly available architecture that spans multiple Availability Zones.
A VPC configured with public and private subnets according to AWS best practices, to
provide you with your own virtual network on AWS.
In the public subnets:
– Managed network address translation (NAT) gateways to allow outbound
internet access for resources in the private subnets.
– A Linux bastion host in an Auto Scaling group to allow inbound Secure Shell
(SSH) access to EC2 instances in public and private subnets.
– A Remote Desktop Gateway (RD Gateway) host in an Auto Scaling group to
provide secure remote access to instances in the private subnets.
Amazon Web Services – IBM FileNet Content Manager on the AWS Cloud April 2020
Page 6 of 22
In the private subnets:
– Active Directory domain controllers for Microsoft Active Directory deployed in
two availability zones/private subnets for redundancy. The Active Directory
service is used to provide Lightweight Directory Access Protocol (LDAP) services
for the FileNet Content Manager components.
– Amazon Relational Database Service (Amazon RDS) for Oracle as the database
for IBM FileNet Content Manager.
– FileNet Content Manager containers in an Amazon EKS cluster.
Amazon Elastic File System (EFS), used as the underlying network file system, for
configuration and content storage.
Figure 2: IBM FileNet Content Manager component architecture
For the FileNet Content Manager components, the Quick Start templates perform the
following tasks:
Configure and start all the required containers.
Create LDAP users and groups.
Amazon Web Services – IBM FileNet Content Manager on the AWS Cloud April 2020
Page 7 of 22
Create and configure Oracle databases for Content Platform Engine and IBM Content
Navigator.
Create a FileNet P8 domain, object store, and workflow system. The FileNet P8 domain
contains the object stores, advanced storage areas, and other entities. Advanced storage
Areas are used to store content on the Amazon (EFS) storage device.
Create a text search server and an index area on the Content Search Services node.
Index Areas, which store information necessary to perform full-text indexing, are also
created on the Amazon EFS storage device.
Create an IBM Content Navigator repository and desktop.
Content Management Interoperability Services (CMIS) is an optional component that
can be configured to provide interoperability services across different content
management services.
Content Services GraphQL is an optional component that provides query language APIs
to facilitate application development for the Content Platform Engine.
Planning the deployment
Specialized knowledge
This Quick Start assumes familiarity with the IBM FileNet Content Manager suite.
This deployment guide also requires a moderate level of familiarity with AWS services. If
you’re new to AWS, visit the Getting Started Resource Center and the AWS Training and
Certification website for materials and programs that can help you develop the skills to
design, deploy, and operate your infrastructure and applications on the AWS Cloud.
Technical requirements
Before you launch the Quick Start, your account must be configured as specified in the
following table. Otherwise, the deployment might fail.
Amazon Web Services – IBM FileNet Content Manager on the AWS Cloud April 2020
Page 8 of 22
Resources If necessary, request service quota increases for the following resources. You might
need to do this if you already have an existing deployment that uses these resources,
and you think you might exceed the default quotas with this deployment. For default
quotas, see the AWS documentation.
AWS Trusted Advisor offers a service quota check that displays your usage and quotas
for some aspects of some services.
Resource This deployment uses
VPCs 1
Elastic IP addresses 2
AWS Identity and
Access Management
(IAM) security groups
1
IAM roles 18
Auto Scaling groups 3
Application Load
Balancers
2 or 4 (if optional components
are deployed)
EC2 instances 7
Regions This deployment includes Amazon Elastic File System (EFS), which isn’t currently
supported in all AWS Regions. For a current list of supported Regions, see AWS
Regions and Endpoints in the AWS documentation.
Microsoft Active Directory is also included in this deployment. For a list of supported
Regions, see Region Availability for AWS Directory Service in the AWS documentation.
Key pair Make sure that at least one Amazon EC2 key pair exists in your AWS account in the
Region where you are planning to deploy the Quick Start. Make note of the key pair
name. You are prompted for this information during deployment. To create a key pair,
follow the instructions in the AWS documentation.
If you deploy the Quick Start for testing or proof-of-concept purposes, we recommend
that you create a new key pair instead of specifying a key pair that’s already being used
by a production instance.
Deployment options
This Quick Start provides the following deployment option:
Deploy IBM FileNet Content Manager into a new VPC (end-to-end
deployment). This option builds a new AWS environment consisting of the VPC,
subnets, NAT gateways, security groups, bastion hosts, and other infrastructure
components, and then deploys IBM FileNet Content Manager into this new VPC.
The Quick Start provides all templates required for this option. It also lets you configure
Classless Inter-Domain Routing (CIDR) blocks, instance types, and IBM FileNet Content
Manager settings, as discussed later in this guide.
Amazon Web Services – IBM FileNet Content Manager on the AWS Cloud April 2020
Page 9 of 22
Deployment steps
Step 1. Sign in to your AWS account
1. Sign in to your AWS account at https://aws.amazon.com with an IAM user role that has
the necessary permissions. For details, see Planning the deployment earlier in this
guide.
2. Ensure that your AWS account is configured correctly, as discussed in the Technical
requirements section.
3. Use the Region selector in the navigation bar to choose the AWS Region where you want
to deploy FileNet Content Manager on AWS. The deployment is restricted to AWS
Regions with at least three Availability Zones.
4. Select the key pair that you created earlier. In the navigation pane of the Amazon EC2
console, choose Key Pairs, and then choose your key pair from the list.
5. Choose an existing S3 bucket or create a new one to store the prerequisite database
client and deployment log files.
6. Use the IAM console to get your access key ID and access key secret. More information
about obtaining the access key ID and secret is available at Managing Access Keys for
IAM Users.
7. Use the AWS Certificate Manager to create a Secure Sockets Layer (SSL) certificate.
Step 2. Obtain an IBM FileNet Content Manager license
This Quick Start requires licenses for IBM FileNet Content Manager.
If you already own licenses for IBM FileNet Content Manager, you can use the Bring Your
Own License model (BYOL).
Otherwise, purchase IBM FileNet Content Manager licenses from Passport Advantage or an
IBM representative. For assistance with Passport Advantage, see the Passport Advantage
Online for customers or eCustomer care webpages.
You must provide an entitlement key to download the FileNet Content Manager containers.
Obtain a key from the Container Software Library.
The Quick Start templates provision an Oracle database instance using the License Included
service model. For more information about the costs associated with this service, see Oracle
Licensing Considerations.
Amazon Web Services – IBM FileNet Content Manager on the AWS Cloud April 2020
Page 10 of 22
Step 3. Download the Oracle SQL client and JDBC driver
This Quick Start uses Amazon RDS for Oracle as the database for IBM FileNet Content
Manager.
Download the following Oracle SQL client and Java Database Connectivity (JDBC) driver:
Oracle Instant Client for Linux x86-64 version 19.3.0.0: instantclient-basiclite-
linux.x64-19.3.0.0.0dbru.zip and instantclient-sqlplus-linux.x64-19.3.0.0.0dbru.zip.
Oracle database 12.2.0.1 JDBC driver.
Upload these files to the S3 bucket from Step 1. Note the path to the client files because it is
used in the parameters section.
For example, the following figure shows a path to the S3 bucket.
Figure 3: Download location of Oracle client files
To obtain the file location, select a file, and then click Copy Path.
Amazon Web Services – IBM FileNet Content Manager on the AWS Cloud April 2020
Page 11 of 22
The copied path value in this example is s3://ibm-fncm-
assets/oracle_client_files/instantclient-basiclite-linux.x64-19.3.0.0.0dbru.zip.
The S3 file location in this example is ibm-fncm-assets/oracle_client_files.
Important: Do not include the prefix “s3://” or the client file name in the file
location value.
Step 4. Launch the Quick Start
Notes: The instructions in this section reflect the older version of the AWS
CloudFormation console. If you’re using the redesigned console, some of the user
interface elements might be different.
You are responsible for the cost of the AWS services used while running this Quick
Start reference deployment. There is no additional cost for using this Quick Start.
For full details, see the pricing pages for each AWS service you will be using in this
Quick Start. Prices are subject to change.
1. Sign in to your AWS account, and launch the AWS CloudFormation template.
Deploy IBM FileNet Content Manager
into a new VPC on AWS
The entire deployment process takes about 2 hours to complete.
2. Check the AWS Region that’s displayed in the upper-right corner of the navigation bar
and change it if necessary. This is where the network infrastructure for IBM FileNet
Content Manager is built. The template is launched in the US East (Ohio) Region by
default.
Note: This deployment includes Amazon EFS, which isn’t currently supported in all
AWS Regions. For a current list of supported Regions, see the AWS Regions and
Endpoints webpage.
• new VPC
• workloadDeploy
Amazon Web Services – IBM FileNet Content Manager on the AWS Cloud April 2020
Page 12 of 22
3. On the Select Template page, keep the default setting for the template URL, and then
choose Next.
4. On the Specify Details page, change the stack name if needed. Review the parameters
for the template. Provide values for the parameters that require input. For all other
parameters, review the default settings and customize them as necessary.
In the following table, parameters are listed by category and described for the
deployment. When you finish reviewing and customizing the parameters, choose Next.
PARAMETERS FOR DEPLOYING IBM FILENET CONTENT MANAGER INTO A NEW VPC
View template
VPC network configuration:
Parameter label
(name) Default Description
Availability Zones
(AvailabilityZones)
Requires input List of Availability Zones to use for the subnets in the VPC. The
Quick Start uses the Availability Zones from your list.
VPC CIDR
(VPCCIDR)
10.0.0.0/16 CIDR block for the VPC.
Private subnet 1 CIDR
(PrivateSubnet1CIDR)
10.0.0.0/19 CIDR block for the private subnet located in Availability Zone 1.
Private subnet 2 CIDR
(PrivateSubnet2CIDR)
10.0.32.0/19 CIDR block for the private subnet located in Availability Zone 2.
Private subnet 3 CIDR
(PrivateSubnet3CIDR)
10.0.64.0/19 CIDR block for the private subnet located in Availability Zone 3.
Public subnet 1 CIDR
(PublicSubnet1CIDR)
10.0.128.0/20 CIDR block for the public subnet located in Availability Zone 1.
Public subnet 2 CIDR
(PublicSubnet2CIDR)
10.0.144.0/20 CIDR block for the public subnet located in Availability Zone 2.
Public subnet 3 CIDR
(PublicSubnet3CIDR)
10.0.160.0/20 CIDR block for the public subnet located in Availability Zone 3.
Allowed external
access CIDR
(RemoteAccessCIDR)
Requires input CIDR IP range permitted to access the deployment. CIDR block
parameter must be in the form x.x.x.x/x. We recommend that
you set this value to a trusted IP range. Otherwise, specify
0.0.0.0/0 to access it from anywhere.
Remote Desktop
Gateway external
access CIDR
(RDGWCIDR)
Requires input Allowed CIDR block for external access to the RD Gateway
instances.
Amazon Web Services – IBM FileNet Content Manager on the AWS Cloud April 2020
Page 13 of 22
Amazon EC2 configuration:
Parameter label
(name) Default Description
Key pair name
(KeyPairName)
Requires input A key pair that allows you to connect securely to your instance
after it launches. This is the key pair you created in your
preferred AWS Region; see the Technical requirements
section.
SSL certificate ARN
(sslCertArn)
Requires input Amazon Resource Name (ARN) for the SSL/TLS certificate
managed by IAM or ACM (e.g., arn:aws:acm:us-east-
1:558510413658:certificate/xxxxx-xxxx-xxxx-xxxxx). It’s
required for secure HTTPS communication. You can use the
AWS Certificate Manager to manage SSL certificates.
Amazon EKS configuration:
Parameter label
(name) Default Description
Node instance type
(NodeInstanceType)
t2.large Type of EC2 instance for the node instances.
Number of nodes
(NumberOfNodes)
3 Number of Amazon EKS node instances.
Node group name
(NodeGroupName)
Default Name of Amazon EKS node group.
Node volume size
(NodeVolumeSize)
20 Size of the node's root EBS volumes.
Additional EKS ARNs
(AdditionalEKSAdmin
Arns)
Optional Comma-separated list of IAM users/roles to be granted
administrator access to the EKS cluster.
Lambda zip bucket
name
(LambdaZipsBucketName)
Optional Name of the bucket where the Lambda .zip files should be
placed. If it’s left blank, a bucket is created.
Kubernetes version
(KubernetesVersion)
1.14 Kubernetes version of the Amazon EKS cluster.
Microsoft Active Directory configuration:
Parameter label
(name) Default Description
Domain controller 1
instance type
(ADServer1Instance
Type)
m5.xlarge Amazon EC2 instance type for the first Active Directory
instance.
Amazon Web Services – IBM FileNet Content Manager on the AWS Cloud April 2020
Page 14 of 22
Parameter label
(name) Default Description
Domain controller 1
NetBIOS name
instance
(ADServer1NetBIOSName)
DC1 NetBIOS name of the first Active Directory server (limited to
15 characters).
Domain controller 1
private IP address
(ADServer1PrivateIP)
10.0.0.10 Static private IP for the first Active Directory server located in
Availability Zone 1.
Domain controller 2
instance type
(ADServer2Instance
Type)
m5.xlarge Amazon EC2 instance type for the second Active Directory
instance.
Domain controller 2
instance NetBIOS
name
(ADServer2NetBIOSName)
DC2 NetBIOS name of the second Active Directory server (limited
to 15 characters).
Domain controller 2
private IP address
(ADServer2PrivateIP)
10.0.32.10 Static private IP for the second Active Directory server located
in Availability Zone 2.
Remote desktop
gateway instance type
(RDGWInstanceType)
t2.large Amazon EC2 instance type for the RD Gateway instance(s).
Microsoft Active Directory configuration:
Parameter label
(name) Default Description
Domain DNS name
(DomainDNSName)
example.com Fully qualified domain name (FQDN) of the forest root
domain.
Domain NetBIOS
name
(DomainNetBIOSName)
example NetBIOS name for users of older versions of Windows (limited
to 15 characters).
Domain administrator
(DomainAdminUser)
Admin User name for the domain administrator. This is separate from
the default administrator account.
Domain administrator
password
(DomainAdminPassword)
Requires input Password for the domain administrator (must contain a
combination of at least 8 letters, numbers, and symbols).
Number of Remote
Desktop Gateway
hosts
(NumberOfRDGWHosts)
1 Number of RD Gateway hosts.
Amazon Web Services – IBM FileNet Content Manager on the AWS Cloud April 2020
Page 15 of 22
Oracle RDS configuration:
Parameter label
(name) Default Description
Oracle client files
location
(ORAFilesLocation)
Requires input Provide the location of the downloaded Oracle client files, but
do not include the “s3://” and the trailing forward slash. For
more information, see Step 3. Download the Oracle SQL client
and JDBC driver.
Oracle database
version
(ORAVersion)
12.2 Amazon RDS Oracle version.
Oracle instance
identifier
(DBInstanceIdentifier)
FNCMORCL Oracle database instance name.
Oracle instance class
(DBInstanceClass)
db.m5.large Amazon RDS instance type for the Oracle database instance.
Oracle database name
(DBName)
P8DB Name of Oracle database.
Oracle database
administrator
(DBUser)
P8Admin Oracle database administrator name.
Oracle database
administrator
password
(DBPassword)
Requires input Oracle database administrator user password (must contain a
combination of at least 8 letters, numbers, and symbols).
High availability for
Oracle database
(DBMultiZone)
true Multiple Availability Zones for Oracle RDS. For more
information, see High Availability (Multi-AZ) for Amazon
RDS.
FileNet Content Manager configuration:
Parameter label
(name) Default Description
FileNet Content
Manager version
(FNCMVersion)
FileNet Content
Manager 5.5.4
Version of FileNet Content Manager to be deployed by this
Quick Start.
IBM entitlement key
(DockerRegistry
EntitlementKey)
Requires input IBM entitlement key to pull FileNet Content Manager Docker
images from the IBM Entitlement Registry. To obtain an
entitlement key, see IBM Container Library.
Content GraphQL
deployment
(DeployContentGraphQL)
false Deploy the optional Content Services GraphQL component.
CMIS deployment
(DeployCMIS)
false Deploy the optional CMIS component.
Amazon Web Services – IBM FileNet Content Manager on the AWS Cloud April 2020
Page 16 of 22
AWS Quick Start configuration:
Note: We recommend that you keep the default settings for the following two
parameters, unless you are customizing the Quick Start templates for your own
deployment projects. Changing the settings of these parameters will automatically
update code references to point to a new Quick Start location. For additional details,
see the AWS Quick Start Contributor’s Guide.
Parameter label
(name) Default Description
Quick Start S3 bucket
name
(QSS3BucketName)
aws-quickstart The S3 bucket name for the Quick Start assets. This string can
include numbers, lowercase letters, uppercase letters, and
hyphens (-). It cannot start or end with a hyphen (-).
Quick Start S3 key
prefix
(QSS3KeyPrefix)
quickstart-ibm-
filenet-content-
manager/
S3 key prefix for the Quick Start assets. The Quick Start key
can include numbers, lowercase letters, uppercase letters,
hyphens (-), and a forward slash (/). If you decide to customize
or extend the Quick Start for your own use, this is the S3 key
name prefix used to simulate a folder for your copy of Quick
Start assets.
5. On the Options page, you can specify tags (key value pairs) for resources in your stack
and set advanced options. When you’re done, choose Next.
6. On the Review page, review and confirm the template settings. Under Capabilities,
select the two check boxes to acknowledge that the template creates IAM resources and
that it might require the capability to auto-expand macros.
7. Choose Create to deploy the stack.
8. Monitor the status of the stack. When the status is CREATE_COMPLETE, the IBM
FileNet Content Manager cluster is ready.
9. Check the stack’s Outputs tab to view the created resources.
Amazon Web Services – IBM FileNet Content Manager on the AWS Cloud April 2020
Page 17 of 22
Figure 4: IBM FileNet Content Manager outputs after successful deployment
Step 5. Test the deployment
CHECK THE DEPLOYMENT COMPLETION STATUS
Verify the completion of the deployment scripts on the AWS Systems Manager, on the
Run Command page.
Figure 5: Deployment completion status
Amazon Web Services – IBM FileNet Content Manager on the AWS Cloud April 2020
Page 18 of 22
CREATE THE FILENET P8 COMPONENTS URLS
1. Connect to the bastion host by using SSH and your private key. The bastion host IP
address is listed on the Outputs tab.
$ ssh -i /path/to/keypair.pem ec2-user@<BastionIP>
2. Use the following kubectl command to get the name of the Content Platform Engine
load balancer:
$ kubectl get ingress/cpe-ingress -o=jsonpath='{.status.loadBalancer.ingress[0].hostname}'
Use the return value to create the Content Platform Engine URL:
https://<Content_Platform_Engine_load_balancer>/acce
3. Use the following kubectl command to get the name of the Content Navigator load
balancer:
$ kubectl get ingress/icn-ingress -o=jsonpath='{.status.loadBalancer.ingress[0].hostname}'
Use the return value to create the Content Navigator URL:
https://<Content_Navigator_load_balancer>/navigator
4. Optional: Use the following kubectl command to get the name of the Content
Services GraphQL load balancer:
$ kubectl get ingress/crs-ingress -o=jsonpath='{.status.loadBalancer.ingress[0].hostname}'
Use the return value to create the Content GraphQL URL:
https://<Content_GraphQL_load_balancer>/content-services-graphql
5. Optional: Use the following kubectl command to get the name of the CMIS load
balancer:
$ kubectl get ingress/cmis-ingress -o=jsonpath='{.status.loadBalancer.ingress[0].hostname}'
Amazon Web Services – IBM FileNet Content Manager on the AWS Cloud April 2020
Page 19 of 22
Use the return value to create the CMIS URL:
https://<CMIS_load_balancer>/openfncmis_wlp
LOG IN TO THE FILENET P8 ENVIRONMENT
To access the Content Platform Engine (Administration Console) and IBM Content
Navigator, use the URLs from the beginning of this step, and then log in with the following
credentials.
User name: P8Admin
Password: Use the DomainAdminPassword value from the Parameters section.
Best practices for using IBM FileNet Content Manager on AWS See IBM FileNet Content Manager Implementation Best Practices and Recommendations.
Security See How does IBM FileNet P8 secure its objects?
Troubleshooting Q. I encountered a CREATE_FAILED error when I launched the Quick Start.
A. If AWS CloudFormation fails to create the stack, we recommend that you relaunch the
template with Rollback on failure set to No. (This setting is under Advanced in the
AWS CloudFormation console, Options page.) With this setting, the stack’s state will be
retained, and the instance will be left running, so you can troubleshoot the issue. (For
Windows, look at the log files in %ProgramFiles%\Amazon\EC2ConfigService and
C:\cfn\log.)
Important: When you set Rollback on failure to No, you will continue to incur
AWS charges for this stack. Please make sure to delete the stack when you finish
troubleshooting.
For additional information, see Troubleshooting AWS CloudFormation on the AWS
website.
Amazon Web Services – IBM FileNet Content Manager on the AWS Cloud April 2020
Page 20 of 22
Q. I encountered a size limitation error when I deployed the AWS CloudFormation
templates.
A. We recommend that you launch the Quick Start templates from the links in this guide or
from another S3 bucket. If you deploy the templates from a local copy on your computer or
from a non-S3 location, you might encounter template size limitations when you create the
stack. For more information about AWS CloudFormation limits, see the AWS
documentation.
Send us feedback To post feedback, submit feature ideas, or report bugs, use the Issues section of the
GitHub repository for this Quick Start. If you’d like to submit code, please review the Quick
Start Contributor’s Guide.
Additional resources
AWS account
If you don’t already have an AWS account, create one at https://aws.amazon.com by
following the on-screen instructions. Part of the sign-up process involves receiving a phone
call and entering a PIN using the phone keypad.
Your AWS account is automatically signed up for all AWS services. You are charged only for
the services you use.
AWS resources
Getting Started Resource Center
AWS General Reference
AWS Glossary
AWS services
AWS CloudFormation
AWS Directory Service
Amazon EC2
Amazon EFS
Amazon EKS
IAM
Amazon Web Services – IBM FileNet Content Manager on the AWS Cloud April 2020
Page 21 of 22
Amazon VPC
IBM FileNet Content Manager documentation
IBM FileNet P8 Platform V5.5.x
Other Quick Start reference deployments
AWS Quick Start home page
Document revisions Date Change In sections
April 2020 IBM FileNet Content Manager on AWS; Step 4.
Launch the Quick Start; Step 5. Test the
deployment
IBM FileNet Content Manager
on AWS; Parameters for
deploying IBM FileNet Content
Manager into a new VPC; Check
the deployment completion
status; Create the FileNet P8
components URLs
January 2020 Initial publication —
Amazon Web Services – IBM FileNet Content Manager on the AWS Cloud April 2020
Page 22 of 22
© 2020, Amazon Web Services, Inc. or its affiliates, and IBM. All rights reserved.
Notices
This document is provided for informational purposes only. It represents AWS’s current product offerings
and practices as of the date of issue of this document, which are subject to change without notice. Customers
are responsible for making their own independent assessment of the information in this document and any
use of AWS’s products or services, each of which is provided “as is” without warranty of any kind, whether
express or implied. This document does not create any warranties, representations, contractual
commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities
and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of,
nor does it modify, any agreement between AWS and its customers.
The software included with this paper is licensed under the Apache License, Version 2.0 (the "License"). You
may not use this file except in compliance with the License. A copy of the License is located at
http://aws.amazon.com/apache2.0/ or in the "license" file accompanying this file. This code is distributed on
an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and limitations under the License.
