Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Appendix B: Installing XBikes on .NET

 

Retired Content

This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

patterns & practices Developer Center

Microsoft Corporation

December 2003

Contents

Introduction

Deploying XBikes on a Single Computer

Deploying XBikes on Multiple Computers

Changing Interoperability Methods

Uninstalling XBikes

Introduction

There are two ways in which you can deploy the .NET Framework version of the XBikes sample application using Microsoft Windows Installer (.msi). This appendix describes the following deployment scenarios

  • Deploying XBikes on a Single Computer
  • Deploying XBikes on Multiple Computers

This appendix also describes how to configure the various XML files that control configuration and interoperability choices. There are also sections on how to execute and uninstall the application.

Deploying XBikes on a Single Computer

Using the XBikes .NET sample code on a single computer requires the following software to be installed:

  • Windows Server 2003 or Windows 2000 Server with Service Pack 3 or later in Workgroup mode
  • .NET Framework 1.1 (Windows 2000 only; included in Windows 2003)
  • .NET Framework 1.1 SDK or Visual Studio 2003
  • Internet Information Services — World Wide Web Server
  • ASP.NET Application Server component (Windows 2003 only)
  • Microsoft Enterprise Instrumentation Framework (EIF)
  • Microsoft Message Queuing (also known as MSMQ)
  • Microsoft SQL Server 2000 with mixed mode security and Service Pack 3
  • JNBridgePro version 1.4 Enterprise Edition (run time only)
Note   ASP.NET Session State Service should be running and its startup type should be set to automatic.

Installing the XBikes Application

To install the XBikes application for the .NET platform on a single computer, complete the following steps.

To install XBikes for the .NET platform

  1. Open Windows Explorer, and then double-click xbikes3tier.msi.
  2. On the xbikes3tier wizard page, click Next.
  3. On the Select Installation Folder page, make sure C:\Xbikes is the installation path, select the Everyone option to install XBikes for all users on the computer, and then click Next.
  4. On the Confirm Installation page, click Next.
  5. On the Install Options page, make sure Single Tier is selected, and then click Next.
  6. In the Winzip Self Extractor dialog box, make sure Unzip to folder is set to C:\xbikes, and then click Unzip.
  7. The dialog box shows that files were unzipped successfully, click OK.
  8. In the Winzip Self-Extractor dialog box, click Close.
  9. The installation program continues the setup process for a few seconds.
  10. On the Installation Complete page, click Close.

Configuring the XBikes Web Application

The XBikes application is now installed. Before you execute the application, you will need to modify the identity of the COM+ to Network Service to allow the application to execute without the need for someone to be logged in.

To configure the COM+ Application

  1. In Control Panel, double-click Administrative Tools, and then double-click Component Services. The Component Services Manager loads.
  2. In the tree on the left, expand Component Services, expand Computers, and then expand My Computer.
  3. Expand COM+ Applications. A list of installed COM+ applications is shown in the tree view.
  4. Right-click XBikes, and then click Properties. The XBikes Properties dialog box appears.
  5. Click the Identity tab, and then click the Network Service option.
  6. Click OK. The XBikes Properties dialog box closes.
  7. Close Component Services Manager.

Now you have the COM+ Application configured, the next task is to check the database connection string is correct for your system.

To configure the database connection string

  1. In Notepad, open the Dllhost.exe.config file from the C:\Windows\System32 folder.
  2. Find the start tag of the <SqlServer> element.
  3. Check to make sure the connection string includes the correct server name. The server name is shown in bold below to help you.
    <SqlServer>
      <connection>
        <add
          key="connectionString"
          value="server=localhost;database=xbikes;user id=dhb; password=bikes"
        />
      </connection>
    </SqlServer>
    

    If you need to change the connection string, modify the value attribute appropriately.

  4. Locate the <QueueNames> tag. Change the NET-MSMQ value to include the correct IP address of your computer.
    <Queue>
        <QueueNames>
            <add key="NET-MSMQ" value="FormatName:DIRECT=TCP:192.168.0.5\Private$\XBikes-OrderQueue" />
    
  5. Save Dllhost.exe.config.
  6. Using Notepad, open XBikes-DAL-MSMQServiceInterface.exe.config from the C:\Xbikes\Net\Xbikes-Dal-Msmqserviceinterface\Bin\Debug folder.
  7. Repeat steps 2 through 4, and then save the file.

This completes the configuration of the XBikes Web application.

Running XBikes on a Single Tier

To test the installation and execute XBikes complete the following steps.

To execute XBikes

  1. Load Internet Explorer.
  2. In the Address field, enter the URL http://localhost/XBikes-Web.

The XBikes Web application allows you to browse bikes by type, order bikes, change quantities and check out your order.

