转贴:
SolidEdge v15 Insight 推荐安装顺序(细节)
安装细节
Windows 2003 Setup
1. Install with default settings
2. After Installation is finished, select “Optional Windows Components” from the autorun menu.
a. Select application server
b. Click “Details”
c. select ASP.net
d. click OK and then “Continue” to install this option
SQL Server Setup
1. different from defaults is printed bold
a. In folder “Enterprise” double click “setup.bat”
b. A warning dialog box appears ?SQL Server 2000 SP2 and below“, click “Continue”.
c. Click “Next”in the next dialog
d. select “Local Computer” in the next dialog and click “Next”
e. select “Create a new instance...” in the next dialog and click “Next”.
f. Key in Name and company in the next dialog and click “Next”.
g. Accept the license agreement by clicking “Yes”.
h. Select “Server and Client Tools” in the next dialog and click “Next”.
i. Use “Default” in the next dialog and click “Next”.
j. Select “Typical” in the next dialog and click “Next”.
k. Select “Use the local system account” in the next dialog and click “Next”.
l. Select “Windows Authentication Mode” in the next dialog and click “Next”.
m. Click “Next” in the next dialog
n. Keyin “10” in field “Per Seat for..” and click “continue”
o. The installation starts
p. When done, click “Finish”.
SQL Server SP2 or higher
1. We installed SP 3 for SQL Server. Again use the default settings. If different from defaults, it is printed bold:
a. Double click Setup.bat in SP3 folder
b. Click “next” in dialog “Welcome”
c. Accept the license agreement by clicking “Yes”
d. Click “next” in dialog “Instance name”
e. Use default in dialog “Connect to Server” (Microsoft Authentication). After validation of user a message popped up telling the password is “blank”. Key in the administrator password (2x) and click “OK”.
f. Select second option “Upgrade Microsoft Search and apply SQL Server 2000 SP3” in dialog “SP3 Setup” and click “Continue”.
g. Click “OK” in dialog “Error reporting”.
h. Click “Next” in dialog “Start copying files”.
Installation starts.
i. When finished, a dialog comes up to explain to create a backup. Click “OK”.
j. Click “Finish” to exit Setup.
WSS Setup
The file STSV2.EXE is a self extracting executable. Start it by double clicking and it will unpack in the folder c:\Program Files\STS2Setup_1033. The number 1033 stands for the English version. A Dialog will be started automatically as soon as the file is unpacked.
1. Exit the automatic Setup dialog by clicking “Cancel”.
a. Click “Start/Run”.
b. Open Explorer and navigate to \Program Files\STS2Setup_1033.
c. Drag “setupsts.exe” to the input field in “Run” and “remotesql=yes”. Don’t forget the blank in front of it.
d. Start with “OK”.
2. Again the setup dialog opens.
3. accept the license agreement and click “Next”
4. Select “Server Farm” in the next dialog, Click “Next”.
5. Click “Install” in the next dialog.
When the installation is finished, Internet Explorer opens.
Configure Virtual Server
1. You can now configure Virtual Server. Before you do so, you need to check that SQL server is started.
2. Do NOT close the window “Configure Admin Virtual Server”, but follow the instructions below:
a. Click “Start\Programme\Microsoft SQL Server” and select “Service Manager”
b. A dialog “SQL Server Service Manager” opens. Select “Start/Continue”, if not already started.
c. It should already be started but it may appear that it has to be started manually.
d. Close the dialog and go back to configure the virtual server.
3. On page “Configure Admin Virtual Server” in the section “Application Pool”, select “Create a new application pool” and key in a name like “SEpool”. Also select “Configurable”, enter a user name using the syntax “Hostname\username” (stlug\administrator). Click “OK”.
4. On page “Application Pool Changed” you find the information that iisreset has to be started in a Command Prompt. Do so and than click “OK”.
5. On page “Set Configuration Database Server” in section “Configuration Database” key in the hostname in the field “Database Server”, a name in the field “SQL Server Database name”. All other settings are default settings. Click “OK”.
6. The page “Central Administration” opens. In section “Virtual Server Configuration” click the link “Extend or upgrade virtual server”.
7. On page “Virtual Server List” select “Default Web Site”.
8. On page “Extend Virtual Server” in section “Provisioning Options” select the link “Extend and Create a Content Database”.
9. On page “Extend and Create a content database” in section “Application Pool” select option “Use an existing application pool” and from the pull down select the pool you just created.
At the bottom of the page in section “Site Owner”, enter an email address in the field “E-Mail”.
Scroll down and click “OK”. When finished click “OK” again.
10. On Page “Virtual server Settings” under the heading “Virtual Server Management”, select “Virtual server General settings”. Scroll to the bottom of the page and turn on “Event Handlers”
11. Before you continue the installation you should follow the following instructions:
a. Install Insight Server V15
12. These next steps are only necessary if you are loading a different language.
a. Change the security settings of Internet Explorer to ?medium“.
(this is to be able to modify the webpart page later)
b. Edit the file “onet.xml”. You find this file in
c:\Program Files\Shared Files\Microsoft Shared\web server extensions\60\template\1033\STS\XML.
Look for the section starting with “Project Title=” and insert the following:
CustomJSUrl=”/_layouts/[%=System.Threading.Thread.CurrentThread.CurrentUICulture.LCID%]/custom_ows.js”
The finished entry looks like this:
ws=”Microsoft SharePoint” CustomJSUrl=”/_layouts/[%=System.Threading.Thread.CurrentThread.CurrentUICulture.LCID%]/custom_ows.js”>
Blue Text has already been there, red text was added.
13. Open Internet Explorer and enter “https://hostname” in the address field. You will need to login.
14. On page “Template Selection” select “Teamsite” from the list to the right. The Teamsite is like a Workspace and represents the highest level. Click “OK”.
15. On page “Home” select “Create” in the blue tool bar.
16. On page “Create Page” select “Document Library” in section “Document Libraries”.
17. On page “New Document Library” enter a name. In section “Document Versions” activate “Yes” for the creation of versions and click “Create”.
18. Start “Start/Programs/Insight Server V15/Workspace Editor” and add the Solid Edge attributes to the Library you just created.
Note: If new sites or document libraries have been created before Insight Server is installed, you can not use Webparts or Insight with it. To make sure Sites and Libraries work properly with Webparts and Insight, they need to be created after Insight Server is installed.
In case the main site has already been created you can create Subsites after you installed Insight Server.
1. Open the Teamsite Homepage and click “Create” on the blue toolbar.
2. On page “Create Page” scroll down and select “Sites and Workspaces” in section “Web Pages”.
3. On page “New SharePoint Site” enter the Title. In section “Web Site Address” enter a name in field “URL name”. Click “Create”.
4. On page “Template Selection” select “Teamsite” and click “OK”.
5. This creates a new Homepage. Here you create a new document library (see topic 13 – 15 above).
6. Now you need to be aware that you need to use the syntax “subsite\document library” when applying the Solid Edge attributes using Workspace Editor because otherwise you get an error message that this workspace does not exist.
Installation of web parts
It is important to know that at this time (build 54) some files have to be copied manually to make the web parts work correctly.
Copy the files “InsightUtils.dll” and “WebServicesClient.dll” delivered in “..Solid Edge\Program” or “..\Insight Connect\Program” to the folder “Winnt\assembly” (for Windows 2000) or “Windows\assembly” (for Windows XP).
Also you need to install a client (Insight Connect or Solid Edge) on your server to be able to display the web parts.
Installation of Web Parts on Server:
1. Before creating Web Parts navigate to your “Home Page” and create a Document Library for the Web Parts.
2. On page “Home” select “Create” in the blue tool bar.
3. On page “Create Page” select “Document Library” in section “Document Libraries”.
4. On page “New Document Library” enter a name such as “Web Parts”.
5. Next we need to create a Web Part Page. Do the following:
6. On page “Create Page” find the section “Web Pages” and select “Web Part Page”.
7. On page “New Web Part Page” enter a name such as “Solid Edge Web Parts”, then select the layout for the page and define where the page should be saved from the pull down list. Here you will select the “Web Parts” document library that you just created. Click “Create” to create the Web Parts page.
8. Navigate to your “Solid Edge web Parts” page. The path will read something like “https://hsvnt179/Web%20Parts/Solid%20Edge%20Web%20Parts.aspx”
9. Copy the address of your web part page from the address field in Internet Explorer. Include the entire path shown above.
10. Navigate to “Program Files\Shared Files\Microsoft Shared\web server extensions\60\Template\Layouts\1033 and open the file “custom_ows.js” using an editor like notepad. You will find a variable named “L_Path_to_SEWebPartPage_Text”. Here you will find a marker , replace this marker with the address you just copied from Internet Explorer. Save the file and close it.
11. Make sure, the PATH variable of your system has the path to stsadm.exe included. If not, add “c:\Program Files\Shared Files\Microsoft Shared\web server extensions\60\BIN” to the PATH variable.
12. Now install the web parts. Open a Command Prompt and navigate to “..\Program Files\Insight Server V15\Web Components”. Start “installwp.bat” using a qualifier “.” (dot) so the command is “installwp.bat .”
13. Open your web part page in Internet Explorer and click “Modify Shared Page”, select “Add Web Parts” and “Browse”. Click on “Virtual Server Library”, where you will find the web parts.
Note: If you get an error message when opening the web page to view parts, delete your cache and the cookies from Internet Explorer. Start the page again. |