Reload cockpit xml configurations

When you make change on product cockpit list, editor, advanced search, base, etc you need to reload configuration xml files to system. Below BeanShell code do this.

import de.hybris.platform.core.initialization.SystemSetupContext;
import de.hybris.platform.core.initialization.SystemSetup;
import de.hybris.platform.core.Registry;
SystemSetupContext setupCtx = new SystemSetupContext(new HashMap(), SystemSetup.Type.PROJECT, "mycustomcockpits");

Registry.getApplicationContext().getBean("cockpitImportConfig").importCockpitConfig(setupCtx);

Log SQL queries which are created with flex

You can add below properties to your local.properties file.

log4j2.config.xml=
log4j2.logger.flexible-search.name = de.hybris.platform.jalo.flexiblesearch
log4j2.logger.flexible-search.level = debug
log4j2.logger.flexible-search.appenderRef.stdout.ref = STDOUT

After configuration you can manage log level in hac.

Adding isempty and in for enum operator for productcockpit

Below configuration adding isEmpty operator for REFERENCE type and in operator for ENUM.

<bean id="editorConditionConfiguration" parent="myCockpitEditorConditionConfiguration" scope="tenant"/>

<bean id="myCockpitEditorConditionConfiguration" parent="defaultEditorConditionConfiguration" scope="tenant"
      class="de.hybris.platform.cockpit.model.advancedsearch.config.impl.DefaultEditorConditionConfiguration" abstract="true">
    <property name="defaultConditionsMap">
        <map merge="true">
            <entry key="REFERENCE" value="isEmpty"/>
            <entry key="ENUM" value="in"/>
        </map>
    </property>
</bean>

<bean class="de.hybris.platform.cockpit.services.search.impl.ConditionTranslatorRegistry.ConditionTranslatorMapping">
    <property name="attributeTypes">
        <set>
            <value>REFERENCE</value>
        </set>
    </property>
    <property name="operatorQualifiers">
        <set>
            <value>isEmpty</value>
        </set>
    </property>
    <property name="translator" ref="genericQueryConditionTranslator"/>
</bean>

<bean class="de.hybris.platform.cockpit.services.search.impl.ConditionTranslatorRegistry.ConditionTranslatorMapping">
    <property name="attributeTypes">
        <set>
            <value>ENUM</value>
        </set>
    </property>
    <property name="operatorQualifiers">
        <set>
            <value>in</value>
        </set>
    </property>
    <property name="translator" ref="genericQueryConditionTranslator"/>
</bean>

You need to add this operator to your referenced property with below code in your advanced search configuration (advancedSearch_VariantProduct.xml).

<property qualifier="product.galleryImages" visible="false">
	<conditions mode="append">
		<condition operator="isEmpty"></condition>
	</conditions>
</property>

Known hybris services

Service Bean Module Description
TimeService defaultTimeService core Get time information from system with timeoffset configuration.
InventoryEventService defaultInventoryEventService warehouse
GuidKeyGenerator guidKeyGenerator  Guid generator
CronJobService cronJobService  Cron job operations
DefaultConfigurationService defaultConfigurationService Configuration service
DefaultCartService Cart operations
DefaultCommerceSaveCartService Manage multiple cart, check configuration for it.
DefaultRuleEngineCalculationService
defaultRuleEngineCalculationService
Rule Engine Calculation Service

 

Getting external IP with groovy

URL url = new URL("http://mkysoft.com/ip.php");
HttpURLConnection connection = (HttpURLConnection) url.openConnection();
InputStream is = connection.getInputStream();
return org.apache.commons.io.IOUtils.toString(is);

Update all items with impex

We canuse bactcmode for updating all items by type

UPDATE Product[batchmode=true];itemType(code)[unique=true];description[en][default='test']
;Product;
;VariantProduct;

Copy schema to another in Hana DB

You can get workfolder at backup console. Get destination folder and change backup as work for example.

export "SOURCESCHEMA"."*" as binary into '/workfolder' with replace threads 10;
import "SOURCESCHEMA"."*" as binary from '/workfolder' with rename schema "SOURCESCHEMA" to "TARGETSCHEMA";

If you get privilege error like “SAP DBTech JDBC: [258]: insufficient privilege: Not authorized”, edit your user at Security menu and add EXPORT/IMPORT System Privileges.