Endeca Stemming Issue

I am having issues with Stemming in my application when I run baseline_update on Windows box. It would be a big help to this newbie if you Endeca gurus help me resolve this. In my simple pipeline, I have just default properties and dimensions, nothing created by me. I had default Stemming selected for English that I played around to add more languages after I had this problem. Currently I have four languages selected - Chinese simplified, Chinese traditional, English and Spanish. I don't have the file - C:\Endeca\Apps\MyApp\data\dgraphs\Dgraph1\dgraph_input/MyApp-aspell.spelldat in the location as pointed in the Dgraph log. Wondering if I need to create this? How?
Here is what I see in my command prompt and the log file:
baseline_update error:
[08.12.13 21:20:37] INFO: [MDEXHost] Starting backup utility 'backup_log_dir_for_component_Dgraph1'.
[08.12.13 21:20:38] INFO: [MDEXHost] Starting component 'Dgraph1'.
[08.12.13 21:20:57] SEVERE: Server component 'Dgraph1' failed to start. Refer to component logs in C:\Endeca\Apps\MyApp\config\script\..\..\.\logs\dgraphs\Dgraph1 on host MDEXHost.
Occurred while executing line 5 of valid BeanShell script:
2|
3|    DgraphCluster.cleanDirs();
4|    DgraphCluster.copyIndexToDgraphServers();
5|    DgraphCluster.applyIndex();
6|
7|
[08.12.13 21:20:57] SEVERE: Error executing valid BeanShell script.
Occurred while executing line 35 of valid BeanShell script:
32|        Dgidx.run();
33|
34|        // distributed index, update Dgraphs
35|        DistributeIndexAndApply.run();
36|
37|        // if Web Studio is integrated, update Web Studio with latest
38|        // dimension values
[08.12.13 21:20:57] SEVERE: Caught an exception while invoking method 'run' on object 'BaselineUpdate'. Releasing locks.
Caused by java.lang.reflect.InvocationTargetException sun.reflect.NativeMethodAccessorImpl invoke0 - null
Caused by com.endeca.soleng.eac.toolkit.exception.AppControlException com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript - Error executing valid BeanShell script.
Caused by com.endeca.soleng.eac.toolkit.exception.AppControlException  com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript - Error executing valid BeanShell script.
Caused by com.endeca.soleng.eac.toolkit.exception.EacComponentControlException com.endeca.soleng.eac.toolkit.component.ServerComponent startInParallel - Server component 'Dgraph1' failed to start. Refer to component logs in C:\Endeca\Apps\MyApp\config\script\..\..\.\logs\dgraphs\Dgraph1 on host MDEXHost.
[08.12.13 21:20:57] INFO: Released lock 'update_lock'.
Error in Dgraph log:
Stemming should be enabled for 4 languages
WARN 08/13/13 04:48:06.592 UTC (1376369286592) DGRAPH {dgraph,baseline} couldn't stat binary word forms file C:\Endeca\Apps\MyApp\data\dgraphs\Dgraph1\dgraph_input\MyApp.zh-CN.wfdat [err=`No such file or directory',errno=2]
WARN 08/13/13 04:48:06.608 UTC (1376369286592) DGRAPH {dgraph,baseline} couldn't stat binary word forms file C:\Endeca\Apps\MyApp\data\dgraphs\Dgraph1\dgraph_input\MyApp.zh-TW.wfdat [err=`No such file or directory',errno=2]
ERROR 08/13/13 04:48:07.639 UTC (1376369287639) DGRAPH {dgraph,baseline} OptiSpell, error creating pspell manager, "The file "C:\Endeca\Apps\MyApp\data\dgraphs\Dgraph1\dgraph_input/MyApp-aspell.spelldat" can not be opened for reading."
FATAL 08/13/13 04:48:07.639 UTC (1376369287639) DGRAPH {dgraph,baseline} Errors initializing aspell module.  This error is most likely due to an incorrect configuration of aspell. Please correct any previous errors and restart the dgraph.
When I unselect all the languages from Stemming in Dev Studio, the error in Dgraph log shows as following:
Stemming should be enabled for 0 languages
ERROR 08/13/13 05:18:16.444 UTC (1376371096444) DGRAPH {dgraph,baseline} OptiSpell, error creating pspell manager, "The file "C:\Endeca\Apps\MyApp\data\dgraphs\Dgraph1\dgraph_input/MyApp-aspell.spelldat" can not be opened for reading."
FATAL 08/13/13 05:18:16.444 UTC (1376371096444) DGRAPH {dgraph,baseline} Errors initializing aspell module.  This error is most likely due to an incorrect configuration of aspell. Please correct any previous errors and restart the dgraph.

Michael,
Thanks for the reply. I do not want Chinese or any other language, except English. I selected English only in stemming and also changed the <aspell> to false as you suggested but still no change. I am still seeing following error in the dgraph log:
Stemming should be enabled for 1 languages
ERROR 08/14/13 21:56:54.375 UTC (1376517414365) DGRAPH {dgraph,baseline} OptiSpell, error creating pspell manager, "The file "C:\Endeca\Apps\MyApp\data\dgraphs\Dgraph1\dgraph_input/MyApp-aspell.spelldat" can not be opened for reading."
FATAL 08/14/13 21:56:54.375 UTC (1376517414365) DGRAPH {dgraph,baseline} Errors initializing aspell module.  This error is most likely due to an incorrect configuration of aspell. Please correct any previous errors and restart the dgraph.
Any other changes you can suggest?

