This document outlines the code base structure and delivery package for CIM's logical code. It includes:
1. The main folders for the data model, ETLs, GUI, and BO code.
2. Details on the check-in folder structures for the data model, ETLs, and GUI code.
3. Additional information on using existing folders for delivery and noting to add new folders/files to source control.
This document outlines the code base structure and delivery package for CIM's logical code. It includes:
1. The main folders for the data model, ETLs, GUI, and BO code.
2. Details on the check-in folder structures for the data model, ETLs, and GUI code.
3. Additional information on using existing folders for delivery and noting to add new folders/files to source control.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online from Scribd
This document outlines the code base structure and delivery package for CIM's logical code. It includes:
1. The main folders for the data model, ETLs, GUI, and BO code.
2. Details on the check-in folder structures for the data model, ETLs, and GUI code.
3. Additional information on using existing folders for delivery and noting to add new folders/files to source control.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online from Scribd
CIMs Logical Code Base Structure & Delivery Package
Installation Configuration Maintenance Code Base CXC_CIM_SYSTEM
DataModel
CXC_CIM_MODEL MartETL
WebGui (.war/.ear) CXC_CIM_GUI Boxi (.biar)
OSS
Data Model Check-in Folder Structure
1. Create a separate folder for individual schema under the highlighted directories 2. Under Model folder create individual files for constraints, indexes, sequences, table definitions 3. Under data folder create the SQL statements for pre-configuration data into specific tables in dat files and the sql statement to call the dat files. /vobs/charging/CIM1/storage/ |-- data |-- model |-- rollback |-- tablespaces | |-- tablespaces.xml |-- upgrade cimadm |-- accounts.dat |-- cimadm.sql
1. Create a separate folder for individual schema under the highlighted directories 2. Under db folder create individual folders for views, triggers /vobs/charging/CIM1/mart_etl/ |-- src |-- db |-- packages views |-- cimadm |-- ddsaccounts.vw
cimbi |-- dds_revenue.spec |-- dds_revenue.bdy
BO Check-in Folder Structure
Create a BIAR file and check in the below mentioned folder /vobs/charging/CIM1/boxi/
GUI Folder Structure
1.The /vobs/charging/CIM1/cim2_code/ is already well-defined by the development team. 2.The build package under the below folder will be used for the delivery /vobs/charging/CIM1/cim2_code/pkg-gui/cim.build/I.Cim 3.The ECCD-I and ECCD-II activity flows are to be checked-in under the below folder structure /vobs/charging/CIM1/cim2_code/pkg-server/src/flowconfig 4.Also deliverables for running the flows on the server will be used from the below folder /vobs/charging/CIM1/cim2_code/pkg-server/dist/deliverables
Some More info.
1. If required create additional folders under /vobs/charging/CIM1/ and mail us regarding the same to include the same for the build 2. Dont forget to do Add to Source Control while checking-in any new folder or new file 3.Upgrade/Rollback is not covered as this is the First CIM delivery. 4.The folder structure in a CIM installed machine would be as below, /opt/cim/
lib contains jars and other dependencies
etc contains configuration files bin contains binaries to run the application modules contains the copy of the installed CIM packages *will subject to change as we progress.
Installation and Configuration of IBM FileNet Information Management Software: A step-by-step guide to installing and configuring IBM FileNet ECM and Case Manager on RHEL 8.0 (English Edition)