When orders are written, they go to the message queue. To move orders from the .NET Message Queue into the SQL Server database, you must run a DOS console application. Complete the following steps on the .NET computer.

To run the DOS console application

  1. Open a command prompt.
  2. Type cd /D C:\xbikes\net\xbikes-dal-msmqserviceinterface\bin\Debug, and then press ENTER.
  3. Execute XBikes-DAL-MSMQServiceInterface.exe. One message is read from the queue. The XML representation of the Order is displayed.
  4. If there are more messages on the queue press Y; otherwise press any other key to exit the application.

Deploying XBikes on Multiple Computers

This section describes how to install XBikes in a distributed environment, so that the Presentation tier, Business tier, and Data tier are installed on different computers.

Another configuration option is to set up the database on a separate computer. In this case, the configuration settings for the Data tier connection string must to be set appropriately to point to this computer.

Note   In a distributed setup, none of the in-memory adapters work. This is by design because they can work only when all three tier processes run on the same computer. For a .NET Framework-only setup, use the .NET Remoting adapters instead.

Identifying Requirements for Each Computer

This section describes the components that must be installed on each computer in a distributed environment before you install the XBikes application.

Presentation Tier Computer Setup

The Presentation tier computer requires the following components:

  • Windows Server 2003 or Windows 2000 Server with Service Pack 3 or later in Workgroup mode
  • .NET Framework 1.1
  • .NET Framework 1.1 SDK or Visual Studio 2003
  • Internet Information Service — World Wide Web Server
  • ASP.NET Application Server component (Windows 2003 only)
  • Microsoft Enterprise Instrumentation Framework (EIF)
  • JNBridgePro v1.4 Enterprise Edition (run time only)
Note   ASP.NET Session State Service should be running and its startup type should be set to automatic.

Installing XBikes on the Presentation Tier

To install XBikes on the presentation tier computer, complete the following steps.

To install XBikes on the Presentation tier computer

  1. Open Windows Explorer, and then double-click xbikes3tier.msi.
  2. On the xbikes3tier wizard page, click Next.
  3. On the Select Installation Folder page, make sure C:\Xbikes is the installation path, select the Everyone option to install XBikes for all users on the computer, and then click Next.
  4. On the Confirm Installation page, click Next.
  5. On the Install Options page, select Web Tier Only, and then click Next to continue.
  6. In the Winzip Self Extractor dialog box, make sure Unzip to folder is set to C:\xbikes, and then click Unzip.
  7. In the dialog box that shows how many files were unzipped successfully, click OK.
  8. In the Winzip Self-Extractor dialog box, click Close.

    The installation program continues the setup process for a few seconds.

  9. On the Installation Complete page, click Close.

Configuring XBikes on the Presentation Tier

The XBikes Web application uses .NET Remoting to communicate between the tiers when deployed across multiple machines. Before executing the application, you must change the configuration for .NET Remoting to point to the correct machine.

To configure the .NET Remoting on the Presentation tier

  1. Using Notepad, open the Remoting.config from the C:\Xbikes\Net\Xbikes-Web folder.
  2. Find the <wellknown> element, and then set its url attribute to the URL of the .NET Remoting Business tier service interface. You must set the server name to the name of the computer where the Business tier components are installed as shown in the following example.
    <wellknown
      url="http://BusinessTierComputer/XBikes-BLL-RemotingServiceInterface/BLLRemotingServiceInterface.rem"
      type="XBikes.BLL.ServiceInterface.Net.Remoting.BLLRemotingServiceInterface, XBikes-BLL-RemotingServiceInterface"
    />
    
  3. Save Remoting.config.

This completes the configuration of the Presentation tier computer.

Business Tier Computer Setup

The Business tier computer requires the following components:

  • Windows Server 2003 or Windows 2000 Server with Service Pack 3 or later in Workgroup mode
  • .NET Framework 1.1
  • .NET Framework 1.1 SDK or Visual Studio 2003
  • Internet Information Service — World Wide Web Server
  • ASP.NET Application Server component (Windows 2003 only)
  • Microsoft Enterprise Instrumentation Framework (EIF)
  • JNBridgePro v1.4 Enterprise Edition (run time only)

Installing XBikes on the Business Tier

To install XBikes on the Business tier computer complete the following steps.

To install XBikes on the Business tier computer

  1. Open Windows Explorer, and then double-click xbikes3tier.msi.
  2. On the xbikes3tier wizard page, click Next.
  3. On the Select Installation Folder page, make sure c:\xbikes is the installation path, select the Everyone option to install XBikes for all users on the computer, and then click Next.
  4. On the Confirm Installation page, click Next.
  5. On the Install Options page, select Business Logic Layer Only. Click Next.
  6. In the Winzip Self Extractor dialog box, make sure Unzip to folder is set to C:\xbikes, and then click Unzip.
  7. In the dialog box that shows how many files were unzipped successfully, click OK.
  8. In the Winzip Self-Extractor dialog box, click Close.

    The installation program continues the setup process for a few seconds.

  9. On the Installation Complete page, click Close.

