Post on 28-Oct-2015
description
SAP
SRM 4.0 Installation Procedure
SRM 4.0 Installation Date: 07‐Nov‐2005
Server: BG3SAPC (BDC) Oracle Database Installation: Setting up the Oracle Home Name and its path.
Select the No Option as SAP has its own DB.
Applying the Oracle Patch
Installing the SRM Server Central instance
Enter the SAP System ID and it’s Instance Number
Enter the Database ID
\
Use the default parameters and Select the Installation type of your choice
Go with default values and select the Instance Installation Drive
Enter the password for the <sid>adm
Lionel123
Enter the Password for SAPService<sid>
Lionel123
Enter the Location of the Kernel CD
Click on Next selecting the Default Values
Enter the Location of the IGS Folder
Verify and Confirm the Parameters for Starting the Installation of the Central Instance
Installing the DB Instance
Select the No Option
Verify and Confirm the Parameters for Starting the Installation of the Database Instance
Password for DDIC & SAP* Users
Installing the Java Stack
Do not use <sysidadm> for installation of Java Stack. This would help in avoiding many of the Java user related errors. Refer Note 676072 & 699557 Also, upgrade the Kernel to the latest Patch and also create a new client before you start Installing the Java Stack.
To rectify this error set the DDIC password as “19920706” (the default password)
Error in Java Web AS where J2EE_ADMIN user cannot login due to “No server running” Refer the below mentioned note as a solution to the above problem.
SP13 Installation
Click Ok and continue…
To resolve the above error Refer Note 737099
Solution: Open KEYDB.xml in notepad which is at location C:\Program Files\sapinst_instdir\SRM04SR1\WEBAS\ERP_10_JAVA and search for the 1st ERROR string and replace it with OK
To avoid the above Problem, ideally update the Kernel to the latest Level before installing the Java Stack. Check the lock status of User SAPJSF (unlock if getting locked) ***SAP Note 802600 for Java Parameters***
TREX Installation
Create a Admin User with all access for the Installation
Leave all fields Blank in the Below Screen for Proxy Settings for TREX
The issue was that there already existed a Version of Python. There should not be an existing version of Python before Installing TREX. If Yes Uninstall the Python Version as TREX does an Installation of Python as a prerequisite.
TREX 6.1 SP14 Installation
Download the Installable from the Market Place:
During the Installation there is an error that one comes across as below that the pythonsetup.exe was not found:
ERROR 2006‐02‐10 15:15:15 FSL‐06002 Error 2 (The system cannot find the file specified. ) in execution of a 'CreateProcess' function, line (278), with parameter ("E:/New_kernel/TREX 6.1/TREX6.1_SP14/PYTHON/NT/I386/pythonsetup.exe" /s "/v/qn INSTALLDIR=C:\usr\sap\Python /l! C:\usr\sap\trex_02\pythonsetup.log"). For this you would need to replace the file contained in the location E:/New_kernel/TREX 6.1/TREX6.1_SP14/PYTHON/NT/I386/ as shown below in the screenshot
With the executable pythonsetup.exe which is found in the TREX 6.1 Installation download from the Installation & Upgrades link in the Marketplace
IPC Installation
IPC Patch
IPC 4.0 SP06 Installation
Download the executables from the Market Place as shown below. Also, remember that the SP06 IPC 4.0 executable contains IPC 4.0 with Patch Version SP06.
Contents OF IPC Properties after Installation: Manifest‐Version: 1.0 Main‐Class: About Specification‐Vendor: SAP AG, Walldorf Specification‐Title: SAP Internet Pricing and Configurator Patch Specification‐Version: 4.0 Archive‐Date: February 2 2006 at 0417 Hours Patch‐Version: IPC4.0_SP06 Build‐ID: 4.0.06.200602020305.64949 Modifications to be done in dispatcher.properties file after Installation: pingInterval = 100000 rfcEnabled = true rfcGateways = bg3sapc:sapgw00 rfcDispatcherProgId = IPC_RFC_DISPATCHER rfcServerCount = 1 rfcServerProgIdPrefix = IPC_RFC_SERVER_
Patching IPC
Installation of Live Auction Cockpit
Post Installation Configuration: Defining a Web Alias:
1. Make sure that the SAP J2EE Engine is up and running. 2. Open the SAP J2EE Engine Administration tool at the location <INSTDIR>:\usr\sap\<sapsid>
\<instancenumber>\j2ee\admin\go.bat
3. Login with the SAP J2EE Engine administrator password and click Connect. 4. In the navigation pane, choose Server Servcices HTTP Provider 5. Select the Runtime tab. 6. Select the Aliases tab. 7. Enter srm/lib/resources. 8. Enter Path INSTDIR>:\usr\sap\<sapsid>\SYS\global\srmla\resources 9. Click Add.
10. Click Save Properties.
11. Exit the SAP J2ee Admin tool. Configuring JCo Settings:
1. Stop the Sap J2EE Engine.
2. Launch the SAP J2EE Engine Config Tool at location <INSTDIR>:\usr\sap\<sapsid> \<instancenumber>\j2ee\configtool.bat
3. Switch to Configuration editor mode.
4. Choose configurations aaps sap.com com.sap.srm.la appcfg
5. Switch between view and edit mode
6. Double Click on the Propertysheet application.global.properties
7. Change values for the Properties as required. Take care to check / change the following Properties jco.client.client jco.client.user JCo User Profile Settings: This user must be defined in the SAP system and should be of type Communication or System also must have the Purchaser and Bidder Roles assigned and the assign the Profile S_BTCH_ADM
jco.client.passwd jco.client.ashost jco.client.sysnr jco.client.r3name jco.cleint.mshost srmla.um
8. After one is thru maintaining the properties exit the SAP J2EE Engine Config Tool and start the SAP J2EE Engine.
The below mentioned IMG Settings are created by default once the LAC has been successfully installed. In any case if they are not they need to be configured. IMG Settings: Maintaining the Backend Destination 1. Go to Transaction SM59. 2. Create an RFC Destination with the Key SRM_LIVE_AUCTION and connection type G.
3. Enter the LAC server as the Target Host(use the fully qualified Domain name or IP address) and it’s port number as the Service No. The port number consists of the Instance number that is used during the installation (5<instance number>00). For ex ; if during installation the instance number used was 00 then the port number would be 50000.
4. Test the connection to see whether EBP cal locate the external Server for the HTTP Service. If the status bar shows ICM_HTTP_CONNECTION_FAILED then the RFC connection needs to be checked and rectified.
Maintaining Definition of Backend System in B2B 1. Execute T‐Code SM31. 2. Maintain table / View BBP_BACKEND_DEST. 3. Click new Entries 4. Select the destination for which you wish to configure this EBP Client
5. Select SRM Live Auction from the dropdown list for System type.
6. Save Settings and exit.
Maintain Number Range for Transaction Types 1. Execute T‐Code bbp_num_auc. Choose Change Intervals
2. Maintain number ranges accordingly and save your settings
Configuring Properties for LAC: Customized properties for LAC will be delivered as part of the SAP system delivery in Client 000. If the Client for LAC is no the default 000, then compare and adjust the entries, for view BBPV_LA_PROP, in the LAC client so that the entries there are identical to those in Client 000. **** An RFC connection to the client 000 of the SAP system must be configured first. **** 1. Execute T‐Code SM31 (on the LAC Client). 2. Maintain Table / View BBP_LA_PROP. 3. The Live Auction Properties Management page is displayed. 4. Choose the menu path Utilities Adjust
5. Enter the R/3 Connection that points to Client 000 and press Enter.
6. The comparison result screen is displayed, Choose the menu path Edit Select Select all. 7. Choose the menu path edit Adjust , this displays the Adjust page. 8. Choose Edit Adjust Copy all entries. 9. Press F3 twice , save the settings and exit.
Live Auction Cockpit Smoke Test After installation is completed, open your web browser ad type the URL: http://<appservername.domain>:<default‐port~50000>srm/la
1. Click on UME Logon screen. 2. Logon with a valid user (assigned the Purchaser Role)
If user management is properly configured, the following message is displayed: SSO Cookie detected and successfully verified by UME
Click on Launch Applet and you would be displayed the following screen, which would confirm the successful installation of LAC:
cFolders Configuration Introduction The purpose of this document is to describe the way the cFolders 3.10 is configured and integrated into SRM 4.0 Step 1 Create the cFolders URL by starting transaction SICF. Click on External Aliases.
Step 2 Select the ‘default host’ and Click on the Create icon.
Step 3 Enter a name and description for the external alias in the External Alias and Description fields in the format “/<External Alias Name>”. The entry is case sensitive which is important when you enter an address in the browser address line. On the Service Data tab, enter a client number (this number is supposed to be the client that cFolders is being set up for).
Step 4 In the same dialog box, choose the “Trg Element” tab page. In the “Virt. Hosts/Services” column choose default_host → sap → bc → bsp → sap and double‐click this folder. The URL /default_host/sap/bc/bsp/sap appears under the “Trg Element: “entry.
Choose to save the entries and to cancel.
Step 5 Activate the services by running transaction SICF. In the Virt. Hosts / Services column, go to default_host → sap → bc → bsp → sap →cfx_rfc_ui. Open the context menu by right‐clicking on cfx_rfc_ui and choose “Activate Service”.
Step 6 In the Virt. Hosts / Services column, go to default_host → sap → bc → kw → cfs. Open the context menu by right‐clicking on cfs and choose “Activate Service”.
Step 7 Start transaction SICF, in the Virt.Hosts/Services column, select the default‐host text and then click on the
External aliases icon. The Maintain external aliases screen appears. Select the default‐host text in the Virt. Hosts/Services column and to
create a new external alias, choose Create . The Maintain external aliases dialog box appears. Enter a name and a description for the external alias in the External alias and Description fields. When you enter the external alias, use the following entry format: "/<Alias Name>". For example, " /idcdemo‐cfolder‐settings”
Step 8 In the same dialog box, choose the “Trg Element” tab page. In the “Virt. Hosts/Services” column choose default_host → sap → bc → bsp →
sap and double‐click this folder. The URL /default_host/sap/bc/bsp/sap appears under the “Trg Element: “entry. Choose to save the
entries and to cancel.
You can now access the cFolders settings through a WebDAV client.
Step 9 Click on Start My Network Places. Configure a new and connect a network place for the cFolders WebDAV URL
Step 10 Click on “Add new network places” and then Next.
Step 11 Choose Next and the “Choose another network location”. In the” Internet or Network Address” field, type in the specified URL setting in the format: http://<Server>:<Port>/<Special External alias for cFolders settings> Click on Next. A log on pop up will appear, put a user name and password and click on enter (the user must have been assigned the SAP_CFX_ADMINISTRATOR role).
Step 12 In the WebDAV folder, copy and paste the SRM folder on the desktop and then modify the XML file in it by renaming the file SRM.xml and then editing the system ID and the RFC destinations. Note: Some folders might not be there, they would have to be created.
Copy of the XML code. <?xml version="1.0" encoding="UTF‐8"?> <SRMType ID="IBS" Namespace="" RFCDestination=" IBS " cFoldersDestination="NS1" xmlns="http://www.sap.com/2003/abap/cfx_integration/customizing/SRMType"> <DataTypes> <DataType ID="string" Namespace="" Type="string" Length=""/> </DataTypes> <PropertyLists> <PropertyList> <Heading Alias="CFX_UI/SRM_HEADER_DATA" Default=""/> <Properties> <Property> <Fields> <Field ID="Name" Namespace="" DisplayLines="" IsConstant="false" IsEntryRequired="false" > <Label Alias="" Default=""/> <DataTypeRef ID="" Namespace=""/> <ABAPField TableName="BBPS_EXTREQ_HEADER" FieldName="DESCRIPTION" RFCDestination=" IBS "/> <DefaultValue Value=""> </DefaultValue> </Field> </Fields> </Property>
<Property> <Fields> <Field ID="PostingDate" Namespace="" DisplayLines="" IsConstant="false" IsEntryRequired="true" Visibility=""> <Label Alias="" Default=""/> <DataTypeRef ID="" Namespace=""/> <ABAPField TableName="BBPS_EXTREQ_HEADER" FieldName="POSTING_DATE" RFCDestination="NS1"/> <DefaultValue Value=""> </DefaultValue> </Field> </Fields> </Property> </Properties> </PropertyList> <PropertyList> <Heading Alias="CFX_UI/SRM_ITEM_DATA" Default=""/> <Properties> <Property> <Fields> <Field ID="Itemdesc" Namespace="" DisplayLines="" IsConstant="false" IsEntryRequired="true" Visibility="" > <Label Alias="" Default=""/> <DataTypeRef ID="" Namespace=""/> <ABAPField TableName="BBPS_EXTREQ_ITEM" FieldName="DESCRIPTION" RFCDestination=" IBS "/> <DefaultValue> </DefaultValue> </Field> </Fields> </Property> <Property> <Fields> <Field ID="Itemdate" Namespace="" DisplayLines="" IsConstant="false" IsEntryRequired="true" > <Label Alias="" Default=""/> <DataTypeRef ID="" Namespace=""/> <ABAPField TableName="BBPS_EXTREQ_ITEM" FieldName="DELIV_DATE" RFCDestination=" IBS "/> <DefaultValue> </DefaultValue> </Field> </Fields> </Property> <Property> <Fields> <Field ID="CostCenter" Namespace="" DisplayLines="" IsConstant="false" IsEntryRequired="true"> <Label Alias="" Default=""/> <DataTypeRef ID="" Namespace=""/> <ABAPField TableName="BAPI_ACC_C" FieldName="COST_CTR" RFCDestination=" IBS "/> <DefaultValue>
</DefaultValue> </Field> </Fields> </Property> <Property> <Fields> <Field ID="InternalNote" Nameslpace="" DisplayLines="3" IsConstant="false" IsEntryRequired="false" Visibility="internal"> <Label Alias="CFX_UI/SRM_INT_NOTE" Default=""/> <DataTypeRef ID="string" Namespace=""/> <DefaultValue> </DefaultValue> </Field> </Fields> </Property> </Properties> </PropertyList> </PropertyLists> </SRMType> The RFC destinations should be changed to a local RFC destination configured for the system Step 13 In the WebDAV folder, copy and paste the System Settings folder on the desktop and then modify the ‘layout.xml’, ‘network.xml’ and ‘system.xml’ XML files.
• Modify the ‘layout.xml’ file in the following way:
<?xml version="1.0" encoding="utf‐8"?> <settings created="20051123191435 " name="layout"> <Images> <Logo></Logo> <LogoMiddle></LogoMiddle> <LogoRight></LogoRight> </Images> <DISPLAY_BANNER>false</DISPLAY_BANNER> <StyleSheet></StyleSheet> <Notification> <display_time_in_ov>true</display_time_in_ov> </Notification> <Display_seconds_in_times>true</Display_seconds_in_times> <User> <Settings> <Appearance> <EnableEditing>false</EnableEditing> </Appearance> </Settings> </User> </settings>
• Modify the ‘system.xml’ file in the following way: <?xml version="1.0" encoding="utf‐8"?> <settings created="20051123191434 " name="system"> <SupportedObjTypes>dis###txt</SupportedObjTypes> <DiagnosisOptions>false</DiagnosisOptions> <UseScenarioCollaboration>false</UseScenarioCollaboration> <UseScenarioCompetition>true</UseScenarioCompetition> <PGP_SUPPORT_ACTIVE>true</PGP_SUPPORT_ACTIVE> <PGP_CLSID_TO_APPLICATION/> <PGP_LPVERB_TO_APPLICATION/> <Default> <UseScenarioStandardParts>false</UseScenarioStandardParts> <UseNetworkAdminiistration>false</UseNetworkAdminiistration> </Default>
</settings>
• Modify the ‘network.xml’ file in the following way: <?xml version="1.0" encoding="utf‐8"?> <settings created="20051123191435 " name="network"> <AbsoluteBaseUrl> http://<Server>:<Port>/<Absolute URL for cFolder</AbsoluteBaseUrl> <Proxy> <Host></Host> <Port></Port> </Proxy> <FTP_BOX_active>false</FTP_BOX_active> <FTP_BOX_Server/> <FTP_BOX_Basepath/> <FTP_BOX_User>ftp</FTP_BOX_User> <FTP_BOX_Password>ftp</FTP_BOX_Password> <FTP_BOX_name/> <CS_directly>false</CS_directly> <AutoVue> <Active>false</Active> </AutoVue> <WebEx> <MeetingActive>false</MeetingActive> <MeetingSite>https://sap‐cfolders.webex.com/sap‐cfolders</MeetingSite> <DurationMax>15</DurationMax> <FolderName>WebEx‐meetings</FolderName> <MeetingAssistenUpdateSeconds>60</MeetingAssistenUpdateSeconds> <UseDemoSite>false</UseDemoSite> <EmailInvitation>false</EmailInvitation> </WebEx> <EMail> <UseAlternativeSenderAdress>false</UseAlternativeSenderAdress> </EMail> </settings> Step 14 Create a system user CF_RFC in the system and assign the SAP_CFX_ADMINISTRATOR and SAP_CFX_USER roles to it (ensure that profiles are generated for these roles). Start transaction SM59 and create an RFC connection cFolder, of connection type 3 (R/3 connection). On the Technical Settings tab, fill in the target host of the local system, the system number and the IP Address radio button.
Step 15 Click on the Logon / Security tab. In the Logon, fill in the Language, Client, User and Password fields. The user will be the system user created above in step 14 and the client will be the client where the user was created and will be used (in this example client 300). Click on the Test connection icon to test the connection and then F6 to test the authorization and then save the connection.
Step 16 Start transaction SPRO. Go to SAP Reference IMG Collaboration Projects Define Absolute URL for calling cProjects. Fill in the absolute URL for calling cFolders in the format:
http://<Server>:<Port>/<External alias>cfx_rfc_ui
Click on save .
Step 17
Start transaction SPRO. Go to SAP Reference IMG Collaboration Projects Documents Specify URLs for Windows File Explorer Integration.Fill in the URL for windows File Explorer Integration in the format: http://<Server>:<Port>/<External alias>cfx_rfc_ui
In the ID field choose “Communication ACC. To SOAP Convention File Explorer – WAS and click on save .
Step 18 Start transaction SPRO. Go to SAP Reference IMG Collaboration Projects Connection to External Systems cFolders Integration Stipulate RFC Destination for Collaboration. Click on New Entries. Step 19 Fill in the “Destination” field and fill in the cFolder RFC destination for the client and then save this.
Step 20 Start transaction BD54. Create a logical system for the cFolders system. Save this.
Step 21 Start transaction SPRO. Go to SAP Reference IMG Supplier Relationship Management SRM Server Technical Basic Settings Define Backend Systems. Click on New Enteries.
Step 22 Fill in the field with the required information: In the Logical system field, fill it with the logical system created for cFolders:
Step 23 In the Description field, fill in a description. Step 24 In the RFC Destination field, fill in the cFolder RFC connection to the system Step 25 In the “Sys. type” drop down, choose “PLM cFolders ab Release 2.0.
Step 26 Tick the “Local” field and in the “FI valid” field choose ‘no validation of FI data”.
Step 27
Choose the cFolder RFC destination for the system in the “RFC –Destination” field. After filling this, click on save .
Step 28 Log into the cFolder frontend using the defined external alias in the form, by typing it in a browser: http://<Server>:<Port>/<External alias>cfx_rfc_ui/default.htm Click on the Settings icons and then on the General Tab. Tick the Plug – in and File explorer on the on the General tab. Click on “Install software for the integration of SAP cPrpject Suite in Microsoft Windows File Explorer”. This will install the cProjects file explorer.
Step 29: Click on Network Administration and then the Network tab. In the “Absolute URL of the Application” Field, fill in the absolute URL defined for calling cFolders and then Save.