bnee_1

JasperReports® Server 8.2.0May 8, 2023 JasperReports Server 8.2.0 adds these improvements: • JDK 17 Support Starting from JasperReports Server 8.2.0, JDK 17 is supported in Runtime mode, but only on Tomcat 9.0.x. • Report Splitting Users are now able to schedule a report in JasperReports Server that can be split into multiple pieces, and are then stored separately, or sent to different recipients based on report splitting markers found in the report itself. For more information, see the TIBCO JasperReports Server User Guide. • UI/UX Enhancements • Tool tip for calculated fields in Ad Hoc Designer. For more information, see the JasperReports Server User Guide. • Ability to close Editors and Viewers using a Close button. For more information, see the JasperReports Server User Guide and JasperReports Server Domains Guide. • Ability to navigate back from drill-down into parent report. A drill-down report contains a parent report and a sub-report. For more information about how to create them, see the JasperReports Server User Guide and Jaspersoft Studio User Guide. • Superuser ability to enable uploading .JAR files. By default, no one can upload or modify .JAR files for JDBC drivers from the UI. Now, the system administrator (superuser) can enable the setting and then upload or modify .JAR files. For more information, see the JasperReports Server User Guide. • Upgrade of Highcharts The Highcharts library is upgraded to version 10.1.0, which enables new breadcrumb navigation when drilling down interactively into chart data. The breadcrumbs appear automatically and let you navigate back to any previous level of drill down. In addition, overall chart behavior is more consistent with minor fixes to pie chart data levels, the order of fields in chart tooltips, and mouseover data in Visualize.js gauge charts. • XLSX Export Option An XLSX export option is now available in the Scheduler for running jobs with an XLS report. For more information, see the JasperReports IO User Guide, JasperReports Server REST API Reference, and the JasperReports Server User Guide. • Limiting Failed Login Attempts To prevent brute-force attacks against user and administrator accounts, the server can now lock an account after a configurable number of failed login attempts. The server now records failed login attempts and administrators may configure and set limit after which the account is disabled. An administrator must enable the account before it can be used again. Note: Only LDAP and External DB authentication are supported. CAS is not supported for JasperReports Server 8.2.0. For more information, see the JasperReports Server User Guide, JasperReports Server Administrator Guide, and the JasperReports Server Security Guide. • JasperReports Library Performance Improvements for Excel and CSV Output Formats The new version of JasperReports Library comes with a new property named 'net.sf.jasperreports.text.measurer.factory=naive', which enables skipping the measurement of string length for table and crosstab reports. This feature is particularly useful when exporting to data-centric formats such as CSV and Excel, where Excel has its own feature responsible for text measuring. However, when exporting to Excel, an additional property 'net.sf.jasperreports.export.xls.auto.fit.row=true' must be added if the cells in Excel are expected to grow vertically to fit their contents. Without this property, texts that would have normally stretched may not be fully visible in Excel, although the full text would still be present in the cell and accessible when the cell is selected. Skipping these calculations can significantly speed up the generation of output files, by more than 50%. However, it is recommended to use this property with caution, as it may affect other output formats that rely on pixel-perfect calculations, such as PDF or HTML. It is advisable to use this property only on a report level and for reports that will be solely exported to CSV or Excel. • New property resolveRuntimeAdhocFilterLabels Added to applicationContext-adhoc.xml A new property has been introduced in applicationContext-adhoc.xml > resolveRuntimeAdhocFilterLabels. This property resolves the inconsistency between Adhoc View Filters and Filters/Input Controls labels in dependent Adhoc Reports/Dashboards/Visualize where operators were not previously shown, and it is disabled by default. To have Adhoc Designer resolve Ad Hoc filter labels at runtime, set this property to true and restart the application server. Otherwise (with default setting), you will need to re-save all the AdHoc views in order for the operator to be displayed in the dependent report, dashboard and in Visualize. Note: If the property is set to true (which means the UI ignores any custom labels given by user on the UI) and the existing dashboard has 2 views/reports with the same filters name, the UI uses the label sent by the server. As a result, those filters will have the same labels. For example, creating new dashboard with Country filter for both will display them as Country and Country2. For more information, see the JasperReports Server Administrator Guide. • Hibernate and Spring Security Update • Configuration to allow Private Networks Access for Visualize.js applications In the latest version of Chrome, a new feature called Private Network Access (PNA) has been introduced. This feature requires websites (for example Visualize.js application) to obtain explicit permission from servers on private networks before sending arbitrary requests. To enable PNA, the new header Access-Control-AllowPrivate-Network, must be included in pre-flight requests. For more information on how to enable this feature, see the JasperReports Server Visualize.js Guide. • New Operating System Versions This release adds support for several new operating system versions: • Red Hat Enterprise Linux (RHEL) (64-bit) 8.7 • Microsoft Windows 11 Pro, Server 2022 • Apple MacOS 12.x • Ubuntu 20.04 LTS, 22.04 LTS • Fedora 34, 35 • New Application Server Versions This release adds support for several new third-party application server versions: • JBOSS EAP 7.2 • Oracle WebLogic 12.2.1.4, 14.1.1.0 • Jetty Version 9.4.45.v20220203 (JRIO Pro) • New Database Versions This release adds support for several new third-party database versions: • PostgreSQL 13, 14 • ElasticSearch 8.2.0 • AWS Athena 3 • AWS RDS - PostgreSQL 13, 14 • New Platform Versions This release adds support for several new platform versions: • Kubernetes 1.22.x • Openshift 4.5.x+ Changes in 8.2.0 Functionality• Simba drivers removed since JasperReports Server 8.2.0 Simba drivers have been removed from JasperReports Server. If you have any resources that use or depend on any of the following Simba Drivers: • athena-jdbc42 2.0.33.1003 • cassandra-jdbc42 2.0.13.1014 • impala-jdbc42 2.6.26.1031 • neo4j-jdbc42 • spark-jdbc42 2.6.22.1040 then you must manually install publicly available drivers (for example, Athena and Cassandra have the same Simba drivers publicly available). For other drivers, you must obtain the drivers which are recommended by the database vendor. After installing new drivers, update the resources in JasperReports Server to use the new drivers. • Hibernate Upgraded from 5.2 to 5.6 The path for hibernate.properties file is now changed to WEB-INF/classes. • Excel Export Option Changes In export options (from JasperReports Server Administrator Guide, Jaspersoft Studio) the old Excel format (.xls, .xls-Paginated) has been removed and replaced with a new format (.xlsx and .xlsx- Paginated). Also, metadata exporter format is added for Excel. • Ability to decide where SVG files will be placed This release introduces a new configuration property to control if generated HighCharts image has to be embedded into HTML output or to be available as a separate file attachment, when rest_v2/reportExecutions task is submitted with parameter {"interactive": false}. • Deprecation of sample themes Sample themes are deprecated and will be removed in the future releases. • Deprecation of Jaspersoft OLAP views In this release, OLAP views are being deprecated. Users who still use them are encouraged to migrate to AdHoc views that are based on Mondrian or XMLA connections, as these views will continue to receive full support. • Calculated fields with aggregate expressions behavior change If a calculated field contains an aggregate expression and is used in another aggregate expression, it will always be calculated in memory. With this release, there is no need to explicitly set the inMemory setting to true for such functions. • Recommended Deployment Architecture to Handle the Third Party Cookies Browsers Policy Reports Executions and Input Controls cache are no longer user-session dependent. If the recommended architecture is applied, then the Visualize application will continue to work even if your application and JasperReports Server are deployed on different servers. For more information, refer to the Jaspersoft Community article "Recommended Architecture to Handle Browser Third Party Cookies Policy." For more details: https://community.jaspersoft.com/documentation/tibco-jasperreports-server-release-notes JasperReports® Server 8.0.4April 25, 2023 JasperReports Server 8.0.4 is a maintenance release that addresses a driver update (Simba drivers removed from JasperReports Server Pro 8.0.4), and branding and copyright updates. All installations of 7.x and 8.0.x should upgrade to 8.0.4 as soon as possible. It is released in two formats: • As a cumulative service pack with patch files for the 8.0.x Commercial version. There is also a separate service pack for the Community version. • As a full binary WAR file that can be used to deploy JasperReports Server 8.0.4 from scratch or as an upgrade from any version 7.x directly to 8.0.4 (using samedb or newdb upgrade scripts). Changes in 8.0.4 FunctionalitySimba drivers are now removed from JasperReports Server If you have any resources that use or depend on any of the following Simba Drivers: • athena-jdbc42 2.0.33.1003 • cassandra-jdbc42 2.0.13.1014 • impala-jdbc42 2.6.26.1031 • neo4j-jdbc42 • spark-jdbc42 2.6.22.1040 then you must manually install publicly available drivers (for example, Athena and Cassandra have the same Simba drivers publicly available). For other drivers, you must obtain the drivers which are recommended by the database vendor. After installing new drivers, update the resources in JasperReports Server to use the new drivers. For more details: https://community.jaspersoft.com/documentation/tibco-jasperreports-server-release-notes JasperReports® Server 8.1.1December 13, 2022 JasperReports Server 8.1.1 is a maintenance release that addresses security vulnerabilities. All installations of 8.1.0 should upgrade to 8.1.1 as soon as possible. It is released in two formats: • As a cumulative service pack with patch files for the 8.1.0 Commercial version. There is also a separate service pack for the Community version. • As a full binary WAR file that can be used to deploy JasperReports Server 8.1.1 from scratch or as an upgrade from any version 8.0.x directly to 8.1.1. Changes in 8.1.1 Functionality• OLAP Views no longer supported. However, you can use OLAP connections and XMLA connections in AdHoc as before. • OLAP Scripts As of this release, the ability to use JavaScript as a formatter for values, members, etc. is now disabled by default. To enable it, edit /apache-tomcat/webapps/jasperserver-pro/WEB-INF/js.config.properties and set olap.mondrian.scripts.enabled to true. • Resolves CVE-2022-31197 vulnerability in pgjdbc driver (PostgreSQL JDBC driver) • Resolves CVE-2022-34169 vulnerability in Apache Xalan • Resolves CVE-2022-33980 vulnerability in Apache Commons2 • Resolves CVE-2022-42889 vulnerability in Apache Commons Text • Resolves CVE-2021-29489 vulnerability in HighCharts • Minor improvements requested by customers. For more details: https://community.jaspersoft.com/documentation/tibco-jasperreports-server-release-notes JasperReports® Server 8.0.3December 13, 2022 JasperReports Server 8.0.3 is a maintenance release that addresses security vulnerabilities. All installations of 7.x and 8.0.x should upgrade to 8.0.3 or 8.1.1 as soon as possible. It is released in two formats: • As a cumulative service pack with patch files for the 8.0.x Commercial version. • As a full binary WAR file that can be used to deploy JasperReports Server 8.0.3 from scratch or as an upgrade from any version 7.x directly to 8.0.3 (using samedb or newdb upgrade scripts). Changes in 8.0.3 Functionality• OLAP Views no longer supported. However, you can use OLAP connections and XMLA connections in AdHoc as before. • OLAP Scripts As of this release, the ability to use JavaScript as a formatter for values, members, etc. is now disabled by default. To enable it, edit /apache-tomcat/webapps/jasperserver-pro/WEB-INF/js.config.properties and set olap.mondrian.scripts.enabled to true. • Resolves CVE-2022-31197 vulnerability in pgjdbc driver (PostgreSQL JDBC driver) • Resolves CVE-2022-34169 vulnerability in Apache Xalan • Resolves CVE-2022-33980 vulnerability in Apache Commons2 • Resolves CVE-2022-42889 vulnerability in Apache Commons Text • Resolves CVE-2021-29489 vulnerability in HighCharts • Minor improvements requested by customers. • Fix JS-64375 The fix introduces the fallbackColumnWidth property in applicationContext-adhoc.xml to the bean tableDefaults. That is a fallback value in case of an attempt to set column width to zero (for example, by resource import). Must be set to 0 or greater. The default value is `-1` which disables the fallback. Also, the com.jaspersoft.ji.adhoc.AdhocColumn logger is available to trace the source of the zero value if set to debug level. • Fix for JS-65763 The fix introduces ability for Input Controls to use configurable`date.format`, `time.format` and `datetime.format` formats declared in the jasperserver_config.properties file. To enable feature: 1. Open `js.spring.properties` file. 2. Comment out `bean.calendarFormatProvider=isoCalendarFormatProvider` line. 3. Then, uncomment `bean.calendarFormatProvider=messagesCalendarFormatProvider` line. By default, Input Controls use previous behaviour and converts data with the standard ISO formats: • date: yyyy-MM-dd • time: HH:mm:ss • datetime: yyyy-MM-dd'T'HH:mm:ss • Fix JS-64844 There is a new option, inputControl.handler.values.caseSensitive, in js.config.properties to turn on/off sensitivity for input control and filter. This case insensitive option only works for case insensitive database and default value is "true". Setting inputControl.handler.values.caseSensitive to "false" will turn off sensitivity. • Fix JS-66815 Domain calculated fields that have Sum, Average, Min, Max, Range, Mode, or other aggregate functions and are used in Adhoc Total, Grand Total, or Summary results will be calculated in-memory due to SQL limitations. You can find all aggregated defined functions in applicationContext-el-operators.xml definitions. For more details: https://community.jaspersoft.com/documentation/tibco-jasperreports-server-release-notes

Issue:The TIBCO JasperReports® Server 7.2 Pro Source zip includes outdated catalogs for MySQL and PostgreSQL. This results in the wrong theme files being used on the server. When running any report, users will see misaligned toolbar menus and input boxes. When creating an ad hoc view, users will be unable to create pre-filters or change filter values in the designer. Resolution:To resolve this issue before installationDownload the WAR file distribution TIB_js-jrs_7.2.0_bin.zip and the source code package TIB_js-jrs_7.2.0_src.zip for the commercial version of TIBCO JasperReports® Server from TIBCO Technical Support (https://support.tibco.com). Copy the following catalogs from TIB_js-jrs_7.2.0_bin.zip/buildomatic/install_resources/export/ to TIB_js-jrs_7.2.0_src.zip/jasperserver/buildomatic/install_resources/export/ js-catalog-mysql-minimal-pro.zipjs-catalog-mysql-pro.zipjs-catalog-postgresql-minimal-pro.zipjs-catalog-postgresql-pro.zipThen, proceed with the instructions in the JasperReports® Server 7.2 Source Build Guide. To resolve this issue after installationDownload the WAR file distribution TIB_js-jrs_7.2.0_bin.zip from TIBCO Technical Support (https://support.tibco.com). Copy the following catalogs from TIB_js-jrs_7.2.0_bin.zip/buildomatic/install_resources/export/ to TIB_js-jrs_7.2.0_src.zip/jasperserver/buildomatic/install_resources/export/ js-catalog-mysql-minimal-pro.zipjs-catalog-mysql-pro.zipjs-catalog-postgresql-minimal-pro.zipjs-catalog-postgresql-pro.zipRun "js-ant create-load-js-db-pro" Warning: This will delete and re-create the JasperReports Server database.

Issue DescriptionI have an existing ReportUnit resource that I would like to modify using the REST v2 API. When I attempted to update the "resources" field of this ReportUnit like this: [toc]{ "version":0, "patch":[ { "field":"resources", "value":"[uRI OF RESOURCE HERE]" } ]}[/code]I got the error: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <errorDescriptor> <errorCode>patch.failed</errorCode> <message> EL1010E:(pos 0): Field or property resources cannot be set on object of type com.jaspersoft.jasperserver.dto.resources.ClientReportUnit </message> <parameters> <parameter> resources = "[uRI OF RESOURCE HERE]" </parameter> </parameters></errorDescriptor>[/code]ResolutionUse this JSON syntax: { "version":0, "patch":[ { "expression": "files.put('test_file', new com.jaspersoft.jasperserver.dto.resources.ClientReference().setUri('/public/Samples/Resources/Images/ico-library.jpg'))" } ]}[/code]"files" is used instead of "resources" because ClientReportUnit doesn't have any "resources" field. It has a "files" field, which is java.util.Map, and it's being mapped to "resources" for convenience. You can look in our jasperserver-dto package to see the actual Java structure of classes to patch. The PATCH Method was introduced in JasperReports Server v5.5, and it is discussed in the Web Services Guide PDF that comes with JasperReports Server. Ref. Case 00057949

Issue DescriptionJobs are segregated to child jobs and managed by a single parent job. The parent job is checking if the child jobs run were successful or failed and will send emails to respective users. If a child job fails, it will trigger its own tlogcather or tassertcather and perform its respective logging job in the child job itself, but the parent is unable to perform its "OnSubJobError" trigger to follow up the email actions. The desired behavior is that the parent job should know if the child jobs run were successes or failures with the trigger of "OnSubJobOK" and "OnSubJobError". ResolutionWhen you use an OnSubJobError link in a child job, it is the result of the processing after that link that is passed back to the parent. So, no problem logging the error in the child job means no error in the tRunJob in the parent. To force an error in the tRunJob in the parent, you need a tDie as the last component after logging the error in the child job. Ref. Case 00058362

Issue DescriptionI modified the WEB-INFapplicationContext-externalAuth-LDAP-mt.xml file so that I could login to JasperReports Server using users from my LDAP server. After saving the file and restarting JasperReports Server, trying to login with an LDAP user failed. The error was: [toc]HTTP Status 500 - Error during synchronization type Exception report message Error during synchronization description The server encountered an internal error that prevented it from fulfilling this request. exception org.springframework.security.authentication.AuthenticationServiceException: Error during synchronization com.jaspersoft.jasperserver.api.security.externalAuth.ExternalDataSynchronizerImpl.synchronize(ExternalDataSynchronizerImpl.java:106) ... root cause java.lang.RuntimeException: com.jaspersoft.jasperserver.api.JSException: jsexception.folder.too.long.uri com.jaspersoft.jasperserver.multipleTenancy.security.externalAuth.processors.ldap.LdapExternalTenantProcessor.process(LdapExternalTenantProcessor.java:74) ... ResolutionThe full distinguished name for the user was very long, and it included severals organizational units (ou) and domain components (dc). By default, when an external user logs into JasperReports Server for the first time, it is created in an organization tree that corresponds to the distinguished name. In this case, the organization tree was so large that their resultant URIs caused the exception. The solution was to shrink the organization tree by setting excludeRootDN to "true" in WEB-INFapplicationContext-externalAuth-LDAP-mt.xml and specify the baseDN (which we wanted excluded from the organization tree) in the ldapContextSource's constructor-arg value. Another way to shrink the organization tree would be to modify the ldapExternalTenantProcessor's organizationRDNs property by removing values you do not want to include in the organization tree. Ref. Case 00059296

Issue DescriptionAfter not using JasperReports Server for a couple of hours, I tried to access the JasperReports Server login page, and it took over a minute to finish loading. After this, JasperReports Server has normal response times until another long period of inactivity. The error in the logs was: java.util.prefs.FileSystemPreferences syncWorld WARNING: Couldn't flush user prefs: java.util.prefs.BackingStoreException: Couldn't get file lock. java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode WARNING: Could not lock User prefs. Unix error code 2. ResolutionThis appears to be due to the Java process not being able to write to the user root directory. The solution is to add the folder /.java/.userPrefs/ in the tomcat directory and define tomcat7 as the owner for all objects in the tomcat directory. Ref. Case 00059447

Issue DescriptionI am using an Oracle database for my reports, and one of the time fields is returning the wrong values when I run the report in my local time zone. The times are stored in UTC in the database, and I am located in CET (Winter)/CEST (Summer). The JasperReports Server is installed in CET/CEST, and I choose the time zone on the JasperReports Server login page as Europe/Paris. The data source configuration in JasperReports Server has "Use database settings" for the time zone. The data type for this field is TIMESTAMP. ResolutionCET is UTC+1 in the Winter, and CEST is UTC+2 in the Summer. Since you specified "Use database settings", then the TIMESTAMP values coming from the database will be trusted, and JasperReports Server will internally treat these values as the same time zone as JasperReports Server (CET/CEST). So, if the TIMESTAMP value from the database has 12:37:00, then JasperReports Server treats this value as 12:37:00 CET/CEST. So, if you select CET as the time zone on the login page, and it's Winter, you will see 12:37:00 in your report. The behavior would differ if the field's datatype was TIMESTAMP WITH TIME ZONE. Then, if you specified "Use database settings" for the data source setup, the TIMESTAMP WITH TIME ZONE values coming from the database would have a time zone value in them and JasperReports Server would convert them to the time zone JasperReports Server is in (CET/CEST). So, 12:37:00 UTC in the database would be treated as 13:37:00 CET or 14:37:00 CEST in JasperReports Server. Then, if you login with CET time zone, you'd see 13:37:00 in the Winter. For this scenario, you could do either of the following: Change the field's data type to be TIMESTAMP WITH TIME ZONE and leave "Use database settings" for the data source's time zone property Leave the field's data type as TIMESTAMP and change the data source's time zone to be "UTC". Ref. Case 00054352

Issue DescriptionOn my AWS BYOL environment, the new jasperserver.license in the JasperReports Server's WEB-INF directory is not recognized. I see this error when I try to login to JasperReports Server: [toc]License Failed Invalid license. License file /usr/share/tomcat7/webapps/jasperserver-pro/WEB-INF/jasperserver.license was not found. Please contact Jaspersoft Technical Support."[/code]ResolutionModified the permissions with chmod for the jasperserver.license to allow every user to read it. Then, restarted Tomcat. Ref. Case 00059760

Issue DescriptionI have installed a new JasperReports Server and imported the repository backup from an older version of JasperReports Server. When I edit the imported domains, then click on the domain designer link, I get the error: [toc]Cannot get database meta info : /public/Data_Sources/MyDataSource java.lang.IllegalArgumentException: getObjectType for javaType: returned null at com.jaspersoft.commons.dataset.expr.ObjectTypeMapper.getObjectType(ObjectTypeMapper.java:79)[/code]MyDataSource is an Oracle data source. ResolutionIt was determined that the WEB-INFapplicationContext-semanticLayer.xml had been modified in the source environment to map Oracle's clob data type to java.lang.String. However, the target environment had not provided that mapping, yet. Changing the mapping from this: <entry key="CLOB" value=""></entry>[/code]to this: <entry key="CLOB" value="java.lang.String"></entry>[/code]Saving the file and restarting the server resolved the issue. Ref. Case 00059792

Issue Description:How can we hide the "Save Ad Hoc View As..." option from users that have Read Only permission for that Ad Hoc View? Resolution:If you give a user role Read Only access to an Ad Hoc View, users of that role type can't choose "Save Ad Hoc View" or "Save Ad Hoc View and Create Report." However, they can select "Save Ad Hoc View As..." If you want to disable "Save Ad Hoc View As..." as an option for those users, you will need to modify these 4 files: WEB-INF/actionModel-adhocChart.xmlWEB-INF/actionModel-adhocCrosstab.xmlWEB-INF/actionModel-adhocIntelligentChart.xmlWEB-INF/actionModel-adhocTable.xmlReplace this line: <simpleAction labelKey="ADH_037_MENU_SAVE_REPORT_AS" action="designerBase.handleSaveAs"/>[/code] with these lines: <condition test="getIsNotWritable"> <simpleAction labelKey="ADH_037_MENU_SAVE_REPORT_AS" disabled="disabled"/></condition><condition test="getIsWritable"> <simpleAction labelKey="ADH_037_MENU_SAVE_REPORT_AS" action="designerBase.handleSaveAs"/></condition>[/code]Save the xml files and restart the server. Ref. Case #00047764

Creating a domain is a multipart request. Not every REST client handles multiple attachments equally, so the following steps are for RESTClient 3.2.1. A domain will have a schema xml file and a data source at minimum. It may also have a security file and any number of resource bundle properties files. These should all be specified in the resource decriptor used in the REST request. The below steps use the sample Supermart Domain (/public/Samples/Domains/supermartDomain) that comes with JasperReports Server, and it uses the sample Foodmart JNDI data source (/public/Samples/Data_Sources/FoodmartDataSourceJNDI). The schema xml file, security file, and bundle properties file belong to that existing domain, and the resource descriptor was modified to create a domain with a new name (createdSupermartDomain) in the repository directly under the Public folder. Start the RESTClient 3.2.1 and type in the URL: http://127.0.0.1:8080/jasperserver-pro/rest/resource Under the Method tab, select HTTP Method: PUT [screenshot 1] Under the Body tab, click the String or File buttons to attach each file to the request (see screenshots 2a - 2d below): String, text/plain; charset=UTF-8, ResourceDescriptor, <location_in_file_system> File, application/xml; charset=UTF-8, /public/createdSupermartDomain_files/schema.xml, <location_in_file_system> FIle, text/plain; charset=UTF-8, /public/createdSupermartDomain_files/supermartDomain_domain_security, <location_in_file_system> File, text/plain; charset=UTF-8, /public/createdSupermartDomain_files/supermart_domain.properties, <location_in_file_system> *Notice that the path for the files must have "_files" appended to the name of the Domain. [screenshot 2a] [screenshot 2b] [screenshot 2c] [screenshot 2d] Under the Auth tab, select BASIC, then enter the username and password. [screenshot 3] Send the request, and the HTTP Response should show: Status: HTTP/1.1 201 Created.