Configuring XBikes on the Business Tier

The XBikes application is now installed on the Business tier computer. Before you execute the application, you will need to modify the identity of the COM+ to Network Service to allow the application to execute without the need for someone to be logged in. You will also have to configure .NET Remoting.

To configure the COM+ application on the Business tier

  1. In Control Panel, double-click Administrative Tools, and then double-click Component Services. The Component Services Manager loads.
  2. In the tree on the left, expand Component Services, expand Computers, and then expand My Computer.
  3. Expand COM+ Applications. A list of installed COM+ applications is shown in the tree view.
  4. Right-click XBikes, and then click Properties. The XBikes Properties dialog box appears.
  5. Click the Identity tab, and then click the Network Service option.
  6. Click OK. The XBikes Properties dialog box closes.
  7. Close Component Services Manager.

To configure .NET Remoting on the Business tier

  1. In Notepad, open the Remoting.config file. This file is located in the System32 directory located under the system folder, such as C:\Windows, of the computer hosting the Business tier components.
  2. Find the <wellknown> element, and set its url attribute to the URL of the .NET Remoting Data tier service interface. You must set the server name to the name of the computer where the Data tier components are installed as shown in the following example.
    <wellknown
      url="http://DataTierComputer/XBikes-DAL-RemotingServiceInterface/DALRemotingServiceInterface.rem"
      type="XBikes.DAL.ServiceInterface.Net.Remoting.DALRemotingServiceInterface, XBikes-DAL-RemotingServiceInterface"
    />
  3. Save Remoting.config.

This completes the configuration of the Business tier computer.

Data Tier Computer Setup

The Data tier computer requires the following components:

  • Windows Server 2003 or Windows 2000 Server with Service Pack 3 or later in Workgroup mode
  • .NET Framework 1.1
  • .NET Framework 1.1 SDK or Visual Studio 2003
  • Microsoft Message Queuing (also known as MSMQ)
  • Microsoft SQL Server 2000 with mixed mode security and Service Pack 3
  • Internet Information Service — World Wide Web Server
  • ASP.NET Application Server component (Windows 2003 only)
  • Microsoft Enterprise Instrumentation Framework (EIF)

Installing XBikes on the Data Tier

To install XBikes on the Data tier computer, complete the following steps.

To install XBikes on the Data tier computer

  1. Open Windows Explorer, and then double-click xbikes3tier.msi.
  2. On the xbikes3tier wizard page, click Next.
  3. On the Select Installation Folder page, make sure C:\Xbikes is the installation path, select the Everyone option to install XBikes for all users on the computer, and then click Next.
  4. On the Confirm Installation page, click Next.
  5. On the Install Options page, select Data Access Layer Only. Click Next.
  6. In the Winzip Self Extractor dialog box, make sure Unzip to folder is set to C:\xbikes, and then click Unzip.
  7. In the dialog box that shows how many files were unzipped successfully, click OK.
  8. In the Winzip Self-Extractor dialog box, click Close.

    The installation program continues the setup process for a few seconds.

  9. On the Installation Complete page, click Close.

Configuring XBikes on the Data Tier

The XBikes application is now installed on the Data tier. Before you can execute the application you must configure the queue and database connection settings. To perform the configuration, complete the following steps.

To configure the database connection string

  1. In Notepad, open the Dllhost.exe.config file from the C:\Windows\System32 folder.
  2. Find the start tag of the <SqlServer> element.
  3. Check to make sure the connection string includes the correct server name. The server name is shown in bold below to help you.
    <SqlServer>
      <connection>
        <add
          key="connectionString"
          value="server=localhost;database=xbikes;user id=dhb; password=bikes"
        />
      </connection>
    </SqlServer>
    

    If you need to change the connection string, modify the value attribute appropriately.

  4. Locate the <QueueNames> tag. Change the NET-MSMQ value to include the correct IP address of your computer.
    <Queue>
        <QueueNames>
            <add key="NET-MSMQ" value="FormatName:DIRECT=TCP:192.168.0.5\Private$\XBikes-OrderQueue" />
    
  5. Save Dllhost.exe.config.
  6. Using Notepad, open XBikes-DAL-MSMQServiceInterface.exe.config from the C:\Xbikes\Net\Xbikes-Dal-Msmqserviceinterface\Bin\Debug folder.
  7. Repeat steps 2 through 4, and then save the file.

Running XBikes on Multiple Computers

To test the installation and execute XBikes complete the following steps on the Presentation tier computer.

