This article will document issues that we see when deploying the CLM software into the third-party Cloud environments such as Microsoft Azure; Amazon Web Services; and others. This article will not cover the issues from
ClearObject.
The
Server Virtualization Policy for IBM Software states:
"In response to the significant increase in Cloud and PureSystem technologies now available to its clients, IBM has established a set of virtualization environments for servers that we will support across our multi-platform product portfolio for servers. These virtualization environments consist of the operating system and the hypervisor technology. This information is intended to help clients plan their strategic deployment environments for applications and achieve the economic benefits available through server consolidation."
As you can see from the
jazz.net forum post from our Offering Manager Daniel Moul, we have stated:
Yes. CLM is supported when run in Hyper-V, which is used in the Azure environment.
Note that if using Azure you will still need to bring perpetual licenses and provide admin services.
If you would rather move to SaaS and/or have someone take care of the administrative services, you could move to and IBM cloud offering. To learn more see the following:
https://www.ibm.com/marketplace/cloud/application-lifecycle-management
https://www.ibm.com/marketplace/cloud/engineering-solutions-on-cloud/"
This statement does
not state that we support every aspect that a Cloud provider can offer. There is still a very strong expectation that you will adhere to the rest of the
Systems Requirements.
Windows restarts
If Windows patches are set to deploy automatically, you MUST shutdown the indices and CLM services, cleanly, before this is scheduled in case of the Windows patch requiring a restart.
When creating Oracle tables using the commands that are prescribed in the Knowledge Center or Interactive Installation Guide, on Amazon RDS, you may encounter the following issue(s).
"The data warehouse tables could not be created. Try the action again.ID CRJAZ1745E
CRRTC8030E The creation of the data warehouse failed.
com.ibm.team.repository.common.TeamRepositoryException: CREATE TABLESPACE VNF_IDX LOGGING DATAFILE '/rdsdbbin/oracle/VNF_IDX_1.ora' SIZE 200M AUTOEXTEND ON NEXT 50M MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO"
and
java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1 ORA-20900: RDS only supports Oracle Managed Files. Check ddl and remove any named identifiers ORA-06512: at "RDSADMIN.RDSADMIN", line 160 ORA-06512: at line 2 at
*
What is AWS RDS telling you?:
The version of Oracle in use within the AWS RDS is not your typical on-premise Oracle. Therefore there maybe issues you will need to work around which will not be documented within the IBM documentation.
Standard tablespace create in this way (which they must have already worked around:)
CREATE TABLESPACE JTS
DATAFILE 'ORACLE_BASE/oradata/CLMDB/JTS.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;
What the DW is doing:
CREATE TABLESPACE VNF_IDX
LOGGING DATAFILE c:\somepath\VNF_IDX.ora'
ALTER TABLESPACE VNF_IDX ADD
DATAFILE c:\somepath\VNF_IDX.ora'
Specifying the paths (emboldened) is the problem here. The DBA will need to work within the Oracle command's syntax to create these and allow the Managed File System to allocate the datafies.
**
Heading 2 (use sentence-style capitalization)
Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text
Heading 1
External links: