...
| Info |
|---|
By default, the security settings in Jaggery prevents microsites from being accessed publicly even after being published. For more information please go to http://jaggeryjs.org/apidocs/jagconf.jag. The code related to the security settings will have to be manually removed before publishing it to enable public access once the microsite is published. For more information please go to http://jaggeryjs.org/apidocs/jagconf.jag. |
- On the My Items menu, click and open the microsite folder that needs to be published.
- In the microsite folder open the
jaggery.conffile in the text editor. Remove the following code and save the
jaggery.conffile.Code Block "securityConstraints" : [ { "securityConstraint" : { "webResourceCollection" : { "name" : "Test", "urlPatterns" : [ "/*"], "methods" : [ "GET", "POST", "PUT", "DELETE", "HEAD", "OPTIONS", "TRACE", "CONNECT", "PATCH"] }, "authRoles" : [ "private_mari"] } }]- On the My Items menu in the portal, click on the microsite folder that needs to be published.
- Click Publish.
The Published Settings page will appear. Select "microsite" as the Publish as option.
Dashboards too need to be published as microsites. The default value is microsites.Select the permission type allowed for this microsite.
Users who have the edit permission will be able to edit the microsite. However, the changes will only be visible to the user who made the changes and will not be visible publicly.- Enter a name for the microsite.
- Enter the microsite version.
- Enter the URL that will be used to publicly access the microsite.
- Enter a description on the microsite.
- Enter the URL of the thumbnail.
- Enter the URL of the image.
- Click Publish.