Posts Tagged ‘Enterprise Content Management’


We have discussed about the basics of Apache Sling in the last article. Now we will see a  quick cheat sheet on how the sling resolution takes place. Really helpful for understanding how the script for the requested content is resolved in Adobe Experience Manager (AEM).

Disclaimer: This image is actually shared from AEM website, and is not created by my own.

sling-cheatsheet

 

Advertisements

The AEM Developer Tools is a plugin for Eclipse IDE that brings you the full connection to the Adobe Experience Manager. It is based on the Eclipse plugin for Apache Sling.

Using this plugin, you can directly work with the AEM repository.

The latest version of AEM Developer Tools plugin can be downloaded at https://eclipse.adobe.com/aem/dev-tools/

More information about how to install the plugin can be found at https://docs.adobe.com/content/docs/en/dev-tools/aem-eclipse.html

Screen Shot 2016-04-14 at 7.05.31 PM


No doubt, WebCenter Sites has provided a great tool called CSExplorer in JSK for exploring the Database contents. But this tool has limitations. This works only on the Windows environments. But in reality, developers work on different environments aswell like MAC, Linux, etc.

I really felt bad when I couldn’t find someway to explore the database contents. while working on MAC. Fortunately, I have gone through some other website, and came to know how to explore the HSQLDB using eclipse.

I want to explain now how to explore the underlying tables of WCS using Eclipse, more elaborately.

Step  1 :

Open your server.xml file. It can be found under the below location:

[WCS installation Dir ]/apache-tomcat-7.0.42/Sites/conf/server.xml

Get the below values:

  • Username
  • Password
  • URL

See below screen shot.

server_xml

Step  2:    

Have your eclipse installed. You can get it from  https://www.eclipse.org/downloads/

Step  3:     

Download the Data tools platform from eclipse marketplace. To do this, go to the Eclipse market place window, and search for ECLIPSE DTP (DATA TOOLS PLATFORM) 1.11.1 KEPLER, and install the plugin.

DTP

 Step 4:     

Now open the Perspective ” Database Development“.

You can do this by going to the Eclipse -> Window -> Open Perspective -> Other – > Database Development

Step 5: 

In the left hand, you will see a new tree opened called DATA SOURCE EXPLORER.

Right click on DATA CONNECTIONS, and click on NEW.

DATASOURCE

 Step 6:    

You will now get the following CONNECTION PROFILE window. Select HSQLDB from the available list of options, and click on NEXT button:

conn-profile

 Step 7:    

Enter the DB connection details in the below window:

Enter the following values from the inputs taken in step 1.

  • Database Location  : [WCS Installation Dir ] /App_Server/apache-tomcat-7.0.42/Sites/default/data/hypersonic/csDB
  • UserName  :   sa
  • Password    : blank

Then click on the TEST CONNECTION button. It shows a PING SUCCESSFUL dialog box. Now click on FINISH button.

DB Info Screen

NOTE:  You need to add the hsqldb.jar in the above window, by clicking on the + button available against the DRIVER  drop down.

Step  8:  

That’s it. In the Data source explorer tree of left hand side, you can see a new DB connection created to your local JSK. You can explore the tables as shown in the below screenshot.

 

TABLES

 

That’s it for now.

 

 

 

 


Log Viewer Tool

This is one of the SYSTEM TOOLS. This tool enables you to view, tail, download, and search the contents of the WebCenter Sites logs directly from the WebCenter Sites administrator’s interface.

The options available in this tool are pretty simple, and can be understood upon viewing it. Hence, I’m not going to explain much about it. Below is the screenshot of the tool from Admin UI.

log

By default, it displays upto 100 lines of the log file. We can change it as per our wish upto 100o lines.

Alternatively, instead of going to this utility, we can directly use the following url to view the log file. The maximum number of lines to be displayed can be entered at the end of the url.

http://localhost:8080/cs/ContentServer?pagename=fatwire/systemtools/logs/logTailViewer&pageSize=100

Replace the localhost with your server name, and 8080 with your port number.

Bookmark this url, and this becomes handy when you need to see the WCS logs.


System Information Tool

The System Information tool provides access to various information like WCS information, database information, and thread information for troubleshooting and checking the health of your application.

We can either view information directly in the admin interface or download information to a file.

This tool consists of the following options:

  1. Sites Info
  2. DB Info
  3. Thread Info
Sites Info Node:

This node provides us the following facilities:

  1. Memory Information: This has the info about Total memory, free memory, etc.
  2. Option to download the WCS Property files like the .ini files
  3. Option to download the Webapp property files like the .properties, .xml files
  4. Info about Jar files available in Web-Inf/Lib folder
  5. Info about Session variables
  6. Info about System variables

sites information

DB Info Node:

This node provides us with the following information.

  1. Database Server Information
  2. JDBC Driver Info
  3. JDBC Driver Url
  4. JDBC Version
  5. JNDI Data Source
  6. Information about System Tables
  7. Information about Tree Tables
  8. Information about Object Tables
  9. Information about Other Tables
database info
Thread Info Node:

You can download or view thread dumps to analyze the runtime state of the application server. This can be especially useful when trying to detect problems that might result in resource starvation or thread hangs.

thread info

We will see about other tools in coming posts.


Oracle WebCenter Sites provides us with few tools that will be useful in our day-to-day activities as a developer like managing the page cache, asset cache, viewing logs, etc.

 The System Tools node on the Admin tab provides a range of diagnostic utilities that general administrators can use to troubleshoot directly from the WebCenter Sites administrator’s interface. Features include configuring log4j loggers, accessing various types of system information, managing caches, searching the contents of the WebCenter Sites log, and testing the performance of the shared file system.

One can find the SYSTEM TOOLS as follows in Oracle WebCenter Sites:

  1. Log into the Admin UI of Oracle WebCenter Sites.
  2. Go to ADMIN Tab in the tree.
  3. You will find a node called SYSTEM TOOLS at the bottom of the available nodes.

Double click on the SYSTEM TOOLS node to explore the various options provided by Oracle WebCenter Sites. Below screenshots shows the System Tools in Admin Tab.

System Tools

We will go through these system tools in upcoming posts.

Stay tuned….!


What is a Portal?

A portal is generally defined as a software platform for building websites and web applications. A portal is a web application that commonly provides personalization, single sign on, content aggregation from different sources, and hosts the presentation layer of information systems. Aggregation is the act of integrating content from different sources within a web page. Present day portals have added many features which help the editors to implement various functionalities from a single platform. The below listed various features are available in the modern day’s portals:

  • Web Content management
  • Document management
  • Digital asset management
  • Workflow management
  • Social collaboration (Communities), etc.

These features are making Portals as one of the best options to be chosen while building a web application / websites.

Portal functionality can be divided into three main parts:

  1. Portlet container: A portlet container is very similar to a servlet container. A portlet container is responsible for initializing and destroying portlets and also for passing user requests to it and collecting responses. It controls the life cycle of the portlet.
  2. Content aggregator: The main job of a portal is to aggregate content generated by various portlets.
  3. Common services:  The common services that you can find in most implementations are:
  • Single sign on: This helps us to get access to all the applications that are deployed in the Portal, once we log into the portal server
  • Personalization:This helps the user to customize his page, so that he can view the applications which he is interested.