To execute XBikes

  1. Load Internet Explorer.
  2. In the Address field, enter the URL http://localhost/XBikes-Web.

The XBikes Web application allows you to browse bikes by type, order bikes, change quantities, and check out your order.

When orders are written, they go to the message queue. To move orders from the .NET Message Queue into the SQL Server database, you must run a DOS console application. Complete the following steps on the Data tier computer.

To run the DOS console application

  1. Open a command prompt.
  2. Type cd /D C:\xbikes\net\xbikes-dal-msmqserviceinterface\bin\Debug, and then press ENTER.
  3. Execute XBikes-DAL-MSMQServiceInterface.exe. One message is read from the queue. The XML representation of the Order is displayed.
  4. If there are more messages on the queue press Y; otherwise press any other key to exit the application.

Changing Interoperability Methods

When you have the XBikes application operating correctly, you can change the interoperability methods so that XBikes uses different use case adapters or resource interoperability adapters. This section describes the possible options in the following topics:

  • Using Web Services Adapters
  • Using Ja.Net Adapters
  • Using JNBridgePro Adapters

The following sections describe how to use each kind of adapter.

Using Web Service Adapters

You can use Web services adapters in the following scenarios.

  • Using Web Service Adapters between the Web and Business Tiers
  • Using Web Service Adapters between the Business and Data Tiers

To change XBikes to use Web services adapters, you must modify the application configuration to use the Web services adapters, update the application configuration with the URLs of the Web services, and then restart the application. The following sections describe how to perform these tasks.

Using Web Service Adapters between the Web and Business Tiers

This section describes how to use Web services between the Web and Business tiers. You can either use .NET Web services or J2EE Web services; complete the steps in one of the following procedures.

To use .NET Framework Web services between the Web and Business tiers

  1. In Notepad, open the Web.config file for the XBikes application. This file is located in the C:\Xbikes\Net\XBikes-Web folder.
  2. Find the start tag of the <appSettings> element in the Web.config file.
  3. Find the <add> child element that specifies the URL of the .NET Framework Web service Business tier service interface. Set the value attribute to the correct URL as show in the following example.
    <add
      key="XBikes-UseCaseInteropAdapters.Net.BLLWSSI.BLLWSServiceInterface"
      value="http://localhost/XBikes-BLL-WSServiceInterface/BLLWSServiceInterface.asmx"
    />
    
  4. Locate the <adapters> tag. Locate the <!-- .NET WS Adapters --> comment and remove the comments from configuration information located immediately below this comment.
  5. Within the <adapters> section. Locate an existing group of tags that have not been commented out. Wrap the section with comments.
  6. Save Web.config.

To use J2EE Web services between the Web and Business tiers

  1. In Notepad, open the Web.config file for the XBikes application. This file is located in the C:\Xbikes\Net\XBikes-Web folder.
  2. Find the start tag of the <appSettings> element in the Web.config file.
  3. Find the <add> child element that specifies the URL of the J2EE Web service Business tier service interface. Set the value attribute to the correct URL as shown in the following example.
    <add
      key="XBikes-UseCaseInteropAdapters.J2EE.BLLWSSI.BLLWSServiceInterface"
      value="http://192.168.99.199:9080/XBikesBLLServiceInterface/
    services/BLLWSServiceInterface"
    />
    
  4. Locate the <adapters> tag. Locate the <!-- J2EE WS Adapters --> comment and remove the comments from configuration information located immediately below this comment.
  5. Within the <adapters> section. Locate an existing group of tags that have not been commented out. Wrap the section with comments.
  6. Save Web.config.

Using Web Service Adapters between the Business and Data Tiers

This section describes how to use Web services between the Business and Data tiers. You can either use .NET Web services or J2EE Web services; complete the steps in one of the following procedures.

To use .NET Framework Web services between the Business and Data tiers

  1. In Notepad, open the Dllhost.exe.config file from the C:\Windows\System32 folder.
  2. Find the start tag of the <appSettings> element in the file.
  3. Find the <add> child element that specifies the URL of the .NET Framework Web service Data tier service interface. Set the value attribute to the correct URL as shown in the following example.
    <add
      key="XBikes-ResourceInteropAdapters.Net.DALWSSI.DALWSServiceInterface"
      value="http://localhost/XBikes-DAL-WSServiceInterface/
    DALWSServiceInterface.asmx"
    />
    
  4. Locate the <adapters> tag. Locate the <!-- .NET WS Adapters --> comment and remove the comments from configuration information located immediately below this comment.
  5. Within the <adapters> section. Locate an existing group of tags that have not been commented out. Wrap the section with comments.
  6. Save Web.config.

