[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]


Installing Enterprise Service Portals

Tasks to install an enterprise service portal are:

  1. Preparing the Web Applications for Customization
  2. Configuring Connections to the Directory
  3. (Enterprise Manager Portal only) Configuring Deployment Settings for Enterprise Manager Portal
  4. Deploying the Enterprise Service Portals
  5. Configuring the URL for an Enterprise Service Portal

After you install an enterprise service portal:

Preparing the Web Applications for Customization

When customizing the Web applications, copy the WAR files to a temporary folder and work in that folder.

To copy the WAR file to a temporary folder:

  1. Login as root or another authorized user.
  2. Create a temporary folder in which you will work on the WAR file. For example:
  3. mkdir tempWar
    
    
    
  4. Access the temporary folder. For example:
  5. cd tempWar
    
    
    
  6. Copy the WAR file to the temporary folder.
  7. cp /cdrom/cdrom0/webapp/<filename>
    
    
    

<filename>—Name of the WAR file; for example, entmgr.war

Configuring Connections to the Directory

To configure a connection between the Web application and the directory that contains the configuration for the enterprise service portal:

  1. Access the temporary folder to which you copied the WAR file.
  2. cd tempWar
    
    
    
  3. Extract the boot.props file from the WAR file.
  4. jar xvf <filename> WEB-INF/boot.props
    
    
    

<filename>—Name of the WAR file; for example, entmgr.war

  1. Edit the boot.props file with any text editor; use the following property descriptions as guidelines.
  2. Replace the boot.props file in the WAR file.
  3. jar uvf <filename> WEB-INF/boot.props
    
    
    

Initialization Properties for Enterprise Service Portals

In the boot properties file for an enterprise service portal, you can modify the following fields.

Config.java.naming.provider.url

Config.java.naming.security.credentials

Config.java.naming.security.principal

Config.net.juniper.smgt.des.backup_provider_urls

Config.net.juniper.smgt.des.<propertySuffix>

Config.net.juniper.smgt.lib.config.staticConfigDN

Config.EASP.namespace

Configuring Deployment Settings for Enterprise Manager Portal

You configure deployment settings for Enterprise Manager Portal. You do not need to configure deployment settings for the sample Enterprise Service Portal or NAT Address Management Portal.

To configure deployment settings for Enterprise Manager Portal:

  1. Access the temporary folder to which you copied the WAR file.
  2. cd tempWar
    
    
    
  3. Extract the web.xml file from the WAR file.
  4. jar xvf entmgr.war WEB-INF/web.xml
    
    
    
  5. Edit the web.xml file in the entmgr.war file with any text editor; use the following property descriptions as guidelines.

This file specifies which applications Enterprise Manager Portal displays and specifies how to generate e-mails when IT managers request public IP addresses through this enterprise service portal.

  1. Replace the web.xml file in the WAR files.
  2. jar uvf entmgr.war WEB-INF/web.xml
    

Deployment Properties for Enterprise Manager Portal

In the web.xml deployment properties file for Enterprise manager Portal, you can modify the following fields.

showBasicBandwidthOnDemand

To make class of service (CoS) services available, BoD services and basic BoD services must be enabled. If both are enabled, IT managers must select a basic BoD service before they can subscribe to BoD services.

showBandwidthOnDemand

showFirewall

If you set showFirewall to True and statelessFirewall to False, the portal provides support for stateful firewalls on JUNOS routing platforms.

statelessFirewall

When you set statelessFirewall to True, the Firewall tab but not the Application tab appears in Enterprise Manager Portal.

You can configure either stateless firewalls or stateful firewalls from Enterprise Manager Portal. If you set showFirewall to True and statelessFirewall to False, the portal provides support for stateful firewalls on JUNOS routing platforms.

showNat

showSchedule

showVpn

showExtranet

junoseCompatibleBoD

Consider that if both JUNOS routing platforms and JUNOSe routers exist in an enterprise's network, IT managers who are using the enterprise service portal to configure their SRC-managed environment do not know which routers are JUNOSe routers and which are JUNOS routing platforms.

machineReadableNotifications

renotificationInterval

addressManagerUrl

http://<host>:<port><path>

mail.smtp.host

notificationFrom

notificationTo

notificationSubject

renotificationSubject

notificationText

maxIpPoolSize

Deploying the Enterprise Service Portals

The way you deploy the enterprise service portals depends on your Web application server.

If you are using a Web application server other than JBoss, see the documentation for your Web application server for information about the deployment.

For information about installing the enterprise service portal inside the JBoss Web application server, see SRC-PE Getting Started Guide, Chapter 33, Installing Web Applications.

Configuring the URL for an Enterprise Service Portal

By default, the name of the WAR file determines the URL that you use to access the enterprise service portal. For example, if the name of the WAR files is entmgr.war, the URL for the enterprise service portal is http://<host>:<port>/entmgr.

If you want use a different URL, you must modify the relevant configuration file for your Web application server. For information about this task, see the documentation for your Web application server.


[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]