SAS-config-directory\Lev1\CustomAppData\testportlet
directory.
The scripting facility should be used for portlet development because
it provides a process that integrates your custom portlets with the
SAS versioned JAR repository.
SAS-config-directory\Lev1\CustomAppData\
directory.
Use the portlet name for the configuration directory name.
C:/SAS/EBI/Lev1/CustomAppData/SampleHelloUserJSR168Portlet
).
cfg createJSR168PortletDirectories
-Dmetadata.connection.passwd="unrestricted-user-password"
where unrestricted-user-password is
the password for the unrestricted user.
SAS-config-directory/Levn/CustomAppData/SampleHelloUserJSR168Portlet
to
ensure that the script completed successfully.
source-directory Configurable ears archive-name META-INF wars archive-name WEB-INF Picklists wars archive-name Static ears archive-name META-INF lib wars archive-name jsp source WEB-INF classes spring-config
\Configurable
and \Static
directory
hierarchies are used to store the files needed to create PAR, EAR,
and WAR files for the portlet in the same directory structure as the
PAR, EAR, and WAR files themselves. The \Configurable
hierarchy
is used for files in which values are substituted from the portlet
configuration file when the portlet is built. The \Static
hierarchy
is used for files that do not require substitution. The \Picklists
directory
hierarchy is used to store picklist files that specify which of the
JAR files from the SAS versioned JAR repository need to be included
in the portlet. The \Static\lib
directory
is used to store additional JAR files needed at compile time.
SAS-configuration-directory/Lev1/Web/Applications/SASBIPortlets4.4/PortletDeploymentTool/src
directory.
Locate the configurable value @webappsrv.server.name@ and replace
it with the name of the web application server where SAS Information
Delivery Portal is assigned. By default, the server name is SASServer1.
SAS-config-directory/Levn/Web/Staging/
.