How to deploy an Html content to BCC server in Oracle ATG?
I need to deploy the Html page from my Bcc, so it gets reflected in my production server. I am new to ATG, so i don't know how to start with the basic scratch work.
Things i have started as a scratch.
Created the ATG project in the Eclipse and deployed to the JBOSS.
Created the database and accessed through the Repository.
Created the versioned repository and dono how to accesses it through the BCC.
After these steps, i got struck up. Is the following steps are correct for starting the ATG as a Beginner?
please give me a good suggestion or the task to learn the ATG from scratch.
BCC out of the box don't have the capability to create web pages (don't confuse it with multisite feature). Some time ago ATG was integrated with Endeca which can create pages using Expirience Manager. Now usually you will buy a bundle ATG11 + Endeca.
You have few alternatives to that, usually paid extensions. First is using ATG Sitebuilder plugin delivered by a company called Spindrift. It extend BCC and gives you possibility to build pages from blocks.
Next paid is APF (ATG Portal Framework) from company AMG.net, it gives you possibility to manage pages and content of those pages with nice live editing tool.
Other solution is to create dedicated repository with HTML spinets and use simple ootb droplet (e.g. RepositoryLookup) to show that content.
Related
I'm using Alfresco 6 community edition in which I configured some sites, each site is associated with one tenant. (I saw last year alfresco multitenancy could be deprecated in community edition, so I chose to use sites).
But I heard it could be possible (and better) to use company home instead of sites to isolate my tenants.
I thought "Company Home" was the top level in the repository, how could I configured different company home in the same alfresco installation? I didn't found anything about this. Is it really possible? Did I miss something? Any info about this could help me.
To be complete, I connect my java application to alfresco using alfresco rest API.
The top folder in the Alfresco repository is called Company Home, although it will be referred to with the name repository in the Alfresco Share user interface. You can't have multiple companyHome in any alfresco installation.
https://docs.alfresco.com/5.1/concepts/dev-repository-concepts.html
Features not supported in a multi-tenant environment
There are some features and components that are not supported in a multi-tenant production environment. Not sure your feature occur under the below list.
Using multi-tenancy you can configure multiple, independent tenants on a single Alfresco Content Services instance. However, multi-tenancy is not supported in the following products and features:
Alfresco Desktop Sync
Alfresco Governance Services
Smart Folders
Content replication
Encrypted Content Store
Document Transformation Engine
EMC Centera Connector
Alfresco Mobile Applications (they use the default tenant and can't switch between tenants)
Alfresco Outlook Integration
Alfresco Media Management
Activiti Workflow Console
Arjun - Opentext
Adding on to Arjun's answer, you cannot have multiple roots/company home directories. You also cannot have multiple Sites folders. And, the Sites folder is flat, ie, all sites are immediate children of the Sites folder.
So, if you are trying to "roll your own" multi-tenancy, you will not be able to do so by segregating sites by parent folder per tenant.
Best to make them all private sites and just handle the segregation in your custom app.
I have a client site as a published dnn website hosted on a local server in the organization's premises.
I have developed a new module using the source code that fetches data using a stored procedure.
This is what I did to transfer the changes to the live site
1. I created the stored procedure manually on the live sites DB,
2. I published the site and replaced the content of the website folder with my published site.
3. I added the new module in the live site using the "Module Definitions" option found under the "Host" menu
Everything works perfect in the development environment, but When I publish the site and do the update on the live server , the module returns no data as expected.
Can someone guide me through how to moves the stored procedure and my new published site to the live site.
I would recommend creating your module as an installable zip file including SQL for creating the stored prods and any other db changes required.
There are a number of tutorials around that will help with this and the templates build by Charles Nurse are a great help in getting your head around good practice. (http://www.charlesnurse.com)
In the mean time have you checked the permissions on the SP in the live database. That may well be your issue.
James
This is a project I've been working on off and on for months and I feel like I'm pretty close, but I just can't seem to get past the final hurdle.
The goal is to develop an organization extension library that contains both internal and 3rd party code that we frequently rely on.
History
As a test project, I started with Apache Poi because that is already in wide use in our environment. I have a plug-in and feature built just from the Poi .jars that allows me to build our current Poi applications as long as I add the plug-in (from my workspace) to my build path. The apps work on the servers because we have already distributed the Poi .jars by manually copying them.
The next step is taking that plug-in and getting it into an updatesite so that all of the servers and developers can synchronize on one version. I found and followed these two excellent blog articles (that I wish existed when I started this project):
http://www.dalsgaard-data.eu/blog/wrap-an-existing-jar-file-into-a-plug-in/
http://www.dalsgaard-data.eu/blog/deploy-an-eclipse-update-site-to-ibm-domino-and-ibm-domino-designer/
With the caveat that the articles are written for Domino 9 and we are running 8.5.3 here, but that only matters in the last (installation) step.
Current
This brings us to the problem. All of the above seems to have worked great up to a point. I can install my feature to my designer client from the eclipse update site and it works great. However, the install is failing when I import that into our updatesite.nsf database. This means that while the developers can all install from the updatesite if I put it on a network drive, that doesn't deploy updates to our servers.
The problem is that when I try to install from the .nsf update site, the Eclipse Updater just hangs. I've let it go for well over an hour and eventually Notes becomes completely unresponsive.
So the question is, is there anything I might have done wrong, either in the development of the plug-in or server configuration that might be causing this issue?
Additional Info
I'm looking at the osgi console and that is largely unhelpful. I am getting the following errors as I'm trying to install: SEVERE Could not access digest on the site: no protocol: 0/5B004DDD5E38F3FF85257CAF004C72C7/$file/digest.zip ::class.method=unknown ::thread=Worker-7 ::loggername=org.eclipse.update.core
I could generate dumps if that would be useful.
Security is also locked down fairly tight here. It could be a security issue - is there a way to troubleshoot that? Once I get to the hang I'm just stuck guessing.
This has been edited for clarity and to update information
I know that this is post is over 5 years ago but...
for those that find this and are trying to resolve the error
SEVERE Could not access digest on the site: no protocol: "
is due to the update site project not having the URL of the Domino updatesite.nsf not being added to the Archives tab of the site.xml.
I found the updatesite.nsf also needs to be anonymously accessible as no credentials are prompted/passed through to the Domino server hosting the updatesite.nsf database (at least from DDE), YMMV from eclipse. So if Anonymous connections are blocked on the Domino server you will be out of luck.
To develop a plug-in you really want to have 3 projects:
the plug-in
the feature
the update site
Of course a feature can contain more than one plug-in (and probably should) and a update site can contain more than one feature (and probably should). Once you have an update site project it features a handy button "build all" that makes sure plug-in, feature and update-site get compiled in one go. And that button is what you really want.
You can point using a setting in your Domino Designer (or local Domino server) to the feature directory. Add a plain text .link file to framework/rcp/eclipse/links, that contains the path to your install site - it then picks up the features and plug-ins from there. After a build you would need to restart designer/server to activate the updated feature.
For the Domino server the approach using an updatesite.nsf and the respective notes.ini setting makes the most sense (to me). http restart required. Lazy people script the whole thing.
I still don't have a great answer for this, but I believe the issue is related to the environment here. I don't have the authority to change the environment, even if I were able to conclusively demonstrate it is the cause of this problem, so it is a moot point. All I can say is that at least one administrator computer had no issue installing from the update site.
For me, the solution for distributing the update site is to put it on a network drive and have everyone install it from there. The server has no problem using it from the updatesite.nsf.
I've recently started to develop some sites using orchard, which is great so far, however I'm a bit confused about how to set up my deployment environments properly.
Normally I would set up local dev site, test, staging and live. using web.config transforms to alter connection strings and other app settings
I've recently been using AppHarbor for hosting and I think they are brillant.
There's a guid to setting up Orchard on AppHarbor here
Although I have to agree with comment here about all the post I've read expecting me to want to use and love Web Matrix!
Although most development in Orchard, will be done by creating modules. I think for at least one site they will want at least staging and live environments.
Whats the best way to set up and migrate from one environment to the next?
I've looked at the multi tenancy project, but that seem to address a different issue
I'd be interested to know what other have done. As well as any recommendations for modular Orchard development and in house source control - for those modules only.
I use the import-export module for exporting and importing content in my DTAP environments. Make sure to implement/override Importing and Exporting in your drivers (see: Custom part properties missing in export Orchard 1.6 /plug ;) )
Widgets however should be done manually AFAIK. They don't export and import well with that module.
As for modules and themes: just copy the folder. Same goes for media.
Where I work, we release bug fixes in to the system every night when we know our clients are not using the system.
Trying to take a step towards better service I'd like to deploy to IIS while the application is running.
A solution that comes to mind is to setup two different IIS applications and switch them over after deploy using a script. But I'm not going to try this out as I don't want any complications during our busy hours.
Does anyone have experience in this area of deployment?
Thanks
Regardless of whether you're using PHP, ASP, ASP.NET etc there is no native support for transactional deployment on IIS.
The simplest approach would be to have two physical folders and (optionally two web sites - one production, one test) on your web server, for example:
c:\websites\myapp\dep1
c:\websites\myapp\dep2
Initially your site would have its physical path pointing to c:\websites\myapp\dep1.
When you deploy your latest build you'd deploy into c:\websites\myapp\dep2. Once you're done just switch the physical path of the production site over to this folder. This means you still have the original site and can fall back to it if the new code fails for whatever reason.
The next time you do a deployment you'd deploy into c:\websites\myapp\dep1 and once you're done switch the production site to that folder.
You could optionally have a test site that points to the folder you're deploying to so you can make sure the site works before switching your production site over.
This could all be scripted.
Here's some related reading that may be of interest:
Publishing/uploading new DLL to IIS: website goes down whilst uploading
Is smooth deployment possible with componentized ASP.NET MVC apps?
Rob Conery also had an excellent blog post about the lack of a decent deployment story for ASP.NET application. You should take a trawl through the comments some of which are quite insightful:
ASP.NET Deployment Needs To Be Fixed
Getting Constructive On ASP.NET Deployment