How to Configure SNMP Agent Information
To configure SNMP agent information:
Click Start, point to Control Panel, point to Administrative Tools, and then click Computer Management.
In the console tree, expand Services and Applications, and then click Services.
In the right pane, double-click SNMP Service.
Click the Agent tab.
Type the name of the user or administrator of the computer in the Contact box, and then type the physical location of the computer or contact in the Location box.
These comments are treated as text and are optional.
Under Service, click to select the check boxes next to the services that are provided by your computer. Service options are:
Physical: Specifies whether the computer manages physical devices, such as a hard disk partition.
Applications: Specifies whether the computer uses any programs that send data by using TCP/IP.
Datalink and subnetwork: Specifies whether this computer manages a TCP/IP subnetwork or datalink, such as a bridge.
Internet: Specifies whether this computer acts as an IP gateway (router).
End-to-end: Specifies whether this computer acts as an IP host.
Click OK.
NOTE: If you have installed additional TCP/IP network devices, such as a switch or a router, see Request for Comments (RFC) 1213 for additional information. To view RFC 1213, visit the following Internet Engineering Task Force (IETF) Web site:
http://www.ietf.org/rfc/rfc1213.txt (http://www.ietf.org/rfc/rfc1213.txt)
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
Back to the top
How to Configure SNMP Communities and Traps
To configure traps:
Click Start, point to Control Panel, point to Administrative Tools, and then click Computer Management.
In the console tree, expand Services and Applications, and then click Services.
In the right pane, double-click SNMP Service.
Click the Traps tab.
In the Community name box, type the case-sensitive community name to which this computer will send trap messages, and then click Add to list.
Under Trap destinations, click Add.
In the Host name, IP or IPX address box, type the name, IP or IPX address of the host, and then click Add.
The host name or address appears in the Trap destinations list.
Repeat steps 5 through 7 to add the communities and trap destinations that you want.
Click OK.
Back to the top
How to Configure SNMP Security
To configure SNMP security for a community:
Click Start, point to Control Panel, point to Administrative Tools, and then click Computer Management.
In the console tree, expand Services and Applications, and then click Services.
In the right pane, double-click SNMP Service.
Click the Security tab.
Click to select the Send authentication trap check box (if it is not already selected) if you want a trap message sent whenever authentication fails.
Under Accepted community names, click Add.
To specify how the host processes SNMP requests from the selected community, click the permission level that you want in the Community Rights box.
In the Community Name box, type the case-sensitive community name that you want, and then click Add.
Specify whether or not to accept SNMP packets from a host. To do so, do one of the following:
To accept SNMP requests from any host on the network, regardless of identity, click Accept SNMP packets from any host.
To limit the acceptance of SNMP packets, click Accept SNMP packets from these hosts, click Add, and then type the appropriate host name, IP or IPX address in the Host name, IP or IPX address box.
Click Add.
Click OK.
IMPORTANT: If you remove all of the community names, including the default name "Public", SNMP does not respond to any community names that are presented.
Tuesday, October 13, 2009
User Profile Hive Cleanup Service
The User Profile Hive Cleanup service helps to ensure user sessions are completely terminated when a user logs off. System processes and applications occasionally maintain connections to registry keys in the user profile after a user logs off. In those cases the user session is prevented from completely ending. This can result in problems when using Roaming User Profiles in a server environment or when using locked profiles as implemented through the Shared Computer Toolkit for Windows XP
Thursday, September 3, 2009
How to apply new Group Policy for XP client
1. Logon it as an administrator.
2. Delete all the files under path
C:\windows\security\templates\policies
3. Then, run gpupdate /force
4. Try to logon it use other accounts to see if the problem has been solved.
2. Delete all the files under path
C:\windows\security\templates\policies
3. Then, run gpupdate /force
4. Try to logon it use other accounts to see if the problem has been solved.
Wednesday, September 2, 2009
Creating an ASP .NET Web Application Using the SAP .NET Connector
SAP.NET Connector along with Microsoft.NET can be used to create Web Applications. The following example illustrates creating .NET project using Microsoft Visual Studio. NET. Here, a client application reads and displays customer data from an SAP System using a search value and then displays it in a data grid.
The example uses the function module RFC_CUSTOMER_GET, which requires that customer data exist in the target SAP System, for example, in IDES. Although it is possible to rename all development objects and generated proxy classes, default names are used in this example. This example is provided as part of the connector sample code (DNCWebApp).
Procedure of Creating an ASP .NET Web Application Using the SAP .NET Connector:
1. Open Microsoft Visual Studio .NET.
2. Create a new C# Web form project:
Choose New. New Project. Visual C# Projects. ASP .NET Web Application.
You can also create a project in any other common programming language for .NET, for example, in Visual Basic .NET. In this case, you must add the SAP .NET proxy classes as a separate project in the Microsoft Visual Studio .NET solution.
3. Rename the form Webform1.aspx to Default.aspx.
4. Add Web controls to your Web form.
5. Add proxy classes to connect the Web applications to your SAP server.
a. In the Solution Explorer, right-click on your project.
b. Choose Add. Add new item.
c. Select Web Project Items.
SAP Connector Class and choose Open.
The SAP .NET Connector Wizard opens.
d. Decide from where you want to generate the proxy classes.
Proxies can be created from
- Web Services Description Language (WSDL) files that originate in an SAP interface repository (IFR)
- An SAP server
- Standard WSDL files
e. Select the client proxy object type and select beautify names option.
f. Select the Remote Function Modules (RFM) you want to use in your proxy object.
You can use search filters to look for the Remote Function Modules. In the example, enter the search argument RFC_CUST* in Name-Filter and select RFC_CUSTOMER_GET.
g. Add the modules to your proxy object and choose NEXT.
The proxy classes for the referenced table and structure types are automatically created and added to the project.
6. Build the solution with Build. Build Solution.
7. Create an SAP Login page to support user name and password authentication
a. In the Solution Explorer, right-click on your project.
b. Choose Add. Add new item.
c. Select Web Project Items. SAP Login Form
Leave the name as SAPLogin1.aspx.
8. Set the system connection information in the destination object of the SAPLogin1.aspx page:
a. In the Solution Explorer window find the item SAPLogin1.aspx and double-click on it to bring it up in the designer.
b. Look for the component destination1 on the bottom of the form.
c. Click on the destination component and set the properties for connecting to your SAP system (for example AppServerHost and System Number). The other properties like client, Password and username will be set from the login page.
9. Data bind the data grid to BRFCKNA1Table:
BRFCKNA1Table is the parameter of RFC_CUSTOMER_GET that contains the list of customers.
a. Select SAP Table Wizard from the SAP proxy toolbox and Drag Drop it to your working area. In the dialog box, select BRFCKNA1Table.
b. Select the data grid, and under Properties change Data Source to BRFCKNA1Table using the drop down list.
c. Customize the list of columns displayed on the data grid by modifying the Columns collection property.
10. On the default.aspx page, double-click the Button control you added earlier to create an event handler for the control.
11. Add the connect code to your project:
Select Connect code from the SAP proxy toolbox.
Drag Drop it in the source code of your event handler. A fragment of sample code is then inserted. It connects to the SAP server using the authorization settings from the Proxy Wizard. Normally, you must change these settings.
The syntax for the application will be
private void btnSearch_Click(object sender, System.EventArgs e)
{
// Declare parameters here
SAPProxy1 proxy = new SAPProxy1();
try
{
proxy.Connection =
SAP.Connector.SAPLoginProvider.GetSAPConnection(this);
// Call methods here
proxy.Rfc_Customer_Get("", txtCust.Text, ref brfcknA1Table1);
// Now update Data Bindings. On WinForms this will be automatic, on
// WebForms call the following line
this.DataBind();
}
catch(Exception ex)
{
// If SAPLoginProvider.GetSAPConnection(this) cannot get a connection,
// we might get an error.
// Normally this can be ignored as it will automatically will force a
// relogon.
}
}
12. Build and run the application.
The browser window opens and you are redirected to your SAPLogin1.aspx login page.
13. Enter connection data (for example user, password and client).
If you select SAVE this login information will be stored as an encrypted cookie on your computer and will provide an alternative single sign-on capability the next time you wish to access the site. If you do not select SAVE, the login information will still be saved in the ASP .NET session state but will be lost once the browser is closed.
14. Enter a search argument, for example A* in the Textbox field and choose Search. Thus we create an ASP.NET Application using Visual Studio .NET using Proxy classes to connect to the server and Binding the DATA GRID. Your application connects to the SAP System and displays the requested data in the Data Grid.
The example uses the function module RFC_CUSTOMER_GET, which requires that customer data exist in the target SAP System, for example, in IDES. Although it is possible to rename all development objects and generated proxy classes, default names are used in this example. This example is provided as part of the connector sample code (DNCWebApp).
Procedure of Creating an ASP .NET Web Application Using the SAP .NET Connector:
1. Open Microsoft Visual Studio .NET.
2. Create a new C# Web form project:
Choose New. New Project. Visual C# Projects. ASP .NET Web Application.
You can also create a project in any other common programming language for .NET, for example, in Visual Basic .NET. In this case, you must add the SAP .NET proxy classes as a separate project in the Microsoft Visual Studio .NET solution.
3. Rename the form Webform1.aspx to Default.aspx.
4. Add Web controls to your Web form.
5. Add proxy classes to connect the Web applications to your SAP server.
a. In the Solution Explorer, right-click on your project.
b. Choose Add. Add new item.
c. Select Web Project Items.
SAP Connector Class and choose Open.
The SAP .NET Connector Wizard opens.
d. Decide from where you want to generate the proxy classes.
Proxies can be created from
- Web Services Description Language (WSDL) files that originate in an SAP interface repository (IFR)
- An SAP server
- Standard WSDL files
e. Select the client proxy object type and select beautify names option.
f. Select the Remote Function Modules (RFM) you want to use in your proxy object.
You can use search filters to look for the Remote Function Modules. In the example, enter the search argument RFC_CUST* in Name-Filter and select RFC_CUSTOMER_GET.
g. Add the modules to your proxy object and choose NEXT.
The proxy classes for the referenced table and structure types are automatically created and added to the project.
6. Build the solution with Build. Build Solution.
7. Create an SAP Login page to support user name and password authentication
a. In the Solution Explorer, right-click on your project.
b. Choose Add. Add new item.
c. Select Web Project Items. SAP Login Form
Leave the name as SAPLogin1.aspx.
8. Set the system connection information in the destination object of the SAPLogin1.aspx page:
a. In the Solution Explorer window find the item SAPLogin1.aspx and double-click on it to bring it up in the designer.
b. Look for the component destination1 on the bottom of the form.
c. Click on the destination component and set the properties for connecting to your SAP system (for example AppServerHost and System Number). The other properties like client, Password and username will be set from the login page.
9. Data bind the data grid to BRFCKNA1Table:
BRFCKNA1Table is the parameter of RFC_CUSTOMER_GET that contains the list of customers.
a. Select SAP Table Wizard from the SAP proxy toolbox and Drag Drop it to your working area. In the dialog box, select BRFCKNA1Table.
b. Select the data grid, and under Properties change Data Source to BRFCKNA1Table using the drop down list.
c. Customize the list of columns displayed on the data grid by modifying the Columns collection property.
10. On the default.aspx page, double-click the Button control you added earlier to create an event handler for the control.
11. Add the connect code to your project:
Select Connect code from the SAP proxy toolbox.
Drag Drop it in the source code of your event handler. A fragment of sample code is then inserted. It connects to the SAP server using the authorization settings from the Proxy Wizard. Normally, you must change these settings.
The syntax for the application will be
private void btnSearch_Click(object sender, System.EventArgs e)
{
// Declare parameters here
SAPProxy1 proxy = new SAPProxy1();
try
{
proxy.Connection =
SAP.Connector.SAPLoginProvider.GetSAPConnection(this);
// Call methods here
proxy.Rfc_Customer_Get("", txtCust.Text, ref brfcknA1Table1);
// Now update Data Bindings. On WinForms this will be automatic, on
// WebForms call the following line
this.DataBind();
}
catch(Exception ex)
{
// If SAPLoginProvider.GetSAPConnection(this) cannot get a connection,
// we might get an error.
// Normally this can be ignored as it will automatically will force a
// relogon.
}
}
12. Build and run the application.
The browser window opens and you are redirected to your SAPLogin1.aspx login page.
13. Enter connection data (for example user, password and client).
If you select SAVE this login information will be stored as an encrypted cookie on your computer and will provide an alternative single sign-on capability the next time you wish to access the site. If you do not select SAVE, the login information will still be saved in the ASP .NET session state but will be lost once the browser is closed.
14. Enter a search argument, for example A* in the Textbox field and choose Search. Thus we create an ASP.NET Application using Visual Studio .NET using Proxy classes to connect to the server and Binding the DATA GRID. Your application connects to the SAP System and displays the requested data in the Data Grid.
Subscribe to:
Posts (Atom)