Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

The structure of the Canvas Technology release contents has been changed to pick out the related content for easier consumption. The release has been organized in the following fashion:

  • canvas – This folder contains all the binaries (JARs / ZIPs) that correspond to the base canvas framework. This folder also contains 3rd party JARs in a separate sub-folder called 'dependencies'.
  • database – This folder contains the zip file for the setup of Canvas framework, model house as well as studio across all supported database servers.
  • docs – This folder contains the generated Java doc and JS doc for the Canvas framework.
  • modelhouse – This folder contains:
    • Sample ModelHouse application created for Canvas.
    • Mobile app of the ModelHouse application for iOS and Android platforms.
    • WAR files of ModelHouse for split deployment:
      • ctmodelhouseapp.war - WAR file for ModelHouse mobile app.
      • ctmodelhouseweb.war - WAR file for ModelHouse web app.
  • studio – This folder contains:
    • Expert and Wizard mode of Canvas Studio.
  • Readme.txt – This file contains details of all the third party modules referenced by Canvas along with link to their license details.

Every folder has two reports included -

  • Checksum_Report_MD5.txt – This file contains the MD5 checksums of all the contents of the folder
  • Checksum_Report_SHA1.txt – This file contains the SHA1 checksums of all the contents of the folder

These checksums can be used for verification to ensure that the binaries have not got tampered with or corrupted during file transfer.
The folder-wise checksum for the release contents is provided in the following table:


Folder

Type

Report

     

















          canvas


MD5

MD5(CTAlertsLib.jar) = ecd20249c5eeba2cd38aa5a5ad68d8bb
MD5(CTAuditLib.jar) = feb6d24663f4f55e0164bbb4e6acb3ba
MD5(CTBaseLib.jar) = db75fcc39ff7617d73e947248fa82ab2
MD5(CTCacheLib.jar) = 14d9e546fe79f57d6875ec46d72dd45f
MD5(CTCommonLib.jar) = 185a77d9fbf01f15448ae4719cd623d0
MD5(CTDBLib.jar) = 6ae682d112f3c50570fbc56e4c89e296
MD5(CTEJBs.jar) = c5ec7ad4d517802d7d5b9d6ed94c5625
MD5(CTEntitlementLib.jar) = abcefc54c5224d0e4776e3bf843fc08e
MD5(CTEventLib.jar) = b9b37ad91ad0e94a01e7ff536b278b8e
MD5(CTExportServiceLib.jar) = 0ebf97b6d002782a369c5627576d9c09
MD5(CTFormDefinitionLib.jar) = 969e64868ba54dfaaf80652ffef5bb51
MD5(CTFull.jar) = 2fd460e1d3f6171078db10edbba8015a
MD5(CTHalLib.jar) = 9d4e4f0d1b1e45e8818d482eae710f83
MD5(CTLoggingLib.jar) = 2e6bcb60f722f5b6048d4d33e8eeb5b3
MD5(CTLoginLib.jar) = d9fffb11b65c8b3c377dd9908dafe711
MD5(CTPropertyReaderUtilLib.jar) = 334a893304ec38d76211ef377a112f9e
MD5(CTRIAFramework.zip) = 8bf36aa6c77bc117649fbbbf258b4cdc
MD5(CTReadyApps.jar) = 385466e069feaab31da7969de696bac4
MD5(CTRemoteLib.jar) = c653a59aaccf5d8a9c3d4a8c178da306
MD5(CTRenderLib.jar) = e6fe4cff5fbe8e923de08d46009e8822
MD5(CTReportingFW.jar) = 1ead2c07af2ff65f4f096b5d79b4864c
MD5(CTRequestModelerLib.jar) = ba96fd5ca365db6355c31fc0f91cb957
MD5(CTResources.jar) = bbe427790e98cacfb5fc04095e74e1b5
MD5(CTValidationLib.jar) = d4d1f1d3dde267c012b231a68e1b8eb8
MD5(CTViewDefinitionLib.jar) = 238721b13d272d385407a8416d873648
MD5(YaHPConverter.jar) = 61e4c021b6abb487b7014df40bcd36c1

SHA1

