I am working on a CSC module of ATG. I am very new to this module and want to know how to overwrite jsp files which are already present in OOTB of CSC module.
The ATG Customer Service Center UI programming guide can be found here. It has sections on best practices for customizing CSC.
Related
i want learn the aem /cq5 so Can anyone show or give the download link for AEM / CQ5 please
AEM is a comercial product, you can have it either by working on a project that already bought Production licenses. or your employer is part of the Adobe partner program - SPP. Other way it will be either impossible or illegal :(
Though you would need a license to procure the Adobe product, there are options to learn & understand the basics:
just create an Adobe ID and download old CQ basics from here
-https://helpx.adobe.com/experience-manager/aem-previous-versions.html
if you have understood the very basics of AEM, then the runnable JAR from Apache sling - https://sling.apache.org/downloads.cgi would be very handy.
You can play around with this JAR (which comes with a built-in JCR repository where you can use the JCR API - the core of AEM)
please go ver the below before jump in to the JAR:
https://sling.apache.org/documentation.html
https://docs.adobe.com/docs/en/spec/jcr/2.0/2_Introduction.html
http://felix.apache.org/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial.html
Hopefully someone can help me, I'm new to EPiServer and have been given a data migration task. We are using the latest version 8.5. I need to migrate content from a clients home grown CMS (that luckily is in a tree like structure) to EPiServer. There doesn't seem to be a whole lot of information about this on the web - perhaps I just don't know the right thing to search for.
It looks like using the EPiServer.ServiceApi might be the route to go but again locating useful documentation is proving difficult.
I was thinking of setting up the client CMS in SQL Server and writing a simple console application to call the EPiServer.ServiceApi inserting the content. If anyone has any information on this or better still and example i would be very grateful.
Thanks,
Dan
If you are just importing content from another CMS I would write a scheduled job in EPiServer:
http://world.episerver.com/code/dannymurphy/Stoppable-Scheduled-Job-with-feedback/
That job then uses the standard IContentRepository to create content:
http://world.episerver.com/documentation/Items/Developers-Guide/EPiServer-CMS/8/Content/Persisting-IContent-instances/
That way you can run it whenever you want and have access to EPiServers complete API. Also you can see progress of the import through the job status.
In the job you can read the content as a file in any format you like or directly from the source CMS database or some xml or RSS feed perhaps.
I have moved content from PHP, Java and .NET CMS this way. In .NET you could even access the source CMS via WCF or SOAP if available.
The ServiceApi is relatively new and more focused on Commerce products and media assets rather than CMS page and block content so I wouldn't use that.
There is complete documentation below for the ServiceApi by the way, did you not find it?
http://world.episerver.com/documentation/Items/EPiServer-Service-API/
Regarding language management you can read more in the below links:
http://cjsharp.com/blog/2013/04/11/working-with-localization-and-language-branches-in-episerver-7-mvc/
http://tedgustaf.com/blog/2010/5/create-a-new-page-language-branch-programmatically-in-episerver/
Basically you have two options for multiple languages. If the content is just straight translations you should create nine different language versions (branches) of the same page. You can also have multiple sites in an EPiServer installation but that requires 9 separate licenses (and the associated costs).
I've done a lot of EpiServer content migration projects. The easiest way if it's possible is to export your current sites tree in Json and then import that into EpiServer. I've had to do it on a recent project and mixed with Json.net it's pretty easy.
If you want to go that route you can find all the code to do it here: EpiServer Content Migration With Json.Net/
Ok so i just purchased a new sugarcrm professional instance on sugarcrm and I would like to add some custom logic to my leads. I would like to add them to an external service (mailchimp) through their api. ive seen that I have to create some custom php files, but I dont know how to upload them to my instance, and how is the structure of that upload. any help would be appreciated
You should create your Hook and subsequently created the installation package to install using Module Loader. Try to follow the guidance that you find here Creating an Installable Package for a Logic Hook
As a Joomla (novice) developer, I'm concerned about why we really need modules to create our own forms. I'm definitely not an authority on the subject when it comes to Joomla but here's my issue.
I understand (through hands-on discovery) that we can create forms using two ways (without additional custom modules).
By writing the form content straight in the index.php page, then checking for submit using PHP.
By inserting the HTML content for the form as a CustomHTML article using the admin back-end. Then have a separate PHP page to do the processing and return back to a specific landing page.
First I'm not sure if the above methods are considered sane in the joomla world but I do think they're workable.
If so, why do we need to run through rough seas trying to download and install form-builder plug-ins and write code that looks pretty absurd with so many files.
The first solution you mentioned is the worst that could be done. Editing the index.php should never be done. If an update for the template is bought out and you install it, it will override your changes.
The second point you mentioned is also a bad idea. There is no point in using separate PHP pages if you're using the Joomla CMS.
Stick to Joomla standards and create a custom module (not custom HTML module) either by coding it yourself or getting started with a Module Generator.
The whole point of using a CMS is to make life easier. A Joomla site is built of of Components, Modules and Plugins.
Components are like applications such as a Forum, e-commerce system etc. Modules are like widgets such as a twitter feed, shoutbox etc.
Plugins change the behavior of something.
why do we need to run through rough seas trying to download and
install form-builder plug-in?
Trying to download and install a form builder is not difficult at all. Simple go to the Joomla Extensions Directory, go the the necessary category, click on an extension that suits your needs, download and install it and voilà.
I wanted to know how Orbeon Forms work in Liferay because the Web Forms portlet is very limited, so I visited Orbeon's website and read its documentation. Then I downloaded it and ran in a Tomcat server, I built a form with the Form Builder and then tried it with the Form Runner.
My question is, how can I export one of the forms I created with the Form Builder to include it in Liferay as a portlet for example? Is that possible? Can I export a form into a WAR for example and then deploy it into Liferay?
I know you can deploy Orbeon Forms into liferay but I only want to include a specific form, not all the application with the Form Builder, the examples etc.
Could anyone help me?
First, a clarification: if what you mean is that you just want "the form", in the sense of just the XHTML, that can't work because any form built with Orbeon Forms needs a runtime to function. If the form is created with Form Builder, that means the Form Runner runtime. Either way you will need an Orbeon Forms portlet or servlet.
The forms you create, when published, are stored into a database. By default this is the built-in eXist XML database, but you can use Oracle, MySQL, or your custom persistence layer.
In order to see forms in Liferay, you have two possibilities:
The Form Runner Liferay proxy portlet
The full Orbeon Forms portlet
I recommend you peruse these two pages for details.
How it works depends on which type of portlet you use.
If using the proxy portlet, then the portlet is very lightweight and just forwards requests to a separate webapp running the Form Runner runtime. You configure the portlet to point to a specific form.
If using the full portlet, then Form Runner runs directly as a portlet. Here the portlet will load a landing page, and you probably will want to modify that landing page to point to the forms you want your users to see.
In both cases, your published form will be found as long as Form Runner points to the right database.
In your case it seems like the proxy portlet might be your best option. Note that lots of bug fixes have taken place with the proxy portlet since 3.9, so I would recommend a nightly build. For reference here is the source of the proxy portlet.