How is product specific static content used in Cobalt?
Product specific static content is kept in a different location than Platform static content, but products still use the Platform stuff. For any given product, how are these two sets merged in deployed environments? How are they merged locally?
Tagged:
1
Best Answer
-
As you said, each product has their own folder in the StaticContent project. Beneath this folder, products have to follow a very specific directory structure to ensure that their static content is deployed correctly. At deploy time, an Ant script is invoked which merges the Platform and product static content files. A couple of tasks are performed during the merge process: - Product javascript and images are copied over into the Platform folder (collisions between products are avoided because of the strict directory structure) - Product CSS files are appended to the end of the platform CSS files and are copied back into the product file - Some JavaScript files are concatenated together into one file, depending on the entries in the Ant script. - All JavaScript and CSS files are minified. When working locally, there is a Powershell script for each product which does much of the same thing as the Ant deployment script does... This should be used for merging/deploying a product's static content locally. CM also has a developer Ant script which is meant to be used locally and can be used if preferred, however I'm not sure how many use this script locally. When deployed, the static content web application will serve up the correct product file based on the product being requested. [Here is a good document][1] describing the build/deploy process as well as what happens when a request hits the Static Content server. [1]:
http://tfsnpt.int.thomson.com/Cobalt%20Platform/Documents/On%20boarding/Modules%20(AKA%20verticals)/Static%20Content%20Module/Cobalt%20Platform%20Static%20Content.docx1
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