SHA1(CTAlertsLib.jar) = 705fdeb2657747124c3587f80c7d70eb4f190f45
SHA1(CTAuditLib.jar) = fc7126e785dc6dac30718162fbe78f451ab24afb
SHA1(CTBaseLib.jar) = dc7a1353746ebf79c458a3d800c2c4f7bf1f6207
SHA1(CTCacheLib.jar) = 5acb7887e23f8ed37e188579e6a851b7303d2908
SHA1(CTCommonLib.jar) = 431c459f093ee1ea767a645c191e83709bc96864
SHA1(CTDBLib.jar) = ae02d53acc9573bfe633762c5641f73de0b8cecf
SHA1(CTEJBs.jar) = 0521a61566b851eb73b34e1d59a584f074b49789
SHA1(CTEntitlementLib.jar) = d2eb0e1970f5703c0ca11f6aeee07cb3b9957339
SHA1(CTEventLib.jar) = ab43fb46b9175e2512636164e6b4f0bc13ff6c94
SHA1(CTExportServiceLib.jar) = ead7c1a20dca8b5fc7e61578f4b3cef01e7f03ab
SHA1(CTFormDefinitionLib.jar) = bdedc180e812ce85460a6e284bd01859ef7dd8bb
SHA1(CTFull.jar) = dce2b3edd95cb33d49cc05dd95d2734041696afa
SHA1(CTHalLib.jar) = 0b1f95152d33169aa50db2e704bf7e15ad06b75d
SHA1(CTLoggingLib.jar) = 0641bf91b3f5845cbe836aa995ae4c500e710db5
SHA1(CTLoginLib.jar) = 350797a011701b73a9e97806252f777d7f13a6c7
SHA1(CTPropertyReaderUtilLib.jar) = d915d4b71c76ef63ce02f86425405f438ece48f8
SHA1(CTRIAFramework.zip) = 2c17667768ad8137d184bf1369e22482a43af51d
SHA1(CTReadyApps.jar) = 7039b1e94997b8c9be0b9756aafb23952ad026be
SHA1(CTRemoteLib.jar) = fcede9dbceb3cadf823c3fb8efe2462520127bc0
SHA1(CTRenderLib.jar) = 52bc46b27ea71ad84be1f959cbb56a39b4197ff0
SHA1(CTReportingFW.jar) = e1705eba99823f9017794659ee15fc447a3cbe9d
SHA1(CTRequestModelerLib.jar) = 304b5dbbb923cde3404dfa8e2e5721debc68fb71
SHA1(CTResources.jar) = 9b389e523260de0f39597cd119f4561306434a8d
SHA1(CTValidationLib.jar) = 87b46736c36431f8f77074152d9051ea6efea904
SHA1(CTViewDefinitionLib.jar) = ad1a5802b788225249adcfff802971eedf91f7af
SHA1(YaHPConverter.jar) = 24d8a8326bb493854e875fdf7d19d340a98df280




         Database


MD5

MD5(canvasSetup_DB2.zip) = f3a8802111b2e3f2adf90d3e62a32953
MD5(canvasSetup_MSSQL.zip) = 3eac1a4046ad42e3d6d034581481573d
MD5(canvasSetup_MYSQL.zip) = 22ea20dd02f6b8c6b5b7cf4ec6f96495
MD5(canvasSetup_oracle.zip) = 087ecee6d0602f6ccba852ad982688dc

SHA1

SHA1(canvasSetup_DB2.zip) = 37741d9be8e61172be590890350596575a60600d
SHA1(canvasSetup_MSSQL.zip) = db310dbd0c07c39df59a3deb79076a9c28145270
SHA1(canvasSetup_MYSQL.zip) = fe5cef6303465e764371819dbcc3103e779cae63
SHA1(canvasSetup_oracle.zip) = 119ab8569d15517bc5428ecf0e8686b160de8ba3

             

                docs


MD5

MD5(java-doc-Intellect Digital Enterprise Platform-18.1.0.0.zip) = 668580f244fcaecdc2b977ad564da5d2
MD5(js-doc-Intellect Digital Enterprise Platform-18.1.0.0.zip) = 1b2468d7c3ee184807f535b87fd327e6

SHA1

SHA1(java-doc-Intellect Digital Enterprise Platform-18.1.0.0.zip) = 7ef5c8b2d38cbd94542438df37ec8c2d3456a69f
SHA1(js-doc-Intellect Digital Enterprise Platform-18.1.0.0.zip) = d04943fda885cc5afea68cb4975afcfaa040a5aa

       



       modelhouse


MD5

MD5(ctmodelhouse.war) = 34dfd8c79a6a3fb8ce024d322e9c0c92
MD5(ctmodelhouseapp.war) = 5bc12603b2039d981b3c25fa04540cb1
MD5(ctmodelhouseweb.war) = 1cec26df624ccbadf5e1ca019d25aa21
MD5(mobilebuilds-18.1.0.0-_R8209.zip) = 9469c6674a4b9d33c47109259ec76d92

SHA1

SHA1(ctmodelhouse.war) = 380cd61e660e01e08101e53b1abd9e742d9d0974
SHA1(ctmodelhouseapp.war) = 2f45a420c1e4875ff1691155bfef79bf1fd325ec
SHA1(ctmodelhouseweb.war) = 5674dd428fbfe5c99da4b30853ee94d98a5e74bb
SHA1(mobilebuilds-18.1.0.0-_R8209.zip) = c3a4e7aaac183a8537e886eb81e22d172f611a2c


            Studio


MD5

MD5(expertctstudio.war) = 6072e826c60643595ea3b49c8c2f6e6a
MD5(wizardctstudio.war) = 00d0d90dd28c1257887b0e39fbcbe6bf

SHA1

SHA1(expertctstudio.war) = fbfbaec0239705b9cfb7cdc905324c2603e15ae7
SHA1(wizardctstudio.war) = 715baad2398890f49e31f745a4e801256e1409eb

canvas/dependencies

All third party JARs related to Canvas Technology are stored in this folder. 

canvas/hybridAppPackager

All the necessary files for creating the hybrid mobile app are stored in this folder. 


canvas/plugins


MD5

MD5(CTLogging-Log4j-1x.jar) = cbae6624319c6cc96b43541729282c64
MD5(CTLogging-Log4j-2x.jar) = 2302cbe0276405b26b06073b08b4fdf5

SHA1

SHA1(CTLogging-Log4j-1x.jar) = 70657147b8d5377bfb96c260f9da50cf752c0a45
SHA1(CTLogging-Log4j-2x.jar) = de9b6e8a4e91b8ee58a3a812358ca49b2caa7337


This release corresponds to the following tag in SVN:

  • No labels