Configuring Portal-Side Settings
Use
To enable effective communication between the portal and the.NET runtime environment, you have to configure a number of portal-side settings.
In a clustered environment, multiple portal server nodes communicate with multiple .NET runtime server nodes. The following procedure describes how to configure their communication parameters.
Procedure
...
...
1. Log on to the portal as a system administrator.
2. In top-level navigation, go to System Administration → Support.
3. In the Support Desk iView, displayed in the work area, click Portal Runtime for Microsoft.NET.
4. In the displayed Portal Support Desk:Portal Runtime for Microsoft .NETpage, click .NET Runtime Service Configuration.
5. In the .NET Runtime Service Configuration page that opens, configure the portal-side settings as described below.
Portal Servers
Configure each portal server node to enable communication with a .NET runtime server node:
Element |
Description |
Portal Node |
The ID property of a portal server node. If this is a single node, leave empty; otherwise, specify a different <Portal Server ID> for each portal node. |
Host: Port |
The host and port on which the portal server node listens for a .NET runtime server connection: <Portal Server1 Host>:<Portal Server1 Port for .NET>. If there are multiple portal nodes, specify a different combination of host and port for each node. Default: localhost:8051 (valid for a single portal node) Example: · Single node Portal Node Host: Port localhost:8051 · Multiple nodes Portal Node Host: Port 4279850 localhost:8051 4279851 localhost:8052 |
Add |
Add a new portal server node. |
Remove |
Remove the selected portal server node. Important: Make sure that at least one node remains. |
.NET Runtime Servers
Configure each .NET runtime server node to enable communication with a portal server node:
Element |
Description |
Portal Node |
The ID property of a portal server node. For example: 3200150 Default:* - means that all portal nodes listen to the specified .NET runtime server node |
Host:Port |
The host and port on which a .NET runtime server node listens for the connection from a portal server node; the port number should match the TCP Port property of the server node. <.NET runtime host>:<.NET runtime port number> Example: p504:8050 Default: localhost:8050 |
Add |
Add a new .NET runtime server node configuration. |
Remove |
Remove the selected .NET runtime server node configuration. Important: Make sure that at least one node remains. |
Check Server |
Check response of the selected .NET runtime server node. |
.NET Runtime Failover Servers
To ensure reliability of the operation, specify the failover .NET runtime server nodes to use when none of the servers in the current configuration is responding. It is similar to the .NET runtime servers configuration.
Element |
Description |
Portal Node |
<Portal Server ID> Example: 3200150 Default:* - means all portal nodes listen to the specified .NET runtime server node |
Host:Port |
The host and port on which a .NET runtime server listens for the connection from a portal server; the port number should match the TCP Port property of the server node. <.NET runtime host>:<.NET runtime port number> Example: p504:8050 Default: localhost:8050 |
Add |
Add a new failover .NET runtime server node configuration. |
Remove |
Remove the selected failover .NET runtime server node configuration. |
Check Server |
Check response of the selected failover .NET runtime server node. |
Service Parameters
Configure the general service parameters.
Property |
Description |
Allow Server Affinity |
If selected, all requests from a specific client session are directed to the same .NET runtime server until the end of the session; otherwise, the server is randomly selected by the load balancing mechanism. Default: selected Warning: If this checkbox is unselected, the state management, implemented with the Session and Application objects in the .NET portal components, does not work as expected. |
Display ASP.NET Stack on ASP.NET Error |
If selected, the ASP.NET call stack is displayed on an ASP.NET runtime error: otherwise, a regular portal error message is displayed. It is recommended to clear this checkbox in a production environment. Default: cleared |
Enable Ja.NET Logging |
If selected, writing Ja.NET (Java -.NET interoperability framework) log entries to the portal log is enabled. You also need to configure the portal logger to assign Debug or higher severity level for the com.sap.portal.dotnet component. For more information about tracing and logging, see Trace and Log Files. It is recommended to clear this checkbox in a production environment. Default: cleared |
Production Mode |
Defines the runtime operation mode. If unselected (Development mode), each request is processed by the specific .NET runtime server indicated in the request parameter. This mode enables a group of developers to use a single portal for simultaneous debugging sessions. If selected (Production mode), the requests are processed according to the configuration of .NET runtime servers. Default: selected |
Lease Duration (seconds) |
The initial lifetime of a Java object in seconds and the amount of time to renew the lease each time the object is accessed. If necessary, this value can be increased in the development mode. Default: 5 |
Request Timeout (milliseconds) |
.NET iView request timeout in milliseconds. Default: 5000 |
6. Click Save to save your changes, Cancel to restore previous settings, or Reset to restore defaults.
Note When you restart the portal service, the status indicators of all services in the List of Services panel indicate Stopped. However, you do not need to start the services manually, as they will be started automatically upon the first request.