To use .NET Framework Web services between the Business and Data Tiers

  1. In Notepad, open the Dllhost.exe.config file from the C:\Windows\System32 folder.
  2. Find the start tag of the <appSettings> element in the file.
  3. Find the <add> child element that specifies the URL of the J2EE Web service Data tier service interface. Set the value attribute to the correct URL as shown in the following example.
    <add
      key="XBikes-ResourceInteropAdapters.J2EE.DALWSSI.DALWSServiceInterface"
      value="http://192.168.99.199:9080/XBikesResWS/services/
    DALWSServiceInterface"
    />
    
  4. Locate the <adapters> tag. Locate the <!-- J2EE WS Adapters --> comment and remove the comments from configuration information located immediately below this comment.
  5. Within the <adapters> section. Locate an existing group of tags that have not been commented out. Wrap the section with comments.
  6. Save Web.config.

Using Ja.NET Adapters

You can use Ja.NET adapters in the following scenarios:

  • Using Ja.NET Adapters between the Web and Business Tiers
  • Using Ja.NET Adapters between the Business and Data Tiers

To change XBikes to use Ja.NET adapters, you must modify the application configuration to use the Ja.NET adapters, update the application configuration with the URLs of the Ja.NET service, and then restart the application. You must also reconfigure the J2EE application to allow Ja.NET to function, because out of the box, the J2EE application is configured for J2EE to .NET interoperability. The following sections describe how to perform these tasks.

Reconfiguring the J2EE Application for Ja.NET

To enable the Ja.NET adapters to communicate with the J2EE version of XBikes, you must complete one of the following tasks depending upon your configuration.

To change the WebSphere Studio Application Developer 5.0 configuration

  1. Start WebSphere Application Developer Studio 5.0 by clicking Start, pointing to All Programs, pointing to IBM WebSphere Studio, and clicking Application Developer 5.0.
  2. A WebSphere Studio dialog box appears. Change the workspace to c:\xbikes
    \j2ee-ibm
    and then click OK.
  3. The J2EE – IBM WebSphere Studio Application Developer window appears.
  4. In the left window, click the J2EE Hierarchy tab. The J2EE Hierarchy window appears.
  5. Expand Server Configurations, and then double-click WebSphere v5.0 Server Configuration. The WebSphere v5.0 Server Configuration appears in the main window.
  6. Click the Paths tab from the bottom of the main window. The Paths configuration screen appears.
  7. Click c:\xbikes\J2EE-IBM\janet_libs\janetNetDalProxies.jar, and then click Remove.
  8. Repeat step 7 for c:\xbikes\J2EE-IBM\janet_libs\JanetNetBllProxies.jar and c:\xbikes\J2EE-IBM\janet_libs\janet.jar.
  9. Click the Environment tab from the bottom of the main window. The Environment Options configuration screen appears.
  10. Remove all the entries from the Java VM Arguments field.
  11. Close the WebSphere v5.0 Server Configuration window. The Save Resource dialog box appears. Click Yes to save your changes.
  12. Switch to the J2EE Navigator view in the left pane.
  13. Expand JaNetBLL, expand Java Source, and then expand com.intrinsyc.janet.
  14. Open JaNet.xml.
  15. Locate the <URI> tag and replace http://192.168.0.200:9080/JaNetBLL with http://<ipaddress>/JaNetBLL, where <ipaddress> is the IP address of the computer hosting the JaNetBLL.
  16. Repeat steps 13–15 for both JaNetDAL and JaNetJMS.
  17. You may now restart or start your server.

To change the WebSphere application server configuration

  1. On the computer hosting the Ja.NET service interfaces, open a command prompt and navigate to the C:\Was\Websphere\Appserver\Bin folder.
  2. Type startserver server1, and then press ENTER. After a short period of time, a message displays indicating that server1 is open for e-business.
  3. Open a Web browser window and navigate to http://localhost:9080/admin.
  4. In the User ID field, enter admin, and then click OK.
  5. In the left pane, expand Servers, and then click Application Servers. The Application Servers window appears in the right pane.
  6. In the right pane, click server1. The server1 window appears.
  7. In the right pane, click Process Definition. The Process Definition window appears.
  8. In the right pane, click Java Virtual Machine. The Java Virtual Machine window appears.
  9. Remove all entries from the Classpath field EXCEPT the entry c:\tme\glue\lib
    \GLUE.jar
    .
  10. Remove the entry from the Generic JVM arguments field. The field should be empty.
  11. Click OK. The Messages section appears at the top of the right pane. Click the Save link.
  12. In the Save pane, click the Save button. The right pane reverts to the WebSphere Application Server home page.
  13. Close your browser and restart the server for the changes to take effect.

You must now update the EAR that contains the Ja.NET adapters you want to access. To do this you must have access to the source code.

