Skip to content

Custom Configuration Properties for Script Applications

Default Import Properties for Script Applications

When importing the Script Applications, only specific file types are allowed by default. These properties define which extensions can be uploaded as part of the application package, and each property is not case-sensitive.

Default properties

  • HTML files
    scriptportlet.import.extensions.Html=html,htm

  • Script files
    scriptportlet.import.extensions.Script=js

  • Style files
    scriptportlet.import.extensions.StyleSheet=css

  • Image files
    scriptportlet.import.extensions.Image=jpg,jpeg,gif,png,bmp

Important

With the recommended DXClient approach, file type management is handled differently. For example, support for SVG files is configured at the Web Content level, not through Script Application properties.
See Web Content Manager set SVG to disabled by default.

If you still need to allow uploading of SVG files (or other image types) to Web Content Manager (WCM), update the imageresourcecmpnt.allowedmimetypes property in the WCMConfigService service by using the WebSphere® Integrated Solutions Console.

Example: 

imageresourcecmpnt.allowedmimetypes=image/gif,image/png,image/jpeg,image/jpg,image/jpe,image/jfif,image/bmp,image/x-bmp,image/x-bitmap,image/x-xbitmap,image/x-win-bitmap,image/x-windows-bmp,image/ms-bmp,image/x-ms-bmp,application/bmp,application/x-bmp,application/x-win-bitmap,image/ico,image/svg+xml,image/tiff,image/tif,image/webp
For more details about configuring allowed image formats, see
Enable image formats in WCM
and WCMConfigService configuration reference.

Note on other file types

Afileresourcecmpnt

While images are explicitly managed through imageresourcecmpnt.allowedmimetypes, it is less clear how other file types (HTML, JavaScript, CSS) are controlled at the WCM level.
Logically, a similar property such as fileresourcecmpnt.allowedmimetypes should exist to manage these file types. However, the default Script Application import properties listed above remain as the primary way to manage HTML, script, and style files.

Best Practices for Overriding Properties

By default, you can upload only specific types of files by using the Script Application. The Script Application import feature does not scan uploaded files, therefore use caution before you include other file types as part of an import. If you want to add extra file types, or change any of the other properties, use the procedure given later.

These properties are specific to individual portals. Each virtual portal has its own settings. Therefore, you must override each virtual portal separately.

If you edit the Script Application Configuration Properties component directly in the Script Application Library web content library, your changes are overwritten when a new version of the library is installed, for example when you upgrade your portal installation. To avoid this issue, use the following measure, depending on the type of your HCL DX installation:

  • If your portal version includes a Web Content Manager license and the Web Content Authoring option for creating extra components, create a new text component for overriding properties. To do so, use the full procedure given later.

  • If you use a base portal installation without a HCL Web Content Manager license and with limited Web Content Manager support, you cannot create new components in the Web Content Authoring user interface. In this case, you can edit the default Script Application Configuration Properties component directly, and then update it again after upgrade as mentioned in step 4 of the procedure given later.

  • Add a text component that is called Script Portlet Override Properties in the Web Content Manager library Script Application Library.

    In this component, you can override any of the properties in the Script Application Configuration Properties component.

  • Copy the properties that you want to override from the Configuration Properties component to the Script Portlet Override Properties component.

  • Edit the properties that you want to change and save the file.

  • If you upgrade your portal to another version or with a Combined Cumulative Fix, check to see whether any items you overrode were changed by default. Change the text component and save the component.