Deployment

[kjv]

Hi,

Is it necessary to Install
* Java 1.5.x
* Ant 1.6.x
* Subversion 1.3.x
* Tomcat 5.5.x and/or JBoss Portal 2.0

sepreatly for Deployment?

I cannot found any Installable for Subversion.

Please revert back to me asap.

[kevinr]

You do not need ANT or Subversion for deployment - but you will need them if you want to play with the SDK or checkout the latest HEAD code.

Thanks,

Kevin

[kjv]

Ok. Thanks for quick reply, Kevin.

Can you guide me about deployment?

Thanks.

[kjv]

Hi,

I mean to say that after uploading all the contents for Web-site, what are the procedure of deployment.  Will it work if I follow the instructions given in "http://wiki.alfresco.com/wiki/Packaging_And_Deploying_Extensions"?

Is Web-site will be viewed by user by the url or he/she has to login in Alfresco?

Reply me asap.

[kvc]

Hi,

I mean to say that after uploading all the contents for Web-site, what are the procedure of deployment.  Will it work if I follow the instructions given in "http://wiki.alfresco.com/wiki/Packaging_And_Deploying_Extensions"?

Is Web-site will be viewed by user by the url or he/she has to login in Alfresco?

Reply me asap.

For our GA release, we'll be providing a deployment utility to push finalized, approved content from Alfresco to a run-time environment.

We intend to support three deployment modes:

1.  Alfresco –> File-system (statically generated sites; no need for login)
2.  Alfresco –> Alfresco (for dynamic sites; may or may not require login depending on whether you are targeting content delivery based on an authenticated user and matching content using metadata and user profiles)
3.  Alfresco — File-system and Alfresco rep (for dynamic sites built and managed in Alfresco; JSP etc. to the file system, site content to the run-time repo)

Please let me know if further questions.


Kevin

[kjv]

I can't wait till GA Release of Alfresco.  What changes I should do to implement my requirement as above right now.

Thanks in advance.

[kjv]

Dear Kevin,



We have installed Alfresco and have logged in using the web client provided.

This is what we need to do:

- We need to create a website which has a completely different look and feel than web client

- We do not wish to use the login or create user feature of Alfresco as we have some of our own business logic that we wish to add here.

- We wish to use Alfresco's CMS features and workflows



For the above we understand that we need to design our own site and pages that will use APIs provided by Alfresco. I hope our approach is right.

Do we host these JSP pages in the same folder as tomcat\webapps\alfresco or can we create our own webapp, or do we have to Extend the functionality provided by the web client



Please let us know the approach for customizing the Alfresco solution for our requirement.



Thanks !!!

[kvc]

Dear Kevin,

We have installed Alfresco and have logged in using the web client provided.

This is what we need to do:

- We need to create a website which has a completely different look and feel than web client

- We do not wish to use the login or create user feature of Alfresco as we have some of our own business logic that we wish to add here.

- We wish to use Alfresco's CMS features and workflows

For the above we understand that we need to design our own site and pages that will use APIs provided by Alfresco. I hope our approach is right.

Do we host these JSP pages in the same folder as tomcat\webapps\alfresco or can we create our own webapp, or do we have to Extend the functionality provided by the web client

Please let us know the approach for customizing the Alfresco solution for our requirement.

Thanks !!!

To accomplish this, you will want to use the new WCM module currently available for in its Preview release and scheduled for GA this December.

The new WCM module implements a notion of sandboxed development for websites and web applications.   In the WCM module, users create a Web Project, which provides a production environment for web development.  By default, a Web Project consists of one or multiple user sandboxes and a common shared Staging sandbox.  All user sandboxes by default have a current view of all approved assets available in Staging.  Any modifications made in a user's sandbox are isolated from any other user's sandbox and can be fully previewed in the context of the entire site (ie, any number of modified, newly created, newly deleted, moved or renamed assets can be previewed against that current view of the website as seen in Staging).  Once previewed, entire change sets can be promoted to Staging, execute an optional workflow for editorial review of the change set, and then made available in Staging (and by consequence to all other users for previewing their own change sets against in the context of their own sandboxes).