To update the EAR that contains the Ja.NET adapters you want to access

  1. Start WebSphere Application Developer Studio 5.0 by clicking Start, pointing to All Programs, pointing to IBM WebSphere Studio, and then clicking Application Developer 5.0.
  2. A WebSphere Studio dialog box appears. Change the workspace to c:\xbikes
    \j2ee-ibm
    and then click OK.
  3. The J2EE – IBM WebSphere Studio Application Developer window appears.
  4. Close the WebSphere v5.0 Server Configuration window. In the Save Resource dialog box, click Yes to save your changes.
  5. Switch to the J2EE Navigator view in the left pane.
  6. Expand JaNetBLL, expand Java Source, and then expand com.intrinsyc.janet.
  7. Open JaNet.xml.
  8. Locate the <URI> tag and replace http://192.168.0.200:9080/JaNetBLL with http://<ipaddress>/JaNetBLL, where <ipaddress> is the IP address of the machine hosting the JaNetBLL.
  9. Repeat steps 13–15 for both JaNetDAL and JaNetJMS.

You must now recreate the EARs. To do this, follow the steps for manual deployment in Appendix A, and then deploy the EAR to the server. If you have already installed the EARs using the installer, or if you manually installed the EARs, you must uninstall the EARs. This can be done using the Web-based Administrative Console.

Note   To revert back to the original J2EE configuration, you must add the entries you removed in the previous steps. The quickest way to do this is to uninstall, and then reinstall, the J2EE version of XBikes.

Using Ja.NET Adapters between the Web and Business Tiers

This section describes how to use Ja.NET between the Business and Data tiers. To enable the Ja.NET adapters, complete the following steps.

To configure the Ja.NET use case interoperability adapters

  1. In Notepad, open the Remoting.config file for the XBikes application. This file is located in the C:\Xbikes\Net\XBikes-Web folder.
  2. Find the <client url="…"> element, and then set its url attribute to the URL of the Ja.NET BLL service interface as shown in the following example.
    <client url="http://192.168.99.199:9080/JaNetBLL">
    
  3. Save Remoting.config.
  4. In Notepad, open the Web.config file for the XBikes application. This file is located in the C:\Xbikes\Net\XBikes-Web folder.
  5. Locate the <adapters> tag. Locate the <!-- JaNET Adapters --> comment and remove the comments from configuration information located immediately below this comment.
  6. Within the <adapters> section. Locate an existing group of tags that have not been commented out. Wrap the section with comments.
  7. Save Web.config.

Using Ja.NET Adapters between the Business and Data Tiers

This section describes how to use Ja.NET between the Business and Data tiers. To enable the Ja.NET adapters, complete the following steps.

To configure the Ja.NET resource interoperability adapters

  1. In Notepad, open the Remoting.config file. This file is located in the System32 directory located under the system folder, such as C:\Windows, of the computer hosting the Business tier components.
  2. Find the <client url="…"> element that sets the URL for the Ja.NET Data tier service interface, and set its url attribute to the correct URL as shown in the following example.
    <client url="http://192.168.99.199:9080/JaNetDAL">
    
  3. Find the <client url="…"> element that sets the URL for the Ja.NET queue service interface, and then set its url attribute to the correct URL as shown in the following example.
    <client url="http://192.168.99.199:9080/JaNetJms">
    
  4. Save Remoting.config.
  5. In Notepad, open the Dllhost.exe.config file for the XBikes application. This file is located in the C:\Windows\System32 folder.
  6. Locate the <adapters> tag. Locate the <!-- JaNET Adapters --> comment and remove the comments from configuration information located immediately below this comment.
  7. Within the <adapters> section. Locate an existing group of tags that have not been commented out. Wrap the section with comments.
  8. Save Dllhost.exe.config.

To configure the queue name

  1. In Notepad, open the Dllhost.exe.config file. This file is located in the System32 directory located under the system folder, such as C:\Windows, of the computer hosting the Business tier components.
  2. Find the <QueueNames> element. If the name of the MQSeries queue or queue factory has been changed in the J2EE application, define <add> elements to specify the MQSeries queue name and queue factory name for the Ja.NET queue resource interoperability adapter as shown in the following example.
    <add key="JaNET-MQSeries-QName" value="XBikesQ" />
    <add key="JaNET-MQSeries-QFactoryName" value="XBikesQCF" />
    
  3. Save Dllhost.exe.config.

Using JNBridgePro Adapters

You can use JNBridgePro adapters in the following scenarios.

  • Using JNBridgePro Adapters between the Web and Business Tiers
  • Using JNBridgePro Adapters between the Business and Data Tiers

To change XBikes to use JNBridgePro adapters, you must modify the application configuration to use the JNBridgePro adapters, update the application configuration with the URLs of the JNBridgePro, and then restart the application. The following sections describe how to perform these tasks.

