Category: How To

I recently ran out of storage space on my development server that has both Hybris and Adobe Experience Manager (AEM) installed. A quick df -h command confirmed my suspicion: Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_system-opt 7.0G 7.0G 20K 100% /opt After installing a new disk. the operating system identified this new disk as /dev/sdb.  Since this is a brand new disk, no partitions exist. The following are the steps required to add additional space to a Red Hat Enterprise Linux Server Volume Group. 1. Convert this new disk into a physical volume: # pvcreate /dev/sdb Physical volume "/dev/sdb" successfully created 2. …

Is your company struggling with Hybris Commerce installations and deployments for your development, testing, and production environments? This step-by-step tutorial will show you how to automate your Hybris Commerce installations, which will: Save your company time and money Eliminate installation and deployment mistakes Establish a consistent Hybris deployment process In more technical terms, this article will demonstrate how to automate the installation of SAP Hybris 6.3 and its requisite software dependencies for Linux CentOS 7 with a Vagrant Up command. The information learned in this tutorial should provide a useful framework for Hybris installations and deployments. This tutorial will work on both …

This tutorial demonstrates the configuration details for a two node, load-balanced Hybris cluster using Apache Web Server.   Steps Step 1 Configure Node1's local.properties file to resemble the following: yacceleratorstorefront.webroot= storefrontContextRoot= #Cluster clustermode=true cluster.id=1 cluster.maxid=2 cluster.broadcast.methods=jgroups cluster.broadcast.method.jgroups=de.hybris.platform.cluster.jgroups.JGroupsBroadcastMethod cluster.broadcast.method.jgroups.tcp.bind_addr=127.0.0.1 cluster.broadcast.method.jgroups.tcp.bind_port=7800 cluster.broadcast.method.jgroups.channel.name=hybris-broadcast cluster.broadcast.method.jgroups.configuration=jgroups-tcp.xml cluster.broadcast.method.udp.multicastaddress=230.0.0.1 cluster.broadcast.method.udp.port=9997 log4j.logger.de.hybris.platform.cluster.PingBroadcastHandler=DEBUG log4j.logger.de.hybris.platform.cluster.udp.UnicastBroadcastMethod=DEBUG   Step 2 Configure Node2's local.properties file to resemble the following: yacceleratorstorefront.webroot= storefrontContextRoot=   #Cluster clustermode=true cluster.id=2 cluster.maxid=2 cluster.broadcast.methods=jgroups cluster.broadcast.method.jgroups=de.hybris.platform.cluster.jgroups.JGroupsBroadcastMethod cluster.broadcast.method.jgroups.tcp.bind_addr=127.0.0.1 cluster.broadcast.method.jgroups.tcp.bind_port=7800 cluster.broadcast.method.jgroups.channel.name=hybris-broadcast cluster.broadcast.method.jgroups.configuration=jgroups-tcp.xml cluster.broadcast.method.udp.multicastaddress=230.0.0.1 cluster.broadcast.method.udp.port=9997 log4j.logger.de.hybris.platform.cluster.PingBroadcastHandler=DEBUG log4j.logger.de.hybris.platform.cluster.udp.UnicastBroadcastMethod=DEBUG tomcat.http.port=10001 tomcat.ssl.port=10002 tomcat.ajp.port=10009 tomcat.ajp.ssl.port=10010 tomcat.jmx.port=10003 tomcat.jmx.server.port=10004   Step 3 Edit the Apache Web Server httpd.conf file to include the following: Header add Set-Cookie: "ROUTEID=.%{BALANCER_WORKER_ROUTE}e; path=/" env=BALANCER_ROUTE_CHANGED   <Proxy balancer://mycluster> …

SELECT c.p_nodeid, count(*) as job_count FROM cronjobs c inner join jobs j on c.p_job = j.pk group by c.p_nodeid order by 1;