Similar Messages

  • ATG-Endeca integration issue

    I have a simple jsp to invoke droplet 'InvokeAssembler' as bellow:
    <dsp:droplet name="InvokeAssembler">
      <dsp:param name="contentCollection" value="/content/Shared/PLP Page Collection/PLP passarela - feminino"/>
      <dsp:oparam name="output">
        <dsp:getvalueof var="test" vartype="com.endeca.infront.assembler.ContentItem" param="contentItem" />
        <br/>contentItem.contents: <dsp:valueof param="contentItem.contents" /> <br/></br>
        <br/><br/>contentItem: <c:out value="${test}" />
      </dsp:oparam>
    </dsp:droplet>
    And the 'contentCollection' value is copied from Experience Manager content collection xmgr.html url:
    http://localhost:8006/ifcr/sites/CRS/tools/xmgr.html#content/Shared/PLP%20Page%20Collection/PLP%20passarela%20-%20femini…
    The output for contentItem.contents is empty, I am not sure if there is something I missed in jsp or the content collection is empty in Experience Manager but there is no errors in ATG jboss side, the debug log as below:
    21:50:11,035 INFO [AssemblerPipelineServlet] DEBUG Ignoring (passing on) request because mime type dynamo-internal/html is not allowed for assembly
    21:50:11,040 INFO [AssemblerPipelineServlet] DEBUG Ignoring (passing on) request for /passarela/test.jsp
    21:50:11,531 INFO  [AssemblerTools] DEBUG Assembling content for {@type=ContentSlot, ruleLimit=1, contentCollection=/content/Shared/PLP Page Collection/PLP passarela - feminino}
    21:50:13,289 INFO  [AssemblerTools] DEBUG Record filters: [product.priceListPair:precoVenda_precoTabela]
    21:50:13,290 INFO  [AssemblerTools] DEBUG FilterState.securityFilter:
    21:50:13,318 INFO  [AssemblerTools] DEBUG NavigationState: ?Nf=product.endDate%7CGTEQ+1.3769568E12%7C%7Cproduct.startDate%7CLTEQ+1.3769568E12&Nr=product.priceListPair%3AprecoVenda_precoTabela
    21:50:13,347 INFO [NucleusAssemblerFactory] DEBUG Returning handler from defaultHandlerPath: /atg/endeca/assembler/cartridge/handler/ContentSlot
    21:50:13,363 INFO  [AssemblerTools] DEBUG UserState segments: [sitegroup.grupoPassarela, site.passarelaHome]
    21:50:13,673 INFO  [AssemblerTools] DEBUG Assembled content {contents=[], @type=ContentSlot, atg:currentSiteProductionURL=/passarela, ruleLimit=1, contentCollection=/content/Shared/PLP Page Collection  /PLP passarela - feminino}
    But I have index data there and should return something, anyone has any idea?
    Thanks a lot.

    Hi freind,
    Same errore i got in my case a lso . i am trying to integrate latest endeca installable with ATG 10.1.1 . Could you please help me if you are have followed any remedies for this error..

  • Endeca Windows Server 2012 compatibility (IAP 6.1.1/MDEX 6.2.1)

    Hello,
    I currently try to deploy Endeca ITL HOST on Windows Server 2012 RTM.
    I get an error when doing a Baseline_update action: "Forge.run()" and there are just an empty log to help...
    Windows Server 2008 R2 is working fine for me. Does anybody knows Endeca compatibility issues using Windows server 2012 ?
    My Endeca version is 6.1.1 with MDEX 6.2.1
    Does someone already succeded this operation ? (even with the lastest Endeca version)
    Thanks,
    Gregory

    The component Forge.exe is not working with Windows Server 2012 (c++ runtime error)
    It Looks to be the main problem.
    Does someone knows how to make it works ? changing manifest maybe ?
    Thanks

  • [SOLVED]A nice sharp font renderer (not as sharp as windows)

    Is there another font renderer out there? I tried freetype the default and that gives me blurry edges. Infinality is not better in my opinion. Same blurry edges too many configurations. Are there any other renderers out there?
    Last edited by tedbell (2012-08-07 20:06:21)

    here's ..profile.d/infinality-settings.sh:
    ### INFINALITY ENVIRONMENT VARIABLES FOR EXTRA RUN-TIME OPTIONS ##
    # These environment variables require that their respective patches
    # from http://www.infinality.net have been applied to the Freetype
    # installation you are using. They will do abolutely
    # nothing otherwise!
    # This file should be copied to /etc/profile.d/ for system-wide
    # effects and/or included in ~/.bashrc or ~/.bash_profile for per-user
    # effects:
    # . ~/path/to/this/file/infinality-settings.sh
    # Of course, the per-user settings will override the system-wide
    # settings. Default values indicated below will be used when the
    # environment variables below are not defined.
    # When I say "Default:" below, I'm referring to the default if no
    # environment variables are set. Generally this ends up being
    # whatever Freetype's default is set to.
    # EXAMPLES
    # Please see 3/4 down in this file for examples of different settings.
    ################## EXPLANATION OF SETTINGS ######################
    # SET_XFT_SETTINGS
    # Should the below Xft settings be set globally by this script? (true/false)
    SET_XFT_SETTINGS=true
    # XFT settings are like a red-headed stepchild that should be beaten severely.
    # These only affect legacy programs, and *parts* of some modern programs like
    # google-chrome. We only deal with these settings because we have to, otherwise
    # crap will slip by. I recommend using hintslight and autohint as the defaults
    # normally in local.conf. The reason hintfull and autohint:0 is needed here
    # because otherwise some programs will occassionally request slight hinting for
    # a truetype font. When a program does this, Freetype automatically uses the
    # autohinter, when you may actually want it to be rendered with the TT hinter,
    # (if specified in local.conf). So setting this to hintfull guarantees that the
    # TT font will be rendered with the TT hinter (assuming it is specified in
    # /etc/fonts/local.conf to be rendered that way.) For TT fonts that you want
    # rendered with autohint, specifiying that in the /etc/fonts/local.conf
    # should be enough. But you might think that by setting this to hintfull
    # that it's going to use Freetype's full autohinting (which we *completely*
    # avoid) for fonts you want autohinted. This is where
    # INFINALITY_FT_AUTOFIT_FORCE_SLIGHT_HINTING comes in. It tells freetype to
    # use slight hinting on fonts set for autohinting, even if the program requests
    # full autohinting. Freetype's full hinting only looks OK under certain
    # circumstances. The goal of infinality is to make infinality hinting look
    # good all the time.
    XFT_SETTINGS="
    Xft.antialias: 1
    Xft.autohint: 0
    Xft.dpi: 96
    Xft.hinting: 1
    Xft.hintstyle: hintfull
    Xft.lcdfilter: lcddefault
    Xft.rgba: rgb
    if [ "$SET_XFT_SETTINGS" = "true" ]; then
    echo "$XFT_SETTINGS" | xrdb -merge > /dev/null 2>&1
    fi
    # INFINALITY_FT_FILTER_PARAMS
    # This is a modified version of the patch here:
    # http://levelsofdetail.kendeeter.com/2008/12/dynamic_fir_filter_patch.html
    # Allows you to adjust the FIR filter at runtime instead of at
    # compile time. The idea is to have values add up to 100, and be
    # symmetrical around the middle value. If the values add up to
    # more than 100, the glyphs will appear darker. If less than 100,
    # lighter. I recommend using this method to make glyphs darker
    # or lighter globally as opposed to using the gamma option (see note in
    # the gamma option).
    # Here are some samples of various filter parameters:
    # (this has been changed to use integers between 0 and 100 to
    # avoid problems with regional differences like comma for decimal point)
    # Strong Extra Smooth "15 20 30 20 15" (extra smooth, natural weight)
    # Extra Smooth "20 20 30 20 20" (extra smooth, extra weight)
    # Smooth "15 20 32 20 15" (smooth, natural weight)
    # Stronger Gibson "11 22 38 22 11" (smooth, extra weight)
    # Gibson "11 22 33 22 11" (smooth, natural weight)
    # Freetype Light "00 33 34 33 00" (sharp, natural weight) # freetype's "light" LCD filter
    # Freetype Default "06 25 44 25 06" (sharp, extra weight) # freetype's default
    # Extra Sharp "00 35 35 35 00" (extra sharp, extra weight) # freetype's "light" LCD filter on acid
    # Windows uses something more sharp, maybe along the lines of Freetype's default
    # Default if no ENV_VARS present: [Freetype's default]
    # Recommended: "11 22 38 22 11" (too dark / smooth for some)
    # Example 1: export INFINALITY_FT_FILTER_PARAMS="11 22 38 22 11"
    export INFINALITY_FT_FILTER_PARAMS="11 22 38 22 11"
    # INFINALITY_FT_STEM_ALIGNMENT_STRENGTH
    # This performs analysis on each glyph and determines an amount
    # to shift the glyph, left or right, so that it aligns better to
    # pixel boundaries.
    # This results in subtley cleaner looking stems, at the expense of
    # proper distances between glyphs. This is only active for sizes
    # 10 px or greater and does not apply to bold or italic fonts.
    # There are also exceptions on a small number of fonts that I've
    # not been able to render nicely with alignment enabled. In those
    # cases, a forced translation is applied instead.
    # Possible values:
    # 0 through 100 - think of as percentage of strength
    # 0 corresponds to no shifting whatsoever. In other words, OFF.
    # 100 corresponds to a full move to a snap zone defined by
    # the snapping algorithm, be it left or right. This
    # is the full amount any glyph could be moved in order to make it
    # align to the pixel.
    # Values inbetween act as caps. If the algorithm determines that it
    # wants to move the glyph .33 of a pixel to the left, but the value
    # is set to 50 (i.e. 50%), then the maximum move that would be allowed
    # is 50% of half a pixel, in other words .25. So instead of .33 the
    # glyph is moved .25 of a pixel.
    # For a subtle effect that doesn't dramatically affect the glyph, use
    # 25 for this and 25 for INFINALITY_FT_STEM_FITTING_STRENGTH
    # Default if no ENV_VARS present: 0
    # Recommended if you want to use it: 100
    export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=25
    # INFINALITY_FT_STEM_FITTING_STRENGTH
    # This performs analysis on each glyph and determines an amount
    # to horizontally scale the glyph, so that stems align better to
    # pixel boundaries. An emboldening (or anti-emboldening) is
    # performed afterward to account for stem width exaggeration.
    # This results in subtley cleaner looking fonts, at the expense of
    # proper distances between glyphs and slightly misshapen glyphs.
    # This is only active for sizes 10 px or greater and does not
    # apply to bold or italic fonts.
    # There are also exceptions on a small number of fonts that I've
    # not been able to render nicely with fitting enabled. In those
    # cases, a forced translation is applied instead.
    # Possible values:
    # 0 through 100 - think of as percentage of strength
    # 0 corresponds to no stretching whatsoever. In other words, OFF.
    # 100 corresponds to a full pixel stretch, be outward or inward. This
    # is the full amount any glyph could be stretched in order to make it
    # align to a pixel boundary. Which direction is chosen is part
    # of the art of what I'm trying to do in the code. ;)
    # Values inbetween act as caps. If the algorithm determines that it
    # wants to stretch the glyph .75 of a pixel outward, but the value
    # is set to 50 (i.e. 50%), then the maximum move that would be allowed
    # is 50% of a pixel, in other words .50. So instead of .75 the
    # glyph is stretched .50 of a pixel.
    # For a subtle effect that doesn't dramatically affect the glyph, use
    # 25 for this and 25 for INFINALITY_FT_STEM_FITTING_STRENGTH
    # Default if no ENV_VARS present: 0
    # Recommended if you want to use it: 100
    export INFINALITY_FT_STEM_FITTING_STRENGTH=25
    # INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE
    # This allows you to set a ppem at which alignment and fitting
    # will reach 100%. As glyphs become larger, more dramatic
    # snapping will not affect the glyph shape as much, so it makes
    # sense to allow this.
    # For fonts that are 10 ppem, the values set above for
    # INFINALITY_FT_STEM_ALIGNMENT_STRENGTH and
    # INFINALITY_FT_STEM_FITTING_STRENGTH will be used. As the ppem
    # gradually becomes larger, so will the strength settings, and
    # they will reach 100% at the ppem you specify here.
    # This is a simple linear scale.
    # Possible values:
    # 0 means to not use this feature
    # 11 and up will set the 100% level to that ppem value
    # Anything else is officially undefined, but I still bound it internally.
    # Default if no ENV_VARS present: 0
    export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=40
    # INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS
    # This applies largely to certain MS fonts, but some others as well.
    # it will apply known good settings on a font-by-font basis, regardless
    # of the other settings above or below.
    # - Use known values for selected fonts & ppems that are known to look
    # ok with 100:
    # INFINALITY_FT_STEM_ALIGNMENT_STRENGTH
    # INFINALITY_FT_STEM_FITTING_STRENGTH
    # - Use various internal tweaks like compatible widths and other
    # font-specific hacks.
    # - Use gamma, brightness or contrast adjustments automatically
    # on certain fonts. Global settings will still apply afterwards.
    # - Enable various forced settings on selective fonts during
    # rasterization and stem_alignment.
    # If set to TRUE, this will use 100 regardless of the values you have
    # specified above. It will not affect fonts that are not in this
    # small list.
    # Possible values:
    # FALSE means to not use this feature
    # TRUE will enable this feature
    # Default if no ENV_VARS present: FALSE
    # Recommended: TRUE
    export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=true
    # INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH
    # This enables an algorithm found in ChromeOS for sharpening the
    # appearance of glyphs. It is based off this patch:
    # http://codereview.chromium.org/3298011/diff/9001/media-libs/freetype/files/freetype-2.3.11-lcd-sharpen.patches
    # It gives glyphs a more "grainy" look through some gamma
    # correction. It does tend to thin out vertical stems, which
    # may be a feature or a bug depending on your taste ;)
    # Possible values:
    # 0 through 100 - think of as percentage of strength
    # 0 corresponds to no sharpening whatsoever. In other words, OFF.
    # 25 is good for a subtle effect.
    # 50 corresponds to the default ChromeOS value.
    # 100 corresponds to maximum sharpening. This usually results in
    # something undesirable looking.
    # As you increase this amount, it is good to decrease the gamma (2nd value)
    # of INFINALITY_FT_PSEUDO_GAMMA, and possibly increase
    # INFINALITY_FT_STEM_FITTING_STRENGTH and
    # INFINALITY_FT_STEM_ALIGNMENT_STRENGTH, as it seems like the algorithm
    # lightens stems that aren't fully on-pixel.
    # Default if no ENV_VARS present: 0
    # Recommended: If you're going to use this filter - 50
    export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
    # INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH
    # This enables an algorithm developed with the intention to sharpen
    # fonts to look similarly to Windows.
    # It gives glyphs a more "grainy" look, like the ChromeOS filter
    # except it does so more selectively. This prevents the thinning
    # of vertical stems that is noticible when a blanket gamma filter
    # like the ChromeOS filter is applied.
    # I also get a "cleaner" impression from the fonts with this Windows
    # style filter. This filter was done by 100% experimentation,
    # and there things that could probably be improved.
    # Some may argue that I shouldn't be trying to take the shortcomings
    # of the MS approach and bring them here. I disagree, as part
    # of freedom is having the right to make your fonts look as
    # shitty as you'd like.
    # Using this filter does somewhat lessen the need to use stem
    # fitting and stem alignment, as glyphs appear sharper.
    # This setting can be used at the same time as the previous chromeOS
    # sharpening, and happens after it in the code.
    # Possible values:
    # 0 through 100 - think of as percentage of strength
    # 0 corresponds to no sharpening whatsoever. In other words, OFF.
    # 10-25 is good for a subtle effect while not completely decimating glyphs.
    # 50-75 corresponds to probably something in the range that Windows uses.
    # 100 corresponds to maximum sharpening.
    # Using a high value for this variable along with enabling the
    # fringe filter (below) almost eliminates the need
    # for INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT to be set to 100,
    # and can instead be set at 0. (Setting
    # INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT to 0 prevents missing
    # stems in the middle of s. The drawback is that many fonts just look
    # way too sharp and grainy at this setting. Your call.)
    # Default if no ENV_VARS present: 0
    # Recommended if you want to use this filter: 65
    export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=10
    # INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT
    # When using autohinting, horizontal stems you'd find in E, f, T, -,
    # etc. are normally not snapped to full integer pixel heights, meaning
    # that you will get a semi-dark fringe on these stems, above or
    # below the black line of pixels:
    # (- represents the semi-dark pixels)
    # Setting this to 100 will force integer pixel heights. Setting it to
    # zero will do what Freetype does by default. Anything inbetween will
    # act as a weighted average of the two.
    # This is disabled when the standard width is found (via voodoo) to be
    # less than 1 pixel, in order to prevent the vanishing stem issues on
    # letters with diagonal stems like a and s.
    # Under most circumstances, this should be set at 100. If you choose to
    # not set it to 100, you may want to set INFINALITY_FT_FRINGE_FILTER_STRENGTH
    # to a non-zero value in order to reduce fringing.
    # Possible values:
    # 0 - default Freetype value
    # 100 - a full pixel
    # Default if no ENV_VARS present: 0
    # Recommended: 100
    export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
    # INFINALITY_FT_USE_VARIOUS_TWEAKS
    # - Force autohint when no TT instructions present.
    # - Artificially embolden horizontally only.
    # - When artificially emboldening, maintain the glyph width.
    # - Embolden light and thin-stemmed glyphs automatically.
    # - Don't sharpen italics.
    # Some fonts look bad when stem aligned at certain ppems, no matter
    # what. I've put exceptions in to deal with these, included in
    # these tweaks. Georgia and Lucida Grande are examples.
    # Possible values:
    # true - enable tweaks
    # false - do not enable tweaks (do Freetype default)
    # Default if no ENV_VARS present: false
    # Recommended: true
    export INFINALITY_FT_USE_VARIOUS_TWEAKS=true
    # INFINALITY_FT_GAMMA_CORRECTION
    # This does a weighted gamma correction at the LCD filter phase
    # PRIOR to the LCD filter. Unfortunately it does not however
    # take into account the color on which the glyph is being rendered
    # (or for that matter the color of the glyph),
    # which would need to happen in X rendering. It is actually
    # using the gamma function in calculations though.
    # The first value indicates a px value, the second indicates a
    # "gamma" value. All sizes less than the px value will be corrected
    # on a weighted scale based on the second value.
    # The gamma value is commonly between 0.0 and 3.0. Due to localization
    # issues, the gamma value should be specified as it's actual value
    # multiplied by 100. So a gamma of 1.3 would be 130. In practice,
    # I'd stay between 40 and 250.
    # Values 1 through 100 will darken the glyph
    # Values greater than 100 will lighten the glyph
    # Example 1: Darken glyphs that are less than 10 px. With some fonts
    # even 5 or 6px is readable!
    # export INFINALITY_FT_GAMMA_CORRECTION="10 60"
    # Example 2: Lighten all glyphs (below 100px)
    # export INFINALITY_FT_GAMMA_CORRECTION="100 150"
    # Example 3: Do nothing
    # export INFINALITY_FT_GAMMA_CORRECTION="0 100"
    # Default: [No gamma correction]
    export INFINALITY_FT_GAMMA_CORRECTION="0 100"
    # INFINALITY_FT_BRIGHTNESS
    # This filter adjusts brightness, using the standard algorithm
    # for brightness. It is applied AFTER the LCD filtering.
    # For a Windows XP look, set brightness to something and contrast to 50
    # This will also tend to increase its sharpness.
    # These values are relative and don't really mean anything
    # however they are satisfactory for a range of appearances.
    # Another tip is to use a gamma setting of "1000 110" or something
    # over 100 to lighten things before processing.
    # Default if no ENV_VARS present: 0
    # Dark XP Experience: -25
    # Light XP Experience: 40
    # Example: export INFINALITY_FT_BRIGHTNESS="-20"
    export INFINALITY_FT_BRIGHTNESS="0"
    # INFINALITY_FT_CONTRAST
    # This filter adjusts contrast, using the standard algorithm
    # for contrast. It is applied AFTER the LCD filtering.
    # For a Windows XP look, set brightness to -25 and contrast to 50
    # This will also tend to increase its sharpness.
    # These values are relative and don't really mean anything
    # however they are satisfactory for a range of appearances.
    # Another tip is to use a gamma setting of "1000 110" or something
    # over 100 to lighten things before processing.
    # Default if no ENV_VARS present: 0
    # Dark or Light XP Experience: 50
    # Example: export INFINALITY_FT_CONTRAST="50"
    export INFINALITY_FT_CONTRAST="0"
    # INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH
    # This filter adjusts subpixel-rendered glyphs toward grayscale.
    # Sometimes this is useful in getting a rendering more like
    # OSX.
    # Range: Integers 0 through 100
    # 0 represents no filtering
    # 50 represents halfway between subpixel and grayscale
    # 100 represents completely grayscale
    # Default if no ENV_VARS present: 0
    # Recommended, if you want to use it: 30
    # Example: export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH="33"
    export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH="0"
    # INFINALITY_FT_FRINGE_FILTER_STRENGTH
    # This filter tries to remove the horizontal fringing that is found on
    # default autohinted glyphs (similar to OSX-rendered glyphs).
    # For example, an E may be rendered so that the middle horizontal
    # stem is 100% black, but also has a horizonal row of pixels above
    # it that is at 50% intensity. This makes the glyph look dirty,
    # however it is technically accurate.
    # This would be useful in cases where you have
    # INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT set to something less than 100
    # but also can affect glyphs at 100, to some degree.
    # Unless fonts are showing fringes in a way that annoys you, I recommend
    # keeping it disabled, as it can slightly interfere with smooth appearance
    # sometimes.
    # Range: Integers 0 through 100
    # 0 represents no filtering
    # 50 represents a 50% reduction of detected fringes
    # 100 represents completely removing detected fringes
    # Default if no ENV_VARS present: 0
    # Recommended, if you want to use it: 100
    # Example: export INFINALITY_FT_FRINGE_FILTER_STRENGTH="100"
    export INFINALITY_FT_FRINGE_FILTER_STRENGTH="0"
    # INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH
    # This post-filter darkens horizontal stems that autohint renders as semi-dark.
    # Freetype will by default not force stems to render to pixel boundaries
    # because it results in "vanishing stems". This happens on things like
    # s S a and other glyphs with center diagonal stems.
    # If you have INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT set to 100,
    # you're telling it to force pixel boundaries, which can result in the
    # vanishing stems. To get around this problem, I internally override the
    # INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT setting if the stem width
    # is less than a full pixel, regardless. This causes semi-dark stems, but
    # at least there are stems there.
    # This filter is intended to darken those semi-dark stems. I highly
    # recommend using this, but setting to a low value like 10, because
    # it is particularly sensitive right now, and can make thin fonts
    # look weird otherwise.
    # Range: Integers 0 through 100
    # 0 represents no darkening
    # 50 represents a 50% increase toward 1 pixel in height
    # 100 represents a full pixel of height
    # Default if no ENV_VARS present: 0
    # Recommended, if you want to use it: 10
    # Example: export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH="10"
    export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH="10"
    # INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH
    # This post-filter darkens vertical stems less than 1 pixel that autohint
    # renders as semi-dark. This applies mostly to thin fonts like
    # Courier New, Raleway, and fonts with the word "Light" in the title or
    # style. Although what autohint is doing is technically correct, it
    # results in a bad looking rendering because it's too light, at small
    # ppems. This filter tries to correct that.
    # There is an aspect of this that is automatic, so it's safer to use
    # larger values for this than the above horizontal ENV_VAR. However
    # setting this higher has more impact on thinner fonts. So, I still
    # recommend lower values.
    # Range: Integers 0 through 100
    # 0 represents no darkening
    # 50 represents a 50% increase (from current strength) toward 1 pixel
    # 100 represents a full pixel of width
    # Default if no ENV_VARS present: 0
    # Recommended, if you want to use it: 25
    # Example: export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH="25"
    export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH="25"
    # INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS
    # This will slightly stretch some glyphs vertically between 9px
    # and 14px (inclusive). Some people may find this more
    # aesthetically pleasing. This only applies to fonts that are
    # using autohint. I used to recommend this to be set true, but
    # it does mess with some (less popular) glyphs in a nasty way.
    # The goal here is to increase the height of some fonts by 1 px
    # but leave the x-height where it is. Arial is a good example
    # of this working properly. Compare the heights of Arial, Times
    # and Freesans with this on, vs. TT hinted versions of Arial and
    # Times.
    # Possible values:
    # true - enable height adjustment
    # false - do not enable height adjustment
    # Default: false
    export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=true
    # Experimental emboldening values for OSX mode
    export INFINALITY_FT_GLOBAL_EMBOLDEN_X_VALUE=0
    export INFINALITY_FT_GLOBAL_EMBOLDEN_Y_VALUE=0
    export INFINALITY_FT_BOLD_EMBOLDEN_X_VALUE=0
    export INFINALITY_FT_BOLD_EMBOLDEN_Y_VALUE=0
    ########################### EXAMPLES ############################
    # Set the USE_STYLE variable below to try each example.
    # Make sure to set your style in /etc/fonts/local.conf too.
    # Possible options:
    # DEFAULT - Use above settings. A compromise that should please most people.
    # OSX - Simulate OSX rendering
    # UBUNTU - Simulate UBUNTU rendering
    # LINUX - Generic "Linux" style - no snapping or certain other tweaks
    # WINDOWS - Simulate Windows rendering
    # WINDOWS7 - Simulate Windows rendering with normal glyphs
    # WINDOWS7LIGHT- Simulate Windows 7 rendering with lighter glyphs
    # WINDOWS - Simulate Windows rendering
    # VANILLA - Just subpixel hinting
    # CUSTOM - Your own choice. See below
    # ----- Infinality styles -----
    # CLASSIC - Infinality rendering circa 2010. No snapping.
    # NUDGE - CLASSIC with lightly stem snapping and tweaks
    # PUSH - CLASSIC with medium stem snapping and tweaks
    # SHOVE - Full stem snapping and tweaks without sharpening
    # SHARPENED - Full stem snapping, tweaks, and Windows-style sharpening
    # INFINALITY - Settings I use
    # DISABLED - Act as though running without the extra infinality enhancements (just subpixel hinting).
    USE_STYLE="LINUX"
    ### NEEDS WORK ###
    ################# OSX STYLE #################
    if [ "$USE_STYLE" = "OSX" ]; then
    export INFINALITY_FT_FILTER_PARAMS="03 32 38 32 03"
    export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=25
    export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
    export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
    export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
    export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=0
    export INFINALITY_FT_STEM_FITTING_STRENGTH=0
    export INFINALITY_FT_GAMMA_CORRECTION="1000 80"
    export INFINALITY_FT_BRIGHTNESS="10"
    export INFINALITY_FT_CONTRAST="20"
    export INFINALITY_FT_USE_VARIOUS_TWEAKS=false
    export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=false
    export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=0
    export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=0
    export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=false
    export INFINALITY_FT_GLOBAL_EMBOLDEN_X_VALUE=0
    export INFINALITY_FT_GLOBAL_EMBOLDEN_Y_VALUE=8
    export INFINALITY_FT_BOLD_EMBOLDEN_X_VALUE=16
    export INFINALITY_FT_BOLD_EMBOLDEN_Y_VALUE=0
    fi
    ################# UBUNTU STYLE #################
    if [ "$USE_STYLE" = "UBUNTU" ]; then
    export INFINALITY_FT_FILTER_PARAMS="11 22 38 22 11"
    export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
    export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
    export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
    export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
    export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=0
    export INFINALITY_FT_STEM_FITTING_STRENGTH=0
    export INFINALITY_FT_GAMMA_CORRECTION="1000 80"
    export INFINALITY_FT_BRIGHTNESS="-10"
    export INFINALITY_FT_CONTRAST="15"
    export INFINALITY_FT_USE_VARIOUS_TWEAKS=true
    export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=false
    export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=0
    export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=0
    export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=false
    fi
    ################# LINUX STYLE #################
    if [ "$USE_STYLE" = "LINUX" ]; then
    export INFINALITY_FT_FILTER_PARAMS="06 25 44 25 06"
    export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
    export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
    export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=0
    export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=0
    export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=25
    export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=0
    export INFINALITY_FT_STEM_FITTING_STRENGTH=0
    export INFINALITY_FT_GAMMA_CORRECTION="0 100"
    export INFINALITY_FT_BRIGHTNESS="10"
    export INFINALITY_FT_CONTRAST="50"
    export INFINALITY_FT_USE_VARIOUS_TWEAKS=true
    export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=false
    export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
    export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=0
    export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=false
    fi
    ################# WINDOWS XP STYLE LIGHT #################
    if [ "$USE_STYLE" = "WINDOWSXPLIGHT" ]; then
    export INFINALITY_FT_FILTER_PARAMS="06 25 44 25 06"
    export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
    export INFINALITY_FT_FRINGE_FILTER_STRENGTH=100
    export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
    export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
    export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=65
    export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=15
    export INFINALITY_FT_STEM_FITTING_STRENGTH=15
    export INFINALITY_FT_GAMMA_CORRECTION="1000 120"
    export INFINALITY_FT_BRIGHTNESS="20"
    export INFINALITY_FT_CONTRAST="30"
    export INFINALITY_FT_USE_VARIOUS_TWEAKS=true
    export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=false
    export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
    export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=30
    export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=true
    fi
    ################# WINDOWS 7 STYLE LIGHT #################
    if [ "$USE_STYLE" = "WINDOWS7LIGHT" ]; then
    export INFINALITY_FT_FILTER_PARAMS="20 25 38 25 05"
    export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
    export INFINALITY_FT_FRINGE_FILTER_STRENGTH=100
    export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
    export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
    export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=100
    export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=0
    export INFINALITY_FT_STEM_FITTING_STRENGTH=0
    export INFINALITY_FT_GAMMA_CORRECTION="1000 160"
    export INFINALITY_FT_BRIGHTNESS="0"
    export INFINALITY_FT_CONTRAST="20"
    export INFINALITY_FT_USE_VARIOUS_TWEAKS=true
    export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=false
    export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
    export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=30
    export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=true
    fi
    ################# WINDOWS XP STYLE #################
    if [ "$USE_STYLE" = "WINDOWSXP" ]; then
    export INFINALITY_FT_FILTER_PARAMS="06 25 44 25 06"
    export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
    export INFINALITY_FT_FRINGE_FILTER_STRENGTH=100
    export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
    export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
    export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=65
    export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=15
    export INFINALITY_FT_STEM_FITTING_STRENGTH=15
    export INFINALITY_FT_GAMMA_CORRECTION="1000 120"
    export INFINALITY_FT_BRIGHTNESS="10"
    export INFINALITY_FT_CONTRAST="20"
    export INFINALITY_FT_USE_VARIOUS_TWEAKS=true
    export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=false
    export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
    export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=30
    export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=true
    fi
    ################# WINDOWS 7 STYLE #################
    if [ "$USE_STYLE" = "WINDOWS7" ]; then
    export INFINALITY_FT_FILTER_PARAMS="20 25 42 25 06"
    export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
    export INFINALITY_FT_FRINGE_FILTER_STRENGTH=100
    export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
    export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
    export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=65
    export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=0
    export INFINALITY_FT_STEM_FITTING_STRENGTH=0
    export INFINALITY_FT_GAMMA_CORRECTION="1000 120"
    export INFINALITY_FT_BRIGHTNESS="10"
    export INFINALITY_FT_CONTRAST="20"
    export INFINALITY_FT_USE_VARIOUS_TWEAKS=true
    export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=false
    export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
    export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=0
    export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=true
    fi
    ############### VANILLA STYLE ##############
    if [ "$USE_STYLE" = "VANILLA" ]; then
    export INFINALITY_FT_FILTER_PARAMS="06 25 38 25 06"
    export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
    export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
    export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=0
    export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=0
    export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=0
    export INFINALITY_FT_STEM_FITTING_STRENGTH=0
    export INFINALITY_FT_GAMMA_CORRECTION="0 100"
    export INFINALITY_FT_BRIGHTNESS="0"
    export INFINALITY_FT_CONTRAST="0"
    export INFINALITY_FT_USE_VARIOUS_TWEAKS=false
    export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=false
    export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=0
    export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=0
    export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=false
    fi
    ############### CLASSIC INFINALITY STYLE ##############
    if [ "$USE_STYLE" = "CLASSIC" ]; then
    export INFINALITY_FT_FILTER_PARAMS="06 25 38 25 06"
    export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
    export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
    export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=0
    export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=0
    export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=0
    export INFINALITY_FT_STEM_FITTING_STRENGTH=0
    export INFINALITY_FT_GAMMA_CORRECTION="0 100"
    export INFINALITY_FT_BRIGHTNESS="0"
    export INFINALITY_FT_CONTRAST="0"
    export INFINALITY_FT_USE_VARIOUS_TWEAKS=true
    export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=true
    export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
    export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=0
    export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=false
    fi
    ################# NUDGE STYLE #################
    if [ "$USE_STYLE" = "NUDGE" ]; then
    export INFINALITY_FT_FILTER_PARAMS="11 22 38 22 11"
    export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
    export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
    export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
    export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
    export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=25
    export INFINALITY_FT_STEM_FITTING_STRENGTH=15
    export INFINALITY_FT_GAMMA_CORRECTION="0 100"
    export INFINALITY_FT_BRIGHTNESS="0"
    export INFINALITY_FT_CONTRAST="0"
    export INFINALITY_FT_USE_VARIOUS_TWEAKS=true
    export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=true
    export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
    export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=30
    export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=false
    fi
    ################# PUSH STYLE #################
    if [ "$USE_STYLE" = "PUSH" ]; then
    export INFINALITY_FT_FILTER_PARAMS="11 22 38 22 11"
    export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
    export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
    export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
    export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
    export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=75
    export INFINALITY_FT_STEM_FITTING_STRENGTH=50
    export INFINALITY_FT_GAMMA_CORRECTION="0 100"
    export INFINALITY_FT_BRIGHTNESS="0"
    export INFINALITY_FT_CONTRAST="0"
    export INFINALITY_FT_USE_VARIOUS_TWEAKS=true
    export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=true
    export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
    export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=30
    export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=true
    fi
    ################# INFINALITY STYLE #################
    if [ "$USE_STYLE" = "INFINALITY" ]; then
    export INFINALITY_FT_FILTER_PARAMS="11 22 38 22 11"
    export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
    export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
    export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
    export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
    export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=5
    export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=25
    export INFINALITY_FT_STEM_FITTING_STRENGTH=25
    export INFINALITY_FT_GAMMA_CORRECTION="0 100"
    export INFINALITY_FT_BRIGHTNESS="0"
    export INFINALITY_FT_CONTRAST="0"
    export INFINALITY_FT_USE_VARIOUS_TWEAKS=true
    export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=true
    export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
    export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=40
    export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=true
    fi
    ################# SHOVE STYLE #################
    if [ "$USE_STYLE" = "SHOVE" ]; then
    export INFINALITY_FT_FILTER_PARAMS="11 22 38 22 11"
    export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
    export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
    export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
    export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
    export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=100
    export INFINALITY_FT_STEM_FITTING_STRENGTH=100
    export INFINALITY_FT_GAMMA_CORRECTION="0 100"
    export INFINALITY_FT_BRIGHTNESS="0"
    export INFINALITY_FT_CONTRAST="0"
    export INFINALITY_FT_USE_VARIOUS_TWEAKS=true
    export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=true
    export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
    export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=0
    export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=true
    fi
    ################# SHARPENED INFINALITY STYLE #################
    if [ "$USE_STYLE" = "SHARPENED" ]; then
    export INFINALITY_FT_FILTER_PARAMS="11 22 38 22 11"
    export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
    export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
    export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
    export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
    export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=65
    export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=25
    export INFINALITY_FT_STEM_FITTING_STRENGTH=25
    export INFINALITY_FT_GAMMA_CORRECTION="0 100"
    export INFINALITY_FT_BRIGHTNESS="0"
    export INFINALITY_FT_CONTRAST="0"
    export INFINALITY_FT_USE_VARIOUS_TWEAKS=true
    export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=true
    export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
    export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=40
    export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=true
    fi
    ################# DISABLED STYLE #################
    if [ "$USE_STYLE" = "DISABLED" ]; then
    export INFINALITY_FT_FILTER_PARAMS=
    export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=
    export INFINALITY_FT_FRINGE_FILTER_STRENGTH=
    export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=
    export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=
    export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=
    export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=
    export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=
    export INFINALITY_FT_STEM_FITTING_STRENGTH=
    export INFINALITY_FT_GAMMA_CORRECTION="0 100"
    export INFINALITY_FT_BRIGHTNESS="0"
    export INFINALITY_FT_CONTRAST="0"
    export INFINALITY_FT_USE_VARIOUS_TWEAKS=false
    export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=false
    export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=
    export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=
    export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=false
    fi
    ################# CUSTOM STYLE #################
    if [ "$USE_STYLE" = "CUSTOM" ]; then
    export INFINALITY_FT_FILTER_PARAMS="11 22 38 22 11"
    export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
    export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
    export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
    export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
    export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
    export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=100
    export INFINALITY_FT_STEM_FITTING_STRENGTH=100
    export INFINALITY_FT_GAMMA_CORRECTION="0 100"
    export INFINALITY_FT_BRIGHTNESS="0"
    export INFINALITY_FT_CONTRAST="0"
    export INFINALITY_FT_USE_VARIOUS_TWEAKS=true
    export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=true
    export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
    export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=0
    export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=true
    fi
    And here is fonts.conf:
    <?xml version="1.0"?>
    <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
    <!-- /etc/fonts/fonts.conf file to configure system font access -->
    <fontconfig>
    <!--
    DO NOT EDIT THIS FILE.
    IT WILL BE REPLACED WHEN FONTCONFIG IS UPDATED.
    LOCAL CHANGES BELONG IN 'local.conf'.
    The intent of this standard configuration file is to be adequate for
    most environments. If you have a reasonably normal environment and
    have found problems with this configuration, they are probably
    things that others will also want fixed. Please submit any
    problems to the fontconfig bugzilla system located at fontconfig.org
    Note that the normal 'make install' procedure for fontconfig is to
    replace any existing fonts.conf file with the new version. Place
    any local customizations in local.conf which this file references.
    Keith Packard
    -->
    <!-- Font directory list -->
    <dir>/usr/share/fonts</dir>
    <dir>~/.fonts</dir>
    <!--
    Accept deprecated 'mono' alias, replacing it with 'monospace'
    -->
    <match target="pattern">
    <test qual="any" name="family">
    <string>mono</string>
    </test>
    <edit name="family" mode="assign">
    <string>monospace</string>
    </edit>
    </match>
    <!--
    Accept alternate 'sans serif' spelling, replacing it with 'sans-serif'
    -->
    <match target="pattern">
    <test qual="any" name="family">
    <string>sans serif</string>
    </test>
    <edit name="family" mode="assign">
    <string>sans-serif</string>
    </edit>
    </match>
    <!--
    Accept deprecated 'sans' alias, replacing it with 'sans-serif'
    -->
    <match target="pattern">
    <test qual="any" name="family">
    <string>sans</string>
    </test>
    <edit name="family" mode="assign">
    <string>sans-serif</string>
    </edit>
    </match>
    <!--
    Load local system customization file
    -->
    <include ignore_missing="yes">conf.d</include>
    <!-- Font cache directory list -->
    <cachedir>/var/cache/fontconfig</cachedir>
    <cachedir>~/.fontconfig</cachedir>
    <config>
    <!--
    These are the default Unicode chars that are expected to be blank
    in fonts. All other blank chars are assumed to be broken and
    won't appear in the resulting charsets
    -->
    <blank>
    <int>0x0020</int> <!-- SPACE -->
    <int>0x00A0</int> <!-- NO-BREAK SPACE -->
    <int>0x00AD</int> <!-- SOFT HYPHEN -->
    <int>0x034F</int> <!-- COMBINING GRAPHEME JOINER -->
    <int>0x0600</int> <!-- ARABIC NUMBER SIGN -->
    <int>0x0601</int> <!-- ARABIC SIGN SANAH -->
    <int>0x0602</int> <!-- ARABIC FOOTNOTE MARKER -->
    <int>0x0603</int> <!-- ARABIC SIGN SAFHA -->
    <int>0x06DD</int> <!-- ARABIC END OF AYAH -->
    <int>0x070F</int> <!-- SYRIAC ABBREVIATION MARK -->
    <int>0x115F</int> <!-- HANGUL CHOSEONG FILLER -->
    <int>0x1160</int> <!-- HANGUL JUNGSEONG FILLER -->
    <int>0x1680</int> <!-- OGHAM SPACE MARK -->
    <int>0x17B4</int> <!-- KHMER VOWEL INHERENT AQ -->
    <int>0x17B5</int> <!-- KHMER VOWEL INHERENT AA -->
    <int>0x180E</int> <!-- MONGOLIAN VOWEL SEPARATOR -->
    <int>0x2000</int> <!-- EN QUAD -->
    <int>0x2001</int> <!-- EM QUAD -->
    <int>0x2002</int> <!-- EN SPACE -->
    <int>0x2003</int> <!-- EM SPACE -->
    <int>0x2004</int> <!-- THREE-PER-EM SPACE -->
    <int>0x2005</int> <!-- FOUR-PER-EM SPACE -->
    <int>0x2006</int> <!-- SIX-PER-EM SPACE -->
    <int>0x2007</int> <!-- FIGURE SPACE -->
    <int>0x2008</int> <!-- PUNCTUATION SPACE -->
    <int>0x2009</int> <!-- THIN SPACE -->
    <int>0x200A</int> <!-- HAIR SPACE -->
    <int>0x200B</int> <!-- ZERO WIDTH SPACE -->
    <int>0x200C</int> <!-- ZERO WIDTH NON-JOINER -->
    <int>0x200D</int> <!-- ZERO WIDTH JOINER -->
    <int>0x200E</int> <!-- LEFT-TO-RIGHT MARK -->
    <int>0x200F</int> <!-- RIGHT-TO-LEFT MARK -->
    <int>0x2028</int> <!-- LINE SEPARATOR -->
    <int>0x2029</int> <!-- PARAGRAPH SEPARATOR -->
    <int>0x202A</int> <!-- LEFT-TO-RIGHT EMBEDDING -->
    <int>0x202B</int> <!-- RIGHT-TO-LEFT EMBEDDING -->
    <int>0x202C</int> <!-- POP DIRECTIONAL FORMATTING -->
    <int>0x202D</int> <!-- LEFT-TO-RIGHT OVERRIDE -->
    <int>0x202E</int> <!-- RIGHT-TO-LEFT OVERRIDE -->
    <int>0x202F</int> <!-- NARROW NO-BREAK SPACE -->
    <int>0x205F</int> <!-- MEDIUM MATHEMATICAL SPACE -->
    <int>0x2060</int> <!-- WORD JOINER -->
    <int>0x2061</int> <!-- FUNCTION APPLICATION -->
    <int>0x2062</int> <!-- INVISIBLE TIMES -->
    <int>0x2063</int> <!-- INVISIBLE SEPARATOR -->
    <int>0x206A</int> <!-- INHIBIT SYMMETRIC SWAPPING -->
    <int>0x206B</int> <!-- ACTIVATE SYMMETRIC SWAPPING -->
    <int>0x206C</int> <!-- INHIBIT ARABIC FORM SHAPING -->
    <int>0x206D</int> <!-- ACTIVATE ARABIC FORM SHAPING -->
    <int>0x206E</int> <!-- NATIONAL DIGIT SHAPES -->
    <int>0x206F</int> <!-- NOMINAL DIGIT SHAPES -->
    <int>0x2800</int> <!-- BRAILLE PATTERN BLANK -->
    <int>0x3000</int> <!-- IDEOGRAPHIC SPACE -->
    <int>0x3164</int> <!-- HANGUL FILLER -->
    <int>0xFEFF</int> <!-- ZERO WIDTH NO-BREAK SPACE -->
    <int>0xFFA0</int> <!-- HALFWIDTH HANGUL FILLER -->
    <int>0xFFF9</int> <!-- INTERLINEAR ANNOTATION ANCHOR -->
    <int>0xFFFA</int> <!-- INTERLINEAR ANNOTATION SEPARATOR -->
    <int>0xFFFB</int> <!-- INTERLINEAR ANNOTATION TERMINATOR -->
    </blank>
    <!--
    Rescan configuration every 30 seconds when FcFontSetList is called
    -->
    <rescan>
    <int>30</int>
    </rescan>
    </config>
    </fontconfig>
    Infinality.conf:
    <?xml version='1.0'?>
    <!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
    <fontconfig>
    <!-- Choose an OS Rendering Style. This will determine B/W, grayscale,
    or subpixel antialising and slight, full or no hinting and replacements (if set in next option) -->
    <!-- Style should also be set in the infinality-settings.sh file, ususally in /etc/profile.d/ -->
    <!-- Choose one of these options:
    Infinality - subpixel AA, minimal replacements/tweaks, sans=Arial
    Windows 7 - subpixel AA, sans=Arial
    Windows XP - subpixel AA, sans=Arial
    Windows 98 - B/W full hinting on TT fonts, grayscale AA for others, sans=Arial
    OSX - Slight hinting, subpixel AA, sans=Helvetica Neue
    OSX2 - No hinting, subpixel AA, sans=Helvetica Neue
    Linux - subpixel AA, sans=DejaVu Sans
    === Recommended Setup ===
    Run ./infctl.sh script located in the current directory to set the style.
    # ./infctl.sh setstyle
    === Manual Setup ===
    See the infinality/styles.conf.avail/ directory for all options. To enable
    a different style, remove the symlink "conf.d" and link to another style:
    # rm conf.d
    # ln -s styles.conf.avail/win7 conf.d
    -->
    <!-- Uncomment this to reject all bitmap fonts -->
    <!-- Make sure to run this as root if having problems: fc-cache -f -->
    <!--
    <selectfont>
    <rejectfont>
    <pattern>
    <patelt name="scalable" >
    <bool>false</bool>
    </patelt>
    </pattern>
    </rejectfont>
    </selectfont>
    -->
    <!-- Ban Type-1 fonts because they render poorly -->
    <!-- Comment this out to allow all Type 1 fonts -->
    <selectfont>
    <rejectfont>
    <pattern>
    <patelt name="fontformat" >
    <string>Type 1</string>
    </patelt>
    </pattern>
    </rejectfont>
    </selectfont>
    <!-- Globally use embedded bitmaps in fonts like Calibri? -->
    <match target="font" >
    <edit name="embeddedbitmap" mode="assign">
    <bool>false</bool>
    </edit>
    </match>
    <!-- Substitute truetype fonts in place of bitmap ones? -->
    <match target="pattern" >
    <edit name="prefer_outline" mode="assign">
    <bool>true</bool>
    </edit>
    </match>
    <!-- Make (some) monospace/coding TTF fonts render as bitmaps? -->
    <!-- courier new, andale mono, monaco, etc. -->
    <match target="pattern" >
    <edit name="bitmap_monospace" mode="assign">
    <bool>false</bool>
    </edit>
    </match>
    <!-- Force autohint always -->
    <!-- Useful for debugging and for free software purists -->
    <match target="font">
    <edit name="force_autohint" mode="assign">
    <bool>false</bool>
    </edit>
    </match>
    <!-- Set DPI. dpi should be set in ~/.Xresources to 96 -->
    <!-- Setting to 72 here makes the px to pt conversions work better (Chrome) -->
    <!-- Some may need to set this to 96 though -->
    <match target="pattern">
    <edit name="dpi" mode="assign">
    <double>96</double>
    </edit>
    </match>
    <!-- Use Qt subpixel positioning on autohinted fonts? -->
    <!-- This only applies to Qt and autohinted fonts. Qt determines subpixel positioning based on hintslight vs. hintfull, -->
    <!-- however infinality patches force slight hinting inside freetype, so this essentially just fakes out Qt. -->
    <!-- Should only be set to true if you are not doing any stem alignment or fitting in environment variables -->
    <match target="pattern" >
    <edit name="qt_use_subpixel_positioning" mode="assign">
    <bool>false</bool>
    </edit>
    </match>
    <!-- Run infctl.sh or change the symlink in current directory instead of modifying this -->
    <include>infinality/conf.d</include>
    </fontconfig>
    I tried every conf.d symlink in the /etc/fonts/infinality/styles.conf.avail folder. I just can't get the fonts to be sharp with nice uniform smoothness. They look garbled.
    I just tried the ubuntu freetype and it looks worse.

  • Endeca JDBC adapter issue

    Hi,
    When I ran my baseline with one jdbc record adapter there was no issue.
    When I added one more JDBC record adapter it fails.
    I have mentioned the pass through properly itself
    COLUMN_HANDLER_CLASS     com.endeca.soleng.itl.jdbc.AdvancedJDBCColumnHandler
    SEVERE: Failed to load JdbcColumnHandler: com.endeca.soleng.itl.jdbc.AdvancedJDBCColumnHandler.
    com.endeca.edf.adapter.plugins.JdbcAdapterException: Failed to load JdbcColumnHandler: com.endeca.soleng.itl.jdbc.AdvancedJDBCColumnHandler.
         at com.endeca.edf.adapter.plugins.JdbcAdapter.loadColumnHandler(JdbcAdapter.java:267)
         at com.endeca.edf.adapter.plugins.JdbcAdapter.execute(JdbcAdapter.java:84)
         at com.endeca.edf.adapter.AdapterRunner.run(AdapterRunner.java:168)
         at com.endeca.edf.adapter.AdapterRunner.main(AdapterRunner.java:43)
    Caused by: java.lang.ClassNotFoundException: com.endeca.soleng.itl.jdbc.AdvancedJDBCColumnHandler
         at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
         at java.security.AccessController.doPrivileged(Native Method)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:169)
         at com.endeca.edf.adapter.plugins.JdbcAdapter.loadColumnHandler(JdbcAdapter.java:263)
         ... 3 more
    Please suggest possible approach/solution
    Edited by: 942212 on Nov 23, 2012 8:03 PM
    Edited by: 942212 on Nov 23, 2012 10:56 PM

    Just to confirm, can you check if you have provided the class path in other adapters also. Cuz you are getting ClassNotFound exception which can only happen if you dont provide the class path to AdvJDBCColumnHandler.jar.
    HTH
    --Pravin                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • Preview issue in ATG-Endeca integration case of CRS at Endeca side

    I'm using ATG 10.1.2 and Endeca with Experiece Manager 3.1.1, both are the most current version coming out at the begining of this new year 2013.
    I followed the documents and deployed the Commerce Reference Store (Known as CRS) with option of Endeca integration. Now everything seemed to be ok, and at Endeca side, we could find deployed application of "CRS", and also we could find pages configured in Experience Manager.
    But problems come unexpectly. I just configured the preview fuction for both ATG and Endeca. According to CIM, I believe I've configured them correctly, because I got the result that Preview function acts normal at ATG side with BCC. However, once I try to use preview function at Endeca side, firstly a new browser pops up to show the page of CRS, and then a message pops up said: "Error: Your site is not cofigured for Preview correctly. Please contact your administrator."
    Why?
    And what is the place of log file concerned with this issue could I refer to?

    Solved!!
    After indicated "ATGProduction" for ear file name to assemble, I entered the menu below:
    [D] Deploy Production with a Server Lock Manager ATGProduction.ear to
    Weblogic Online - Done
    [R] Register Datasources on Weblogic Online - Done
    [A] Add database driver to app server classpath - Done
    [P] Post Deployment Actions on Weblogic Online - Done
    [E] Edit runAssembler arguments
    *[O] Configure Another Server Instance
    > e
    Choose e, means that to Edit runAssembler arguments, which I believe is the key point to access the layer setting for EndecaPreview.
    Then the menu shows as below:
    -------APPLICATION ASSEMBLY OPTIONS---------------------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    Choose Application Assembly Options: (* = Currently selected )
    [1] -pack
    [2] -standalone
    [3] -overwrite
    [4] -collapse-class-path
    [5] -jardirs
    [6] -verbose
    [7] -classesonly
    [8] -displayname
    [9] -liveconfig
    [10] -add-ear-file
    [11] -context-roots-file
    [12] -dynamo-env-properties
    [13] -exclude-acc-resources
    [14] -nofix
    [15] -prependJars
    [16] -run-in-place
    [17] -layer
    [18] -distributable
    [D] Done
    Select zero or more > 17
    At here, we choose -layer to config, and do process as below:
    -------APPLICATION ASSEMBLY OPTION VALUES---------------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    Enter values for -layer (separated by space) : > EndecaPreview
    After all configuration above and ear file redeployed to middleware, I now can access Preview function at Endeca Side !!

  • Oracle endeca studio application creation issue

    I have installed oracle endeca 3.1 solution on my desktop but i am not able to create application using endeca studio from excel upload. It shows excel data in preview and fields as well. But it gets stuck in create application page. Please help in resolving this issue.

    Hi,
         I have had this before and sometimes it can be that the Excel spreadhseet has formula, split screen, colours or anything else odd, please copy and paste values and take any split screen or colour off and try again, it usually works for me.
    Regards John

  • Problem with: wildcard search in Endeca with Russian language, or adding custom stemming dictionary

    Hi endeca-gurus. I need your assist in typeahead functionality to implement it with endeca (also we should able to search within * from search input-field). So, per documentation, OLT doesn't support wild card search, but latin-1 does it. So,  I tried to switch to Latin-1, but it doesn’t work…maybe I performed some mistakes :
    1.created file stemming file named ru_word _ forms _collection.xml and added it to the MDEX..\conf\stemming\custom directory:
    <?xml version="1.0"?>
    <!DOCTYPE WORD_FORMS_COLLECTION SYSTEM "word_forms_collection.dtd">
    <WORD_FORMS_COLLECTION>
      <WORD_FORMS>
        <WORD_FORM>ноу</WORD_FORM>
        <WORD_FORM>ноут</WORD_FORM>
        <WORD_FORM>ноутб</WORD_FORM>
        <WORD_FORM>ноутбу</WORD_FORM>
        <WORD_FORM>ноутбук</WORD_FORM>
      </WORD_FORMS>
      <WORD_FORMS>
        <WORD_FORM>sm</WORD_FORM>
        <WORD_FORM>sma</WORD_FORM>
        <WORD_FORM>smar</WORD_FORM>
        <WORD_FORM>smart</WORD_FORM>
      </WORD_FORMS>
    </WORD_FORMS_COLLECTION>
    2. set USE _STATIC _WORDFORMS="TRUE" in <appname>.stemming.xml;
    <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
    <!DOCTYPE STEMMING SYSTEM "stemming.dtd">
    <STEMMING>
    <STEM_RU ENABLE="TRUE" USE_STATIC_WORDFORMS="TRUE"/>
    </STEMMING>
    3. run baseline_update script
    4. try to search with params in endeca_jspref:
    N=0&Ntk=All&Ntt=ноут*&Nty=1&D=ноут*&Ntx=mode+matchall&Dx=mode+matchall
    And search result is zero.. ((
    What the encoding should be for the edited files? any other suggestions for doing it?
    and, common question : willl endeca support wildcard search for russian in close future??

    Did you enable the dimension for wildcard search?  In dev studio, in the dimension pane there is a button called configure search, click it and check the wildcard search checkbox in the dialog.  I think you may have the stemming entry right but as OLT is fairly new I have not had a chance to test changing the default analyzer as yet. If my suggestion does not work or you have already applied the wildcard flag then I will dig a little deeper.
    best
    Terry

  • Issues on server instance restart for endeca

    Hi,
    We are using endeca as a search engine and jboss as the app server for our application,when we restart the jboss instance we are getting following error only on few instance (out of 6 instance in the cluster only 2 or 3).
    2012-05-01 06:39:32,456 ERROR [nucleusNamespace.atg.dynamo.servlet.dafpipeline.DynamoServlet]
    javax.servlet.jsp.JspException: org.apache.jasper.JasperException: javax.el.ELException: Error reading 'defaultSortUrl' on type com.endeca.soleng.uiComponentLibrary.web.urlFormatter.components.MetaInfoComponentUrl
         at org.apache.jsp.tag.web.include_tag.doTag(include_tag.java:124)
         at org.apache.jsp.layout.VitaminShoppeLayout_jsp._jspx_meth_cartridges_005finclude_005f2(VitaminShoppeLayout_jsp.java:694)
         at org.apache.jsp.layout.VitaminShoppeLayout_jsp._jspx_meth_c_005fforEach_005f2(VitaminShoppeLayout_jsp.java:662)
         at org.apache.jsp.layout.VitaminShoppeLayout_jsp._jspx_meth_c_005fotherwise_005f3(VitaminShoppeLayout_jsp.java:572)
         at org.apache.jsp.layout.VitaminShoppeLayout_jsp._jspx_meth_c_005fchoose_005f3(VitaminShoppeLayout_jsp.java:513)
         at org.apache.jsp.layout.VitaminShoppeLayout_jsp._jspService(VitaminShoppeLayout_jsp.java:120)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:687)
         at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590)
         at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505)
         at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968)
         at org.apache.jsp.tag.web.include_tag.doTag(include_tag.java:108)
         at org.apache.jsp.results_jsp._jspx_meth_cartridges_005finclude_005f0(results_jsp.java:125)
         at org.apache.jsp.results_jsp._jspService(results_jsp.java:101)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:687)
         at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590)
         at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505)
         at atg.servlet.WrappingRequestDispatcher.include(WrappingRequestDispatcher.java:94)
         at atg.servlet.ServletUtil.invokeInclude(ServletUtil.java:3316)
         at atg.taglib.dspjsp.IncludeTag.doEndTag(IncludeTag.java:567)
         at org.apache.jsp.search.query_005fnew_jsp._jspx_meth_dsp_005finclude_005f2(query_005fnew_jsp.java:483)
         at org.apache.jsp.search.query_005fnew_jsp._jspService(query_005fnew_jsp.java:206)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:687)
         at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590)
         at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505)
         at atg.servlet.WrappingRequestDispatcher.include(WrappingRequestDispatcher.java:94)
         at atg.taglib.dspjsp.IncludeTag.doEndTag(IncludeTag.java:585)
         at org.apache.jsp.en.query_jsp._jspx_meth_dsp_005finclude_005f0(query_jsp.java:134)
         at org.apache.jsp.en.query_jsp._jspService(query_jsp.java:91)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:687)
         at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:469)
         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403)
         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
         at com.endeca.content.reference.Controller.doGet(Controller.java:230)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
         at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
         at org.jboss.web.tomcat.service.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:97)
         at org.jboss.web.tomcat.service.session.JvmRouteValve.invoke(JvmRouteValve.java:84)
         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
         at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
         at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437)
         at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381)
         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
         at java.lang.Thread.run(Thread.java:662)
    Caused by: org.apache.jasper.JasperException: javax.el.ELException: Error reading 'defaultSortUrl' on type com.endeca.soleng.uiComponentLibrary.web.urlFormatter.components.MetaInfoComponentUrl
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:431)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:687)
         at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590)
         at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505)
         at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968)
         at org.apache.jsp.cartridges.ResultsList_jsp._jspx_meth_dsp_005foparam_005f0(ResultsList_jsp.java:297)
         at org.apache.jsp.cartridges.ResultsList_jsp._jspx_meth_dsp_005fdroplet_005f0(ResultsList_jsp.java:229)
         at org.apache.jsp.cartridges.ResultsList_jsp._jspService(ResultsList_jsp.java:118)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:687)
         at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590)
         at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505)
         at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968)
         at org.apache.jsp.tag.web.include_tag.doTag(include_tag.java:108)
         ... 86 more
    Caused by: javax.el.ELException: Error reading 'defaultSortUrl' on type com.endeca.soleng.uiComponentLibrary.web.urlFormatter.components.MetaInfoComponentUrl
         at javax.el.BeanELResolver.getValue(BeanELResolver.java:66)
         at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53)
         at org.apache.el.parser.AstValue.getValue(AstValue.java:118)
         at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
         at org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:928)
         at org.apache.jsp.components.SortOptions_jsp._jspx_meth_c_005fif_005f0(SortOptions_jsp.java:148)
         at org.apache.jsp.components.SortOptions_jsp._jspService(SortOptions_jsp.java:117)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)
         ... 111 more
    it is not constant on any specific instance it will switch between different instance on each restart.

    Hi Mike,
    Sorry for the late response. Probably you have already solved the issue.
    Anyway, look in the Windows Registry for SAP keys and delete then. A good place to start is "<i>My Computer\HKEU_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services</i>".
    Don't forget to backup the registry before any change.
    Hope this help.
    Cheers,
    Marcelo

  • Endeca 3.1.2 ResultsList Cartiridge issue with Ntt params

    ATG 10.2 integration with Endeca 3.1.2 is used for the following example.
    The product listing page contains products which are rendered by the ResultsList cartridge.
    This cartridge contains the Boost and Bury editor as well as the Default Sort option.
    The users lands on product listing page by clicking on the sub category SEO links from the Global header.
    The mapping of SEO URLs to direct URLs is achieved through urlrewrite.xml and gets mapped to the following pattern
    /browse/category.jsp?categoryId=$2&amp;contentKey=$2&amp;dimVal=$3&amp;N=$3&amp;Ntt=*</to> </rule>
    The ResultsList cartridge is returning results when the converted URL contains parameter Ntt=*.
    If the URL contains the Ntt parameters then Boost and Bury as well as the Default Sort option does not work.
    We had verified from the Discover application, that the calls to the Product listing pages do not need the Ntt parameter in the URL.
    We also observed that on adding Ntt=*, endeca treats this query has a search query rather than the navigation query.
    Kindly let us know in case if anybody faced this issue and has a fix for this.

    Hi,
    You will get above error due to rollup key defined in the OOTB CRS application but not in the endeca pipeline pushed. Search for DefaultFilterState.properties/FilterState.properties component in dyn/admin where you will see the property as below
    rollupKey = product.repositoryId
    Now question is, if you have requirements to use rollup key then create a layered DefaultFilterState.properties/FilterState.properties component in ATG project and overrirde the rollupKey property value to the appropriate rollup attribute enabled property defined in the Endeca pipeline.
    If you just want to by pass this error then create a layered FilterState.properties component in ATG project and override the rollupKey property value to empty
    Example: rollupKey=
    Hope this helps.
    Thanks,
    Ravi

  • Endeca Server performance issue: dgraph is slow and not always available

    Hi, I'm experiencing a problem with Endeca Server. It's very slow and the dgraph process takes about 97% of the cpu without doing queries.
    When I try to open the Studio Page, the cpu utilization of the dgraph process increases up to 200%, and if I try to launch a simple query from Integrator the result is:
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
         <env:Header/>
         <env:Body>
              <env:Fault>
                   <faultcode>env:Server</faultcode>
                   <faultstring>Error contacting the conversation service on data store 'SocialIDData' at port 7011: Error parsing data version from DGraph response.</faultstring>
                   <detail>
                        <ns2:Fault xmlns:ns2="http://www.endeca.com/MDEX/conversation/2/0" xmlns:ns3="http://www.endeca.com/MDEX/lql_parser/types"/>         
                   </detail>
              </env:Fault>
         </env:Body>
    </env:Envelope>
    If I try to ping the Data Store by visiting the url http://192.168.2.16:7001/endeca-server/admin/SocialIDData?op=ping sometimes the response is positive, and sometimes it's negative.
    I've also checked the log file in ${ENDECA_SERVER_DOMAIN}/EndecaServer/logs/SocialIDData.out and I've found that message:
    MALLOC:   4656726016 ( 4441.0 MB) Heap size
    MALLOC:   4617801000 ( 4403.9 MB) Bytes in use by application
    MALLOC:     23912448 (   22.8 MB) Bytes free in page heap
    MALLOC:      2146304 (    2.0 MB) Bytes unmapped in page heap
    MALLOC:      4865568 (    4.6 MB) Bytes free in central cache
    MALLOC:       198144 (    0.2 MB) Bytes free in transfer cache
    MALLOC:      7802552 (    7.4 MB) Bytes free in thread caches
    MALLOC:        27450              Spans in use
    MALLOC:            7              Thread heaps in use
    MALLOC:     19922944 (   19.0 MB) Metadata allocated
    MALLOC:         4096              Tcmalloc page size
    Endeca fatal error detected in dgraph.
    Segmentation violation detected.
    testbi.localdomain:/u01/app/oracle/Middleware/user_projects/domains/endeca_domain/EndecaServer/logs
    Register state:
    Stack trace:
    Please report this problem to Endeca and include the following information
      1. Endeca software version number
      2. Operating system, operating system version, and hardware platform
      3. Any other information that you can provide (including core files)
      4. The contents of this message
    Process map:
    00400000-049b4000 r-xp 00000000 fd:04 2590868                            /u01/app/oracle/Middleware/EndecaServer7.5.1_1/endeca-server/dgraph/bin/dgraph
    04bb4000-04c11000 rw-p 045b4000 fd:04 2590868                            /u01/app/oracle/Middleware/EndecaServer7.5.1_1/endeca-server/dgraph/bin/dgraph
    04c11000-04c69000 rw-p 00000000 00:00 0
    As you can see at rows 16-17-18 that's a problem with the dgraph, but I have no idea on how resolve it.
    My system configuration is:
    OS: Oracle Linux 6
    OEID 3
    Can anyone help me? Thank you.
    Samuele Scattolini

    Please contact Oracle Support at http://support.oracle.com for assistance.  Thanks.

  • OEID 3 - Endeca Server Installation Issue

    Helo,
    I am in the process of installing components of OEID 3 in my Windows7 machine.
    I installed Weblogic and ADF as per the instructions given here - http://docs.oracle.com/cd/E37502_01/server.751/es_install/toc.htm#Installing%20WebLogic%20Server%20and%20Application%20Developer%20Runtime
    I installed Endeca Server as per the instructions given here - http://docs.oracle.com/cd/E37502_01/server.751/es_install/toc.htm#Installing%20Oracle%20Endeca%20Server
    There is no error while installing the Endeca Server but the Oracle Home Size is only 44MB while it should be 470MB as per the instruction.
    The problem is while creating the WebLogic domain, Endeca Server is not appearing for selection.
    Did anyone get into similar situation? Is this related to Windows7? What am I missing?
    Thanks,
    VJ

    Hi VJ,
    Are you referring to this step in the installation procedure (Creating the WebLogic Domain for Endeca Server)?
    http://docs.oracle.com/cd/E37502_01/server.751/es_install/toc.htm#Creating%20the%20WebLogic%20domain%20for%20Endeca%20Server
    If so, this indicates that either the Endeca Server, or the ADF were not properly installed. Are you sure you are using the WLS and ADF packages as indicated in the documentation? Are you using Sun JDK 6?
    Julia

  • EID3.0 Endeca Server SSL disable issue

    Hi,
    I have installed EID3.0 on our server and the SSL was enabled. I built page based on this Endeca Server and it worked well.
    For testing the Java Client call, I need to disable the SSL.
    Today I updated the config file "EndecaServer.properties" under path "MW_HOME/user_projects/domains/endeca_domain/config" as below:
    endeca-require-https=false
    endeca-webserver-port=7001
    endeca-secure-mode=false
    And remove the SSL setting in "MW_HOME/user_projects/domains/endeca_domain/config/config.xml"
    But when I restart the weblogic and run "./endeca-cmd list-dd", it throws error as below:
    endeca-cmd encountered a problem.
    caused by:
    Error contacting the Endeca Server localhost:7001: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Bad response: 503 Service Unavailable from url http://localhost:7001/endeca-server/ws/manage
    caused by:
    javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Bad response: 503 Service Unavailable from url http://localhost:7001/endeca-server/ws/manage
    caused by:
    javax.xml.soap.SOAPException: Bad response: 503 Service Unavailable from url http://localhost:7001/endeca-server/ws/manage
    caused by:
    Bad response: 503 Service Unavailable from url http://localhost:7001/endeca-server/ws/manage
    Anyone know how to disable SSL for EID3.0? Must I reinstall it again?

    Try also clearing the following two EndecaServer.properties:
    endeca-ds-cert-file=
    endeca-ds-ca-file=
    Also don't forget to review your EndecaCmd.properties settings.

  • Endeca Reference application issue

    Hi,
    I am getting below message while deploying discover reference application.
    Found version 6.1 of the Endeca IAP installed in directory
    D:\Endeca\PlatformServices\6.1.3. If either the version or location are
    incorrect, type 'Q' to quit and adjust your ENDECA_ROOT environment variable.
    Press enter to continue with these settings.
    **Does any one know why this is coming??.**
    I have cross checked Endeca root directory and Platform service location. Both are same.
    Thanks.

    The new properties will have to be added to product-sku-output-config.xml, which went under /atg/commerce/search in 10.1.0 (the location might have changed in 10.1.1). Check the ATG Endeca Integration guide for exact steps.
    HTH,
    Pankaj.

  • Endeca - Root Category (Commerce Root) defined in BCC Issue

    Hi All,
    In BCC we have rootCateggory as commerce root and in that I have added the actual categories like Men, Women,Kids etc... and Sub categories in each Categories defined. Now when I index the merchandized category I am getting Commerce root added in the Product Category Hierarchy. How to get rid of Commerce root and make sure that all main categories like Men,Women etc.. fall under product.category instead of commerce root.
    Current state:
    product.category: Commerce Root > Womens > Sweaters > Cardigans
    Required:
    product.category: Womens > Sweaters > Cardigans
    Thanks,
    Ravi

    Hi Ravi,
    There is a property called 'excludedCategoryIds' in CategoryTreeService component. If you specify your 'Commerce Root' category id to 'excludedCategoryIds' property, then you will get your required hierarchy as follows, you will not get 'Commerce Root'.
    product.category: Womens > Sweaters > Cardigans
    Please let me know once if it works.
    Thanks and Regards,
    Dilroz

Maybe you are looking for

  • Help with HP printer all-in-one C4380

    hi,  Can anyone help me. My printer keeps saying that there is a paper jam. There isnt any paper in the printer. I can't get it to work. Many thanks, Yossi 

  • My iPhone has stopped charging and I can't get it to charge at all

    I tried to charge it yesterday it vibrated to tell me it was charging then suddenly stopped straight afterwards. I've tried all the apple troubleshooting guides and noticed that the red battery screen is flashing twice instead of three times so I don

  • Whats the best external drive setup for FCP and accompanying software?

    With all the external Hard Drives out there I am hoping that other users could suggest the best options when setting up FCP to work with an external drive. I am working with both SD and HD and am planning to use DVD Studio, Soundtrack Pro along with

  • WRTP54G

    My security key will not work anymore, and the wireless wont let me access. linlsys wants to charge me 29 bucks for the fix. Can anyone tell me how to reset the key phrase?

  • Form based on Procedure - coding methods

    I would like to create a Portal Form based upon a stored procedure. I can't seem to find any documentation which describes the necessary procedural functions. The form requires standard select, update, delete capabilities. How does that the procedure