Using JNBridgePro Adapters between the Web and Business Tiers

This section describes how to use JNBridgePro between the Business and Data tiers. To enabled the JNBridgePro adapters, complete the following steps.

To configure the JNBridge use case interoperability adapters

  1. In Notepad, open the JNBProxy.config from the C:\Inetpub\Wwwroot folder.
  2. Find the <wellknown> element, and then set its url attribute to the URL of the JNBridge BLL service interface as shown in the following example.
    <wellknown
      url="jtcp://192.168.99.199:8085/JNBDispatcher"
      type="com.jnbridge.jnbcore.JNBDispatcher, JNBShare"
    />
    
  3. Save JNBProxy.config.
  4. In Notepad, open the Web.config file for the XBikes application. This file is located in the C:\Xbikes\Net\XBikes-Web folder.
  5. Locate the <adapters> tag. Locate the <!-- JNBridge Adapters --> comment and remove the comments from configuration information located immediately below this comment.
  6. Within the <adapters> section. Locate an existing group of tags that have not been commented out. Wrap the section with comments.
  7. Save Web.config.

Using JNBridgePro Adapters between the Business and Data Tiers

This section describes how to use Web services between the Business and Data tiers. To enabled the JNBridgePro adapters, complete the following steps.

To configure the JNBridge resource interoperability adapters

  1. In Notepad, open the Dllhost.exe.config file from the C:\Windows\System32 folder.
  2. Find the <jnbridge> element.
  3. Make sure the <add> child element specifies the URL for the JNBridge Data tier service interface as shown in the following example.
    <add
      key="DAL_PrimaryURL"
      value="jtcp://javabox:8086/JNBDispatcher"
    />
    
  4. Find the <QueueNames> element. If the name of the MQSeries queue or queue factory has been changed in the J2EE application, define <add> elements to specify the MQSeries queue name and queue factory name for the JNBridge queue resource Interoperability adapter as shown in the following example.
    <add key="JNBridge-MQSeries-QName" value="XBikesQ" />
    <add key="JNBridge-MQSeries-QFactoryName" value="XBikesQCF" />
    
  5. Locate the <adapters> tag. Locate the <!-- JNBridge Adapters --> comment and remove the comments from configuration information located immediately below this comment.
  6. Within the <adapters> section. Locate an existing group of tags that have not been commented out. Wrap the section with comments.
  7. Save Dllhost.exe.config.

Uninstalling XBikes

To uninstall the .NET XBikes Web application, complete the following steps.

To uninstall XBikes

  1. In Control Panel, double-click Add or Remove Programs.
  2. In the Add or Remove Programs window, click xbikes3tier in the list of currently installed programs, and then click Remove.
  3. Click Yes to confirm that you want to remove this program from your computer.

Next, the following items must be removed manually.

To delete additional items on a single computer

  1. Delete the Com+ application named XBikes:
    1. In Control Panel, double-click Administrative Tools, and then double-click Component Services.
    2. In the Component Services node, expand the tree until you see My Computer.
    3. Expand COM+ Applications, right-click XBIKES, and then click Delete.
  2. Delete the following virtual directories:
    • XBikes-Web
    • XBikes-BLL-RemotingServiceInterface
    • XBikes-BLL-WSServiceInterface
    • XBikes-DAL-WSServiceInterface
    • XBikes-DAL-RemotingServiceInterface
    • xbikes-bll-janetserviceinterface
    • xbikes-dal-janetserviceinterface
  3. In Control Panel, double-click Administrative Tools, and then double-click Internet Information Services. Expand the tree for your computer, click Web sites, and then click Default Web site. Right-click each entry listed in step 2, and click Delete for each one.
  4. Delete the following from the global assembly cache:
    • xbikes-common
    • jnbridgebllproxies
    • jnbridgeDALProxies
    • jnbshare
    • janetBllEjb
    • janetDalEjb
    • JaNetJms
  5. In Control Panel, double-click Administrative Tools, and then double-click Microsoft .NET Framework 1.1 Configuration. Click Assembly Cache in the left pane, and then click Assembly Cache or View List of Assemblies in the right pane. Right-click each entry in step 4, and click Delete for each one.
  6. In Windows Explorer, delete the following folders:
    • C:\Xbikes
    • C:\Windows\System32\Dllhost.exe.config
    • C:\Windows\System32\Dllhost.exe.config.xsd
    • C:\Windows\System32\EnterpriseInstrumentation.config
    • C:\Windows\System32\Remoting.config
    • C:\Inetpub\Wwwroot\Jnbproxy.config
  7. Delete the SQL database named XBIKES:
    1. Click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
    2. Expand Console Root, expand Microsoft SQL Servers, and then expand SQL Server Group. You should see your computer — if not, you need to register your SQL instance. For information about how to do this, see the article "How to register a server (Enterprise Manager)" on MSDN.
    3. Expand your computer, and then expand databases.
    4. Right-click XBikes, and then click Delete.
  8. Delete the private message queue named XBikes-orderqueue:
    1. In Control Panel, double-click Administrative Tools, and then double-click Computer Management.
    2. Expand Services and Applications, expand Message Queuing, and then expand Private Queue.
    3. Right-click XBikes-orderqueue, and then click Delete.

