Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Genral package/SDKs purposes?
System
LiveSite 7.1
I know the answer is it depends but there is the general intent for each.
- cssdk?
- LiveSite Toolkit? Seems like the general stuff for component development
- com.interwoven.wcm...? Seems like the LSCS specific packages
- Any others I might need to be aware of?
We have LiveSite 7.1 (We will be using LSCS and LSDS), OpenDeploy and DataDeploy, MediaBin.
We are redesigning our web site. It currently uses TeamSite but through DataDeploy all the metadata ends up normalized in a database and our web site is built off of that. The new one will be using LSCS instead of the database and LSDS instead of our current custom servlets, jsp's and so on. I just need the help of knowing the general packages/sdk's and their intent so I can focus my time on exploring/learning them.
Thanks,
Find more posts tagged with
Comments
vpatel
CSSDK: for TS side -- i.e. WF external tasks, custom menu items that need some code behind the scenes, JSPs that may be needed for the custom UI items, Java-based Call-Servers for your DCTs, etc.
Generally speaking, these types of code/customizations/configs should go under the "customer_src" toolkit.
-------------------------------------------------------------------------------------------
LS API: for LSDS side -- i.e. component externals and controllers.
LSCS API: for LSCS -- i.e. when you want to query assets out of LSCS.
Generally speaking, these types of code/customizations/configs should go under the "livesite_customer_src" toolkit.
-------------------------------------------------------------------------------------------
There are some others classes / APIs related to OD Web Services (i.e. if you want to do your deployments using OD Web Services rather than OD CLTs) but for the most part aforementioned are the big things that you want get familiar with.
HTH!