Each sandbox contains your entire website - including your own custom web applications.  In the sandbox, you will develop, store, and manage your JSP pages, class files, JAR files, and more.  When previewing the site, the entire web application is virtualized … thus, two developers in two separate sandboxes can idenpendently modify and test two separate sets of changes to your web app without fear of conflict.  To manage a web app in a sandbox, simply take the entire directory structure of your web app and import (an import utility is provided with the Preview release).

You can think of a sandbox as a specialized space designed to hold the entirety of your website, provide a richer versioning model for web development, and enable promotion of entire sets changes across other sandbox to simulation a production environment (by default, this promotion is a simplistic user sandbox –> staging sandbox, though it could be anything). 

From a versioning perspective, sandboxes offer a versioning model that is a supercharged version of Subversion.  This includes support for branching, merging, snapshotting, and a new unique concept called layering.  Details of the sandboxed development model and layers can
be found on our wiki:

http://wiki.alfresco.com/wiki/Collaborative_Content_Production

http://wiki.alfresco.com/wiki/Versioned_Directories

http://wiki.alfresco.com/wiki/Transparent_Layers

Once a change set is in Staging, a website can be served directly from Staging or can be deployed (replicated) to a separate server or set of servers outside your firewall.  This is the aforementioned deployment utility, which would be triggered by a submission to Staging or a rollback of Staging (to a prior snapshot) to push assets to a file-system (your JSP pages, for example) or an Alfresco repository (XML captured by our web content forms) or both.

More details on the Preview release and overall WCM plan can also be
found on our wiki:

http://wiki.alfresco.com/wiki/New_Web_Content_Management_Plan

Please let me know if any further questions.

Kevin

[kjv]

Dear Kevin,



Thanks a lot for your reply.

We also have following doubts:



- We are looking at developing a solution where we want to use Alfresco as a content management server

- Here we are not looking for WCM (Web Content Managment) but only Content or Document Management

- I believe Alfresco server can offer this with the existing release

- As stated earlier we have tried using the web client and some Foundation Service APIs

- Our doubt is about the approach towards the solution

- We want to build a web site using JSP which will access Alfresco repository to search content

- All authentication, registration to be done outside Alfresco

- Our approach is as follows, please let us know if it is correct:



          - Design our own application using Java and JSP

          - For functionalities like search use Foundation API to get access to search and then use it accordingly

          - For all such interactions with Alfresco functionality code the functionality using Foundation Service APIs

          - Considering the above to be true, why do we need the web client that is provided

          - Also for all admin related work do we code everything using API or use the web client provided and then customize the web client

          - Our doubt is that are we forced to use frameworks such as Spring or JSF?

          - Do we have to put our JSP pages in webapps\alfresco or can we host our own webapp

          - If we put our page in webapps\alfresco then a lot of times we get alfresco login page even if we have coded the authentication in our page, I guess this is due to faces-config-navigation rules

          - Is this approach toward developing a typical CMS solution with Alfresco, right?



Thanks!!!

[kvc]

Your use case is a great one for our WCM module.

Alfresco's WCM model is built around the notion of providing a development, staging, and test environment for any custom web app you build (this can be a simply web app using JSP and not relying on the Alfresco web client / JSF / Spring). 

Alfresco's WCM module provides a set of repository and web clilent enhancements.  From the repository, we provide essential source code management for your custom-built website / web app - support for sandboxed development, change sets, file and directory versioning (including snapshotting and rollback).  In addition, we provide virtualization services - the ability to test and preview your custom web app at any stage in development - so that you can test your application code and ensure your site is functioning prior to check-in.

So, what you are doing is exactly why we designed our WCM module the way we did:  we are encouraging people to build custom dynamic website that leverage Alfresco content management services.   The Alfresco web client itself is not meant to be used as part of your run-time website - it is meant only for your developers and contributors to build, maintain, and utlimately deploy your site to your own run-time environment.

I encourage you to take a look at our WCM Preview release, and again evaluate our upcoming BETA this December.  I think you'll find that this system will make the development of your Alfresco-powered custom site much easier and more manageable.

Kevin