1、安装许可(Installing Licenses)
The hybris Commerce Suite uses a license file which holds information about unlocked functionality in the hybris Commerce Suite. For example, you may or may not be allowed to use Cluster - Technical Guidefunctionality.
license文件当hybris Server启动的时候,被放在${HYBRIS_CONFIG_DIR}/licence这个目录下,我们没有必要明确的去安装这个licenses文件,我们只需要把这个licenses文件放到${HYBRIS_CONFIG_DIR}/licence这个目录下,然后重启hybris Server,就能自动的安装这个Licenses了。
每一个配置模板文件(Configuration Templates)就包含了一个licenses文件的,在配置模板文件被配置到服务器中的时候,licenses会被自动的拷贝到${HYBRIS_CONFIG_DIR}/licence这个目录下, This means that you will have a license file available right away.
当然,我们也可以手动的安装不同的licenses文件。
Manually Install a Different License
- Extract the license zip archive (
hybris20licenceQ205.zip
, for example). - Copy the
hybrislicence.jar
file to the${HYBRIS_CONFIG_DIR}/licence
directory. - Stop the hybris Server.
- Start the hybris Server:
2、环境变量:
The hybris Commerce Suite uses a number of environment variables that are defined to reference the paths of its various components.
Default Values of Environment Variables
The table below summarizes the hybris environment variables.
Variable Name |
Description |
Factory Default |
---|---|---|
HYBRIS_BIN_DIR | Points to the /bin directory of the hybris Commerce Suite, in which the platform and all extensions are located.
|
hybris/bin |
HYBRIS_CONFIG_DIR | Points to the /config directory of the hybris Commerce Suite, where custom configuration files are stored.
|
hybris/config |
HYBRIS_DATA_DIR | Points to the /data directory of the hybris Commerce Suite, where runtime data is stored.
|
hybris/data |
HYBRIS_LOG_DIR | Points to the /log directory of the hybris Commerce Suite, containing log files from the hybris Server, JDBC logging, etc.
|
hybris/log |
HYBRIS_TEMP_DIR | Points to the /temp directory of the hybris Commerce Suite, where temporary files are stored.
|
hybris/temp/hybris |
在默认情况下,这些目录都是在 platform
这个目录往上推两层目录,然后加上自己对应的子目录,比如:一个环境的platform目录是:C:\hybris\bin\platform,那么HYBRIS_LOG_DIR
就是C:\hybris\log\.....
关于如何修改环境变量,比较简单,直接参考官方文档:https://wiki.hybris.com/display/release5/hybris+Environment+Variables
3、配置模板(Configuration Templates)
The hybris Commerce Suite comes with pre-defined configuration sets ready to use as configuration templates. A configuration template consists of a set of configuration files pre-optimized by hybris for a certain aspect of running the hybris Commerce Suite, such as for use in development and production environment.
官方提供了两个配置模板:开发 和 生产(当然是开发注重的性能、debug等信息;而生产肯定注重的是安全)
Configuration Template Structure(配置模板的结构)
A configuration template can consist of the following:
- A
local.properties
file - Configuration files for the Apache Tomcat, such as
wrapper.conf
orwrapper-debug.conf
- A license file(第一小节所说的证书)
在使用ant构建服务器的时候,会要求你选择developer模式还是product模式,默认是develop模式,当然你也可以建立多个HYBRIS_CONFIG_DIR
手工的切换使用,以到达不同的需求,可参考:https://wiki.hybris.com/display/release5/Configuration+Templates
4、目录结构:
All extensions developed by hybris are grouped in specific directories under the /bin
directory to distinguish between the different kinds of extensions that hybris offers. Additionally, distinguishing the /bin
directory from the other directories is beneficial for both partner developers and system administrators when updating the hybris Commerce Suite.
每一个ext目录都是一个可以被eclipse打开的项目,可以完成特定的功能。
hybris把bin目录和其他的目录分开,其他的目录包括数据啦、日志啦、配置模板啦、、、等等。这样一个显著的好处就是bin目录只有固定的代码,不会有任何改变,若你升级hybris,直接替换这个bin目录就行了,别的客户化的东西,都不用管的。
Directory Structure Overview
Directory |
Description |
Environment Variable |
---|---|---|
/bin
|
Contains the hybris Platform directories, the template directory, and the hybris extensions directory. It may also contain the directory for partner extensions or custom extensions made by customers for their own use. | ${HYBRIS_BIN_DIR} |
|
This directory is created during the process of creating the custom extensions. It should contain your own project extensions. For details about creating extensions see the Creating a New Extension document. | |
|
This directory contains acceleratorcms, acceleratorfacades, acceleratorservices, b2bacceleratorfacades, b2bacceleratorservice .
|
|
|
This directory contains addon extensions. | |
|
This directory contains cscockpit, instore, mobileoptionals,mobileservices,print,printcockpit,printhmc .
|
|
|
This directory contains commerce-related extensions. | |
|
This directory contains bmecat, classificationsystems,cms2,cmscockpit,importcockpit,mam, productcockpit .
|
|
|
This directory contains sample data extensions. | |
|
This directory contains admincockpit, backoffice, cockpit, hmc, mcc, platformhmc extensions.
|
${HYBRIS_EXT-PLATFORM_DIR} |
|
This directory contains optional platform extensions. | ${HYBRIS_EXT-PLATFORM_DIR} |
|
This directory contains print, printcockpit and printhmc extensions |
${HYBRIS_EXT-PRINT} |
|
This directory contains all extgen templates.
|
${HYBRIS_EXT-TEMPLATE_DIR} |
|
This directory contains the actual hybris Platform functionalities. It includes core extensions, the build framework, custom extension templates in /extgen , and the application server directories.
|
${HYBRIS_PLATFORM_DIR} |
/config
|
The directory contains your custom configuration files for the hybris Commerce Suite, such as: local.properties ,localextensions.xml , andhybrislicence.jar . This directory also contains the files for the customization mechanism of the hybris Commerce Suite.
|
${HYBRIS_CONFIG_DIR} |
/data
|
This directory contains runtime data, such as:
|
${HYBRIS_DATA_DIR} |
/log
|
This directory contains log files from the hybris Server, JDBC logging, and so on. | ${HYBRIS_LOG_DIR} |
/temp
|
This directory contains temporary files. | ${HYBRIS_TEMP_DIR} |