Monday, May 28, 2012
Thursday, May 17, 2012
Nagios opensource monitoring tool
Nagios is a popular open source computer system monitor, network monitoring and infrastructure monitoring software application. Nagios offers complete monitoring and alerting for servers, switches, applications, and services and is considered[by whom?] as the defacto industry standard in IT infrastructure monitoring. It watches hosts and services, alerting users when things go wrong and again when they get better.
Tuesday, May 15, 2012
Mule ESB
The tutorial can be found in the location
http://blogs.mulesoft.org/getting-started-with-mule-free-training-videos-tutorials/
http://www.mulesoft.org/documentation/display/MULE3EXAMPLES/Error+Handler+Example
http://oss.org.cn/ossdocs/soa/mule/1.3/Mule%20Examples%20Webapp.html
http://oss.org.cn/ossdocs/soa/mule/1.3/Examples.html
http://mvnrepository.com/artifact/org.mule.examples
http://blogs.mulesoft.org/getting-started-with-mule-free-training-videos-tutorials/
http://www.mulesoft.org/documentation/display/MULE3EXAMPLES/Error+Handler+Example
http://oss.org.cn/ossdocs/soa/mule/1.3/Mule%20Examples%20Webapp.html
http://oss.org.cn/ossdocs/soa/mule/1.3/Examples.html
http://mvnrepository.com/artifact/org.mule.examples
Monday, May 14, 2012
Latest Technologies
EIP : Enterprise Integration pattern
ESB : Mule, ServiceMix , Camel , ActiveMQ(JMS tool)
Mule, ServiceMix , Camel
http://www.liferay.com/community/wiki/-/wiki/Main/Liferay+ESB+Support+-+ServiceMix+and+Mule
http://www.scribd.com/doc/16762906/Liferay-Portal-With-Mule-ESB
Spring Roo
Appfuse
Above are the development stratergies
ESB : Mule, ServiceMix , Camel , ActiveMQ(JMS tool)
Mule, ServiceMix , Camel
http://www.liferay.com/community/wiki/-/wiki/Main/Liferay+ESB+Support+-+ServiceMix+and+Mule
http://www.scribd.com/doc/16762906/Liferay-Portal-With-Mule-ESB
Spring Roo
Appfuse
Above are the development stratergies
Liferay ESB Integration
http://www.scribd.com/doc/16762906/Liferay-Portal-With-Mule-ESB
http://www.liferay.com/community/wiki/-/wiki/Main/Liferay+ESB+Support+-+ServiceMix+and+Mule
By default, Liferay uses JBoss' jBPM engine for its workflow component. Both ESBs' XMLs are preconfigured to call the jbpm-web webapp to process data submitted from the "Workflow" portlet. By default, the portal is configured to use ServiceMix for the workflow component, but this can be overridden in portal.properties:
http://www.liferay.com/community/wiki/-/wiki/Main/Liferay+ESB+Support+-+ServiceMix+and+Mule
By default, Liferay uses JBoss' jBPM engine for its workflow component. Both ESBs' XMLs are preconfigured to call the jbpm-web webapp to process data submitted from the "Workflow" portlet. By default, the portal is configured to use ServiceMix for the workflow component, but this can be overridden in portal.properties:
#jbi.workflow.url=http://localhost:8080/servicemix-web/workflow jbi.workflow.url=http://localhost:8080/mule-web/workflow
By this property Liferay is integrated with ESB for the workflow implementation.
Monday, May 7, 2012
Thursday, May 3, 2012
performance
http://www.anotherstrangerme.com/alfresco-lucene-index-gone-bad-and-storage-considerations/
http://blog.alfrescian.com/?p=146
http://blog.alfrescian.com/?p=146
Lucene index check
With the below url we can do index check
http://localhost:8080/alfresco/service/enterprise/admin/indexcheck
http://localhost:8080/alfresco/service/enterprise/admin/indexcheck
Wednesday, May 2, 2012
Ehcache settings Alfresco
http://wiki.alfresco.com/wiki/Repository_Cache_Configuration#Overriding_the_EHCache_Defaults
org.alfresco.repo.cache.EhCacheTracerJob
increasing l2 cache
low hit ratios to be fine tuned
http://docs.alfresco.com/4.0/index.jsp?topic=%2Fcom.alfresco.enterprise.doc%2Fconcepts%2Fcache-memorysettings.html
http://docs.alfresco.com/4.0/index.jsp?topic=%2Fcom.alfresco.enterprise.doc%2Fconcepts%2Fcache-indsettings.html
http://docs.alfresco.com/4.0/index.jsp?topic=%2Fcom.alfresco.enterprise.doc%2Ftasks%2Fcaches-trace.html
Each cache is configured in an XML block with the following parameters:
name
The name attribute is the name of the cache and generally indicates the type of objects being cached.
maxElementsInMemory
The maxElementsInMemory controls the maximum size of the cache. This value can be changed to tune the size of the cache for your system. Ehcache caches are implemented using a linked-map system, which means that memory is only required for objects that are actually in memory. If you set the maxElementsInMemory to a high value, it will not automatically allocate that number of slots. Instead, they are added to the linked list as required. When maxElementsInMemory is reached, the cache discards the oldest objects before adding new objects.
timeToIdleSeconds - timeToLiveSeconds
timeToIdleSeconds and timeToLiveSeconds control the automatic timeout of cached objects.
overflowToDisk
overflowToDisk controls whether the cache should overflow to disk rather than discarding old objects.
A typical trace is as follows:
The criteria are:
(MissCount - CurrentCount) must be as low as possible.
(HitCount/MissCount) must be as high as possible.
Estimated maximum size affects the permanent memory taken up by the cache. If the caches grow too large, they may crowd out transient session memory and slow down the system. It is useful to have this running, on occasion, to identify the caches with a low HitCount/MissCount ratio.
org.alfresco.repo.cache.EhCacheTracerJob
increasing l2 cache
low hit ratios to be fine tuned
http://docs.alfresco.com/4.0/index.jsp?topic=%2Fcom.alfresco.enterprise.doc%2Fconcepts%2Fcache-memorysettings.html
http://docs.alfresco.com/4.0/index.jsp?topic=%2Fcom.alfresco.enterprise.doc%2Fconcepts%2Fcache-indsettings.html
http://docs.alfresco.com/4.0/index.jsp?topic=%2Fcom.alfresco.enterprise.doc%2Ftasks%2Fcaches-trace.html
Each cache is configured in an XML block with the following parameters:
name
The name attribute is the name of the cache and generally indicates the type of objects being cached.
maxElementsInMemory
The maxElementsInMemory controls the maximum size of the cache. This value can be changed to tune the size of the cache for your system. Ehcache caches are implemented using a linked-map system, which means that memory is only required for objects that are actually in memory. If you set the maxElementsInMemory to a high value, it will not automatically allocate that number of slots. Instead, they are added to the linked list as required. When maxElementsInMemory is reached, the cache discards the oldest objects before adding new objects.
timeToIdleSeconds - timeToLiveSeconds
timeToIdleSeconds and timeToLiveSeconds control the automatic timeout of cached objects.
overflowToDisk
overflowToDisk controls whether the cache should overflow to disk rather than discarding old objects.
A typical trace is as follows:
The criteria are:
(MissCount - CurrentCount) must be as low as possible.
(HitCount/MissCount) must be as high as possible.
Estimated maximum size affects the permanent memory taken up by the cache. If the caches grow too large, they may crowd out transient session memory and slow down the system. It is useful to have this running, on occasion, to identify the caches with a low HitCount/MissCount ratio.
Subscribe to:
Posts (Atom)