Configuring and Managing Portal Runtime for
.NET
The SAP Portal Runtime for .NET Snap-In for Microsoft Management Console (MMC) provides tools to create, configure and manage the Portal Runtime for .NET server nodes on your local or remote servers.
A server is the local or remote host, on which Portal Runtime for .NET is installed.
A server node is a separate instance of the Portal Runtime for .NET service, installed on the same host. The corresponding service name is SAP NetWeaver Portal Runtime for Microsoft .NET Server XX, where XX is the server node ID.
Starting the SAP Portal Runtime for .NET Snap-In
...
...
1. Go to Start → Programs → SAP Portal Runtime for Microsoft.NET → Management Console. An MMC window with the SAP Portal Runtime for .NET node opens.
2. In the left pane, expand the SAP Portal Runtime for .NET node. In the right pane, the currently defined server nodes are displayed.
In the left pane, expand the SAP Portal Runtime for .NET node. In the right pane, the currently defined server nodes are displayed.
Initial Configuration
To start using the Portal Runtime for .NET service, perform the following configuration steps:
...
1. By default, the server This computer and the node Server00 are defined. If you have installed Portal Runtime for .NET on a remote server, connect to this server.
2. If necessary, create new server node(s) on your server.
3. Set the properties of each server node.
4. Start each server node.
For detailed instructions on performing the required tasks, see Configuration and Management Tasks.
Configuration and Management Tasks
Task |
Description |
Right-click the SAP Portal Runtime for .NET node and select Connect to Server… In the Connect to Server dialog box select either Connect to the local computer or Connect to a remote server; for a remote server, enter Server name or IP address. Important: Portal Runtime for .NET should be installed on this server. |
|
Disconnecting a server |
Right-click a server and select Disconnect from the context menu. |
Displaying the list of existing server nodes |
Double-click a server. The list of existing server nodes is displayed in the right pane. |
Right-click a server and select New node from the context menu. Set the properties of the new node as required (see below). |
|
Double-click a server node. In the Properties dialog box that opens, set the properties as follows: TCP Port: Enter the port number to be used by this node to communicate with the portal. Assign Service Logon Account: Enter the credentials of the dedicated logon account that was previously created for the service and granted full control permissions for the following folders: · %Program Files%\SAP\Portal Runtime for Microsoft .NET · %windir%\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files · %windir%\Temp This account should have the “Log on as service” permission. For more information, see Creating a Logon Account for Portal Runtime for .NET in the Installation, Configuration and Upgrade Guide.
· If you do not select a dedicated account, the default LocalSystem account will be used. This account has more permissions than necessary, so for security reasons it is not recommended for this purpose. · You can use the same account for all nodes on one server. · It is possible to assign the logon account to the service in the Windows Services tool. Click OK to assign this account to the service. |
|
Deleting a server node |
Right-click a server node and select Delete from the context menu. Confirm or cancel the deletion in the message box that appears. |
Right-click a server node and select the relevant option from the context menu. You can also use the toolbar buttons which are enabled when a node is selected. Important: To activate a service, you need to start the relevant server node. |
|
Saving state |
To save the list of servers to an .msc file, select Save or Save As from the Console menu. The list is also saved automatically when you exit MMC. |