To delete additional items on a Web tier computer

  1. Delete the virtual directory named XBikes-Web:
    1. In Control Panel, double-click Administrative Tools, and then double-click Internet Information Services.
    2. Expand the tree for your computer, expand Web sites, and then click Default Web site.
    3. Right-click each entry listed in step 2 of the preceding procedure, and click Delete for each one.
  2. Delete the following from the global assembly cache:
    • xbikes-common
    • jnbridgebllproxies
    • jnbshare
    • janetBllEjb
  3. In Control Panel, double-click Administrative Tools, and then double-click Microsoft .NET Framework 1.1 Configuration. Click Assembly Cache in the left pane, and then click Assembly Cache or View List of Assemblies in the right pane. Right-click each entry listed in step 2 (of this procedure), and click Delete for each one.
  4. In Windows Explorer, delete the C:\Xbikes folder and the file C:\Inetpub
    \Wwwroot\Jnbproxy.config.

To delete additional items on a Business tier computer

  1. Delete the Com+ application named XBikes:
    1. In Control Panel, double-click Administrative Tools, and then double-click Component Services.
    2. In the Component Services node, expand the tree until you see My Computer.
    3. Expand COM+ Applications.
    4. Right-click XBIKES, and then click Delete.
  2. Delete the following virtual directories:
    • XBikes-BLL-RemotingServiceInterface
    • XBikes-BLL-WSServiceInterface
    • xbikes-bll-janetserviceinterface
  3. In Control Panel, double-click Administrative Tools, and then double-click Internet Information Services. Expand the tree for your computer, expand Web sites, and then click Default Web site. Right-click each entry listed in step 2, and click Delete for each one.
  4. Delete the following from the global assembly cache:
    • xbikes-common
    • jnbridgeDALProxies
    • jnbshare
    • janetDalEjb
    • JaNetJms.dll
  5. In Control Panel, double-click Administrative Tools, and then double-click Microsoft .NET Framework 1.1 Configuration. Click Assembly Cache in the left pane, and then click Assembly Cache or View List of Assemblies in the right pane. Right-click each entry listed in step 4, and click Delete for each one.
  6. In Windows Explorer, delete the following folders:
    • C:\Xbikes.
    • C:\Windows\System32\Dllhost.exe.config.
    • C:\Windows\System32\Dllhost.exe.config.xsd.
    • C:\Windows\System32\EnterpriseInstrumentation.config.
    • C:\Windows\System32\Remoting.config.
    • C:\Inetpub\Wwwroot\Jnbproxy.config.

To delete additional items on a Data tier computer

  1. Delete the following virtual directories:
    • XBikes-DAL-WSServiceInterface
    • XBikes-DAL-RemotingServiceInterface
    • xbikes-dal-janetserviceinterface
  2. In Control Panel, double-click Administrative Tools, and then double-click Internet Information Services. Expand the tree for your computer, expand Web sites, and then click Default Web site. Right-click each entry listed in step 1, and click Delete for each one.
  3. Delete the following from the global assembly cache:
    • xbikes-common
    • jnbshare
  4. In Control Panel, double-click Administrative Tools, and then double-click Microsoft .NET Framework 1.1 Configuration. Click Assembly Cache in the left pane, and then click Assembly Cache or View List of Assemblies in the right pane. Right-click each entry listed in step 3, and click Delete for each one.
  5. In Windows Explorer, delete C:\Xbikes.
  6. Delete the SQL database named XBIKES:
    1. Click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
    2. Expand Console Root then Microsoft SQL Servers and then SQL Server Group. You should see your computer — if not, you need to register your SQL instance. For information about how to do this, see the article "How to register a server (Enterprise Manager)" on MSDN.
    3. Expand the tree under your computer, and then expand the tree under databases.
    4. Right-click XBikes, and then click Delete.
  7. Delete the private message queue named XBikes-orderqueue:
    1. In Control Panel, double-click Administrative Tools, and then double-click Computer Management.
    2. Expand Services and Applications, expand Message Queuing, and then expand Private Queue.
    3. Right-click XBikes-orderqueue, and then click Delete.

Start | Previous

patterns & practices Developer Center

Retired Content

This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.