NetWeaver Installation and Introduction

装NetWeaver就像噩梦，回想起以前安装win98,win2k,winxp,同学都笑我重装大王，一个星期一次，有时候一下午装几次。我自己也怕，从这个过程我成了高手，不再怕它，而是玩它。刚开始还用软盘作驱动，我的光驱也不怎么好，于是我设计N种方法重装。软盘很容易坏，嗤嗤的响，经常坏，我就弄了一大堆坏盘。大一的时候CAD中心向我们捆绑卖软盘，花了几十块。过了一两年优盘流行了，还有mp3。

言归正传。NetWeaver有2004s产品光盘，网上也能下载Java stack 和ABAP stack trial版。前者是正式产品，干净的，后者要新一些，不稳定，带一些开发数据。ABAP edition就是所谓的minisap了。试用版是分开的，可以装在同一台机子上，这样没有PI(XI)了。源文件各2-3G，安装后20G左右（大部分是数据库占用的）。
还有SAP ERP2005和ECC6.0 IDES版,两者源文件30G左右，安装后要200G-300G空间。IDES就是学习版，比2005对硬件要求低一些，我在HP server(8G memory+640G SCSI+Xeon 2.66G)上没装成功。当然可以只装SAP ERP2005中的NetWeaver platform，也就是ABAP APP(ERP)没有。

安装准备。下载JDK1.42.09和JCE.一个稳定的网卡，因为安装程序是JAVA的，SAPinst GUI通过网络连接后台。可以安装Microsoft loopback Adpter,虚拟一个网卡，并设置IP。安装前不稳定的网卡禁用掉，安装程序貌似会选择活动的网卡。因为我有无线网卡，无线网络会时常中断。
获得solution manager key.登陆solution manager运行Tcode SMSY.输入你的host name, system ID, instance number .你也可以在网上找一个，设置你的系统用别人的key。
安装很漫长，你可以用VPN+remote desktop connection远程安装，不耽误回家看电影睡觉。
操作系统win2003 server, XP也许不行。必须是NFS文件系统，否则无法继续安装。
安装中断后，找出问题可以继续上一次安装。
安装前设置参数，要多次指定原文件路径，很烦人。
Mater password 默认 abcd1234 就是系统所有账户的默认密码包括J2ee_admin, administrator,sap*, DDIC，及BI,PI相关的用户等

装好后。SAP Management Console start or shut down the system.
Client copy.sale define logic system. SCCL -local copy, SCC9 -remote copy.
开账户，登陆SAP GUI,PFCG - profile generator. SU01 - user maintain,懒人就assign一个 SAP_ALL吧，还需要权限就自己加！

Portal http://[hostname]:(50000+instance no.)*10/ SAP J2EE engine start page. system information 察看 system ID, port等信息；/useradmin User management(UME) 管理portal上的权限，用户名密码和ABAP里的一样。
Web Dynpro administrator 管理WD app.
/nwa SAP NetWeaver administartor 提供Visual administrator里的部分功能。
/irj portal，整合了所有应用，有所有权限就可以看到全部菜单。
system administration-->system configuration重要的配置入口。
Guided Procedures GP
/devinf SAP NetWeaver Development Infrastructure(NWDI)入口,包括cbs,cms,dtr
/VC Visual Cmposer
/caf composition application framework config
/sld System Landscape Directory. a tool of product management.
/rep Exchange infrastruture XI 入口,这里启动 Integration repository and Directory(design and configue)

J2EE related
SAP NetWeaver Developer Studio (NWDS): CAF,Web Dynpro for Java.
Configure
SAP J2EE Engine, host:--, message server port:3900
JDI URL http://iwdfvm2160.wdf.sap.corp:51000
Fully Qualified Domain Names (FQDN) problems, edit hosts at c:\windows\system32\drivers\etc\
10.1.254.59 SAPDiscoverySystem iwdfvm2160 iwdfvm2160.wdf.sap.corp
Visual Administrator in usr\sap\\DVEBMGS10\j2ee\admin\go.bat 大量配置信息，比如start,deploy,remove applications;Adapters,Connectors,Destinations.
J2EE Engine Config Tool, configre the server.
SDM RemoteGui -Software Deployment manager

useful transaction codes
for ABAP
SE11 ABAP Dictionary Maintenance
SE16 Data Browser
SE24 Class Builder
SE37 ABAP Function Modules
SE38 ABAP Editor
SE51 Screen Painter
SE63 Translation
SE80 Object Navigator
SE84 Repository Information System
SE93 Maintain Transaction Codes
SEARCH_SAP_MENU Find in SAP Menu
SEARCH_USER_MENU Find in User Menu
SMARTFORMS Smart forms
ABAPHELP Key word documentation
ABAPDOCU Example library
BAPI BAPI explorer
ST22 ABAP dump analysis
ST05 Performance Analysis

And others
PFCG Profile Generator – Activity Groups
SCC0 Client Copy
SCC9 Remote Client Copy (between clients in different systems)
SCCL Local client copy (within one system, between different clients)
SM02 System Messages
SM04 User List
SM50 Workprocess Overview
SPRO Start SAP IMG
SQ00 ABAP/4 Query – Query Initial screen
ST01 System Trace
SU01 User Maintenance
SU10 User mass maintenance
STMS Transport Management System
WE20 Partner Profiles
WE21 Maintain a port and assign a RFC destination
WE30 Develop IDoc Types
IDX1 Port Maintain in IDoc Adapter
RZ70 System landscape directory :Local Administration
WE02 Idoc List
WSADMIN Web Service administration
SLDCHECK Test SLD Connection
SALE ALE settings
BD54 Maintain Logical System
SICF HTTP Service Hierarchy Maintenance
RSA1 Modeling - Data Warehousing Workbench
RSA6 Maintain DataSources
SMGW Gateway Monitor
SMICM ICM Monitor
SM59 Configuration of RFC connections
SMLG Logon Groups
--the end

SAP NetWeaver 2004s SR1 Installation guide ABAP+Java windows Oracle

Basic SAP System Parameters
SAPinst then creates by default client 001 as the production client for the ABAP part of your SAP system. The ABAP part of the system initially contains only clients 000 and 001.
You can install the Java Add-In to an already existing ABAP system.
You can change the default names of the Java users J2EE_ADMIN, J2EE_GUEST and SAPJSF during the input phase of the installation.
SAP System ID The SAP System ID identifies the whole SAP system.
Instance Number: Technical identifier for internal processes, consisting of a two-digit number from 00 to 97.
ABAP/Java Message Server Port
The external message server port uses the parameter rdisp/msserv with default value 36, where is the instance number of the ABAP message server instance.
The internal message server port uses the parameter rdisp/msserv_internal with default value 39.
ABAP RFC User, Password
The user DDIC is normally used for the RFC logon ABAP RFC user. It has the required special administrator rights. Alternatively, you can use user SAP*.
Java users Administrator Name:
SAPinst sets the user name J2EE_ADMIN by default. If required, you can choose another user name according to your requirements.
SAPinst sets the following user names by default.
n For the Java part of an ABAP+Java system: J2EE_ADMIN
n For a Java system: Administrator.
Communication User Name: This user is used for the communication between the ABAP and the Java part of an ABAP+Java system. SAPinst sets the user name SAPJSF by default.
Master Password This password is used for all user accounts SAPinst creates and for the secure store key phrase. The length has to be 8-14 characters. Depending on your installation scenario there might be more restrictions.
Enterprise Portal URL The portal URL consists of the following:
http://:/irj
SLD HTTP Host The host name of the System Landscape Directory (SLD)
SLD HTTP Port The HTTP port of the Java system where the SLD is installed. The following naming convention applies:
500.
SLD Data Supplier User and password n
If you want to install a local SLD, SAPinst creates this user during the installation. If you want to connect your system to an existing central SLD, you have to enter the existing SLD Data Supplier User and password of the central SLD during the installation.
We recommend that you name this user SLDDSUSER
SLD ABAP API User and password n
If you want to install a local SLD, SAPinst creates this user during the installation. n If you want to connect your system to an existing central SLD, you have to enter the existing SLD Data Supplier User and password of the central SLD during the installation.
We recommend that you name this user SLDAPIUSER
RFC User, Password The ABAP RFC user of the SLD ...
Code page The code page that is used by your database (Unicode or Non-Unicode).
Database schemata, Passwords The Java database schema is namedSAPDB. Default name is SAPSR3DB. The ABAP database schema is named SAP. Default name is SAPSR3.

Running Adobe Document Services on Non-Supported Platforms
Adobe document services (ADS) are currently not supported to run natively on all platforms supported by SAP systems based on SAP NetWeaver, in particular on 64-bit platforms.
Procedure
To use ADS in SAP landscapes on non-supported platforms, install an additional standalone AS Java on a platform supported by ADS.

Usage Type Development Infrastructure
The SAP NetWeaver Development Infrastructure (NWDI) is the environment for all processes in Java-based development and software life-cycle management. You can centrally manage all development phases with the Change Management Service (CMS), from the definition of a central development environment for each software project through to quality management and production. The CMS controls the management of sources in the Design Time Repository (DTR) and archives in the Component Build Service (CBS). The component model adds metadata to Java-based projects, which is the basis for the new development process.
There are the following Java development scenarios with SAP NetWeaver:
n Scenario “Java Projects with Central Source File Storage”: development with central source code version control only Scenario “Developing Components with the NWDI”: all services of the Development Infrastructure and the SAP component model are used

SAP recommends to perform a domain installation.
1. Check that you have Domain Administrators rights.
Logging On to the SAP System
You need to check that you can log on to the SAP system using the following standard users.
ABAP Usersser User Name Client
SAP* 000, 001, 066
DDIC 000, 001
ABAP+Java UserUseAdministrator J2EE_ADMIN
Java Standalone Users Administrator Administrator

Logging On to the J2EE Engine
1. Start a Web browser and enter the following URL:
http://:500

Establishing the Portal URL
http://:/irj

Generating the SAP Solution Manager Key
1. In your SAP Solution Manager system, call transaction SMSY (System Landscape Maintenance).

Performing Initial ABAP Configuration

Configuring the transport management system

1,Set up operation modes transaction RZ04
2,Set up logon groups transaction SMLG
3,Set up administrators
4,Schedule background jobs
5,Install a printer
6,Configure the system log

Installing languages using transaction I18N:
Performing language transport using transation SMLT
Activating and configuring the integrated Internet Transaction Server (ITS),see SAP Note 742048

Post-Installation Steps for Adobe Document Services
1,Creating Role ADSCallers and Assigning it to ADSUSER(transaction PFCG).
Installation Check and Quick Tests for Adobe Document Services
Enter the following URL in your web browser:
http://:/AdobeDocumentServices/Config where
Checking the ABAP Connection
1. Log on to your SAP system.
2. Call transaction SE38.
3. Enter the name of the test report FP_PDF_TEST_00.

Performing Post-Installation Steps for CAF Core
In SLD
1. In the SAP System Landscape Directory (SLD), create a new project.
2. Create a new software component (SC) to be developed.
3. Create SCs of the build plug-ins for the dependent development component (DC). They are:
Archive Names
BI-MMR CAF-KM EPBC2 SAP_JTECHS
BI_UDI CAF-UM EP-PSERV SAP_PRT
BI-REPPLAN EC-JSTARTUP KMC-CM SAP-EU
BI-WDALV EP_BUILDT LM-TOOLS SAP-JEE
CAF EPBC SAP_BUILDT UWLJWF
4. Define the build plug-in dependencies created in step 3 above.
5. Define the SC dependencies created in step 2 above.

In CMS
1. In CMS, identify or create a domain.
2. Identify an existing track or create a new track for composite application development in
Landscape Configurator--> Creating a Development Track.
3. Add the SC created in step 2 in the section above to the track.
4. Add the runtime system of the track.
See Landscape Configurator--> Creating a Development Track--> Configuring Runtime Systems.
5. Check in the archives listed in the table below.
6. Import the archives into the track.

Configuring the BI Java Connectors
BI JDBC Connector
If you have not already done so, you must first deploy your datasource’s JDBC driver, performing the following steps:
a) Start the Visual Administrator. .
A) On your central instance host, change to the admin directory:
(path: \usr\sap\\\j2ee\admin):
B) Double-click go.bat.
b) In the Cluster tab select Server x--> Services--> JDBC Connector.
c) In the right frame, select the node Drivers on the Runtime tab.
d) From the icon bar choose Create New Driver or Data source.
e) In the DB Driver field in the Add Driver dialog box, enter a name of your choice for your JDBC driver.
f) Navigate to your JDBC driver's JAR file and select it.
g) To select additional JAR files, select Yes when prompted; if finished, select No.

Connection Properties for the BI JDBC Connector
USERNAME Data source user name User with at least reading authorization for the data source.(These authorizations differ according to the used data source.)
PASSWORD Data source password (your password)
URL URL string specifying the location of a database (used by the java.sql.DriverManager to determine which driver to use) jdbc:mysql://localhost/test
DRIVERNAME Class name of JDBC driver used for this connection com.mysql.jdbc.Driver

Checking the Connectors Implementation
After the configuration of the different connectors, you can perform a rough installation check by just displaying the different connector pages.
BI JDBC Connector http://:/TestJDBC_Web/TestJDBCPage.jsp
BI ODBO Connector http://:/TOdbo/servlet/TestOdbo
BI SAP Query Connector http://:/TSapq/servlet/TestSapq
BI XMLA Connector http://:/TXmla/servlet/TestXmla

Setting Environment Variable CPIC_MAX_CONV
1. Log on to your operating system as user adm.
2. Set environment variable CPIC_MAX_CONV to a higher value (at least 200) and restart the system.

Performing PI-Specific Steps for SLD Configuration
Local and Central System Landscape Directory (SLD)
Mapping Security Role to User
1. Log on to the Visual Administrator of the J2EE engine of the SLD host.
2. Choose Cluster® Server® Services® Security Provider.
3. In the Runtime tab, choose Policy Configurations and then the column Components, and select the component
sap.com/com.sap.lcr*sld.
4. Switch to the Security Roles tab to display the assigned roles.
5. Select role LcrInstanceWriterLD.
The user SLDAPIUSER already exists with its security role LcrInstanceWriterLD.
6. Switch to edit mode and add user PIAPPLUSER with the same role LcrInstanceWriterLD.
.
Maintaining SLD Connection Parameters (ABAP API)
1. Log on to the SAP XI Integration Server System as user DDIC and call transaction SLDAPICUST. The screen Maintain SLD Access Data is displayed.
2. Choose Display <-> Change and proceed as follows:
a) Replace the existing SLDAPIUSER with PIAPPLUSER user.
For a central SLD, make sure you use the user with security role LcrInstanceWriterLD.
b) Make sure your entry is marked as Primary.
Only the entry marked as Primary is active.
c) Save your settings.

Checking the CR Data in the SLD (optional)
Since CR_Content.zip contains all available SAP components, the content of this file grows with time. Theextensions contain information about new components (new releases and Support Packages, for example).
This content in the SLD has to be updated from time to time.

Ensuring User Security
Recommendation
In all cases, the user ID and password are only encoded when transported across the network.
Therefore,
we recommend using encryption at the network layer, either by using the Secure Sockets Layer (SSL) protocol for HTTP connections, or Secure Network Communications (SNC) for the SAP protocols dialog and RFC.

Operating system user
adm SAP system administrator
SAPService User to run the SAP system

Oracle database user
SAP Oracle database owner (that is, the owner of the database tables)
SYSTEM ‒
SYS ‒
OUTLN ‒
DBSNMP ‒

ABAP+Java Users
SAP* User exists at least in SAP system clients 000, 001 and 066.
DDIC User exists at least in SAP system clients 000 and 001.
EARLYWATCH User exists at least in SAP system client 066.
SAPCPIC User exists at least in SAP system clients 000 and 001.
Administrator The name that you gave this user during the installation or the default name J2EE_ADMIN
Users for Adobe Document Services (ADS)
ADSUSER User exists at least in SAP system clients 000 and 001.
ADS_AGENT User exists at least in SAP system clients 000 and 001.
Data supplier user for System Landscape Directory (SLD) (optional) The name that you gave this user during the installation.The recommended name is SLDDSUSER.User exists at least in SAP system clients 000 and 001.
Note
SAPinst created this user automatically if you chose Configure local SLD during the installation.
ABAP API user for System Landscape Directory (SLD)(optional)
The name that you gave this user during the installation. The recommended name is SLDAPIUSER.
User exists at least in SAP system clients 000 and 001.

DI Configuration
Choose each of the items you need: Design Time Repository Configuration, Component Build Service, Change Management Service.
Importing the Build Archives
1. Before the first check-in and import of the build archives, restart the J2EE Engine once.
2. Copy the build archives SAPJEE0x_0.SCA , SAPJTECHS0x_0.SCA and SAPBUILDT0x_0.SCA from the folder
\usr\sap\trans\EPS\in\ CMSP< hostname> into the CMS inbox folder \usr\sap\JTrans\CMS\inbox.
3. Start the CMS Web UI with user NWDI_ADM.
4. Select the Demo track in the Transport Studio.
5. Switch to the Check-In tab.
6. Click on the Value help button.
7. Select the following software components:
n sap.com SAP-JEE
n sap.com SAP_JTECHS
n sap.com SAP_BUILDT
8. Switch to the Development tab.
9. Select Select All and then Import.
10. Switch to the Consolidation tab.
11. Select Select All and then Import.

Preparing User Management for an External ABAP System
For a Java system, you can also deploy user management for an external ABAP system. In this case,
you configure the User Management Engine (UME) of the J2EE Engine for the user management of a
separate ABAP system.
Prerequisites
n The ABAP system is based on at least SAP Web AS ABAP release 6.20 SP25.
n In transaction PFCG, check that the roles SAP_BC_JSF_COMMUNICATION and SAP_BC_JSF_COMMUNICATION_RO
exist and make sure that their profiles are generated.
n In transaction PFCG, check that the roles SAP_J2EE_ADMIN, SAP_J2EE_GUEST and SAP_BC_FP_ICF exist.
Neither role contains any ABAP permissions, so you do not need to generate any profiles.
n In transaction PFCG, create a role named ADSCallers. You do not need to maintain authorization data or generate any profiles for that role.

Administration of the ABAP system
Perform the following administration steps in the ABAP system:
1. In transaction SU01 create a new communication user and assign it to the role SAP_BC_JSF_COMMUNICATION_RO.
2. In transaction SU01 create a new dialog user and assign it to role SAP_J2EE_ADMIN. This is your administrator user in the J2EE Engine.
3. In transaction SU01 create a new dialog user and assign it to role SAP_J2EE_GUEST. This is your guest user in the J2EE Engine.
4. In transaction SU01 create the following dialog users :
Users for Adobe Document Services (ADS) (optional):
l ADSUSER:
In transaction PFCG, assign the role ADSCallers to this user.
l ADS_AGENT:
In transaction PFCG, assign the role SAP_BC_FP_ICF to this user.
n SLD Data supplier user (optional):
You only have to create this user if you want to install SAP System Landscape Directory (SLD). The SLD data supplier user name that you enter later on during the Java system installation must be identical to this user.
SLD ABAP API user (optional):
You only have to create this user if you want to install SAP System Landscape Directory (SLD). The SLD ABAP API user name that you enter later on during the Java system installation must be identicalto this user.

Initial Technical Configuration for Application Server Java (AS Java)

Initial Technical Configuration for Adobe Document Services
SAPinst automatically performs initial technical configuration steps specific to Adobe Document Services (ADS) during the installation.
However, you have to perform some of these steps manually if:
n You upgraded your SAP system to NetWeaver 2004s SR1.
n You have installed AS Java on a separate host and want to use ADS for a standalone ABAP system.
n You want to change existing parameters or you want to set additional parameters.

Checking the IIOP Service
The startup mode of the service iiop must be set to always. To verify this, you have to check and if required modify special settings on the central instance host.
Procedure
1. Start the configuration tool of the J2EE engine:
Run \usr\sap\\DVEBMGS\j2ee\configtool.bat
The J2EE Engine ‒ Config Tool screen appears.
2. In the left frame, open the tree Cluster data® Global dispatcher configuration® Services.
3. Choose service iiop.
4. The field Startup mode in the right frame must be set to always.
5. Choose Apply changes.
6. Repeat the steps 2. ‒ 5. for the following path: Cluster data® Global server configuration® Services.
Checking Java Startup Properties
You have to check if the Java startup property for Adobe document services is set. To do so, you have to check and if required modify special settings on the central instance host.
Procedure
1. Start the configuration tool of the J2EE engine:
Run \usr\sap\\DVEBMGS\j2ee\configtool.bat
The J2EE Engine ‒ Config Tool screen appears.
2. Select cluster data® instance_® server_.
3. In the right frame, check if the following line exists in the section Java Parameters of the tab
General:
-Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.
services.ts.jts.ots.PortableInterceptor.JTSInitializer
If it is not true, add the line to this section.
Creating a User for Basic Authentication
To ensure secure access, you must create a user and assign the security role ADSCaller to this user
. The ADSCaller security role was created during the SAP system installation.

1. Log on to the Visual Administrator of the J2EE Engine.
a) On your central instance host, change to the admin directory:
(path: \usr\sap\\\j2ee\admin):
b) Double-click go.bat.
2. On the Cluster tab, choose Server ® Services® Security Provider.
3. On the User Management tab, choose Create Group to create a group called ADSCallers, if the group does not exist. In the dialog box that follows, enter the name and choose OK.
4. Choose Create User.
The Create New User dialog box is displayed.
5. In the User name, Password, and Confirm password boxes, enter ADSUser for the user name and enter a password.
6. Choose the Tree tab in the right panel. In the User Tree, select ADSCallers, and then choose OK.
7. Choose the Tree tab in the left panel. Select ADSCallers® ADSUser.
8. In the Authentication area, select No password change required.
9. On the Policy Configurations tab, in the Components area, select
com.adobe/AdobeDocumentServices*AdobeDocumentServicesAssembly.jar.
10. On the Security Roles tab, select ADSCaller from the Security Roles list.
11. In the Mappings area, choose Add, which is assigned to Users.
The dialog Choose Users or Groups is displayed.
12. Choose the Tree tab.
13. In the User Tree, under the ADSCallers group, select the ADSUser that you just created and choose OK.
This assigns the new user to the ADSCaller security role.
Creating a User in AS ABAP
1. Log on to the SAP system with an admin user, in the client that is used for the UME authentication.
2. Choose Tools® Administration® User Maintenance® User (transaction SU01).
3. Enter ADSUser as user name and choose Create.
4. Choose system user as type for ADSUser.
5. Choose Tools® Administration® User Maintenance® Role Administration® Roles (transaction PFCG).
6. Create a role ADSCallers (no authorizations required).
7. Activate the role.
8. Assign the user ADSUser to this role.
9. Log on to the Visual Administrator of the J2EE Engine.
a) On your central instance host, change to the admin directory:
(path: /usr/sap///j2ee/admin):
(path: \usr\sap\\\j2ee\admin):
b) Run go.sh.
c) Double-click go.bat.
10. On the Cluster tab, choose Server ® Services® Security Provider.
11. On the User Management tab, choose the Tree tab in the left panel.
12. In the User Tree, ensure that the user you created in ABAP appears under the ADSCallers group.
13. On the Policy Configurations tab, in the Components area, select
com.adobe/AdobeDocumentServices*AdobeDocumentServicesAssembly.jar.
14. On the Security Roles tab, select ADSCAller from the Security Roles list.
15. In the Mappings area, choose Add, which is assigned to Users.
The dialog Choose Users or Groups is displayed.
16. Choose the Tree tab.
17. In the User Tree, under the ADSCallers group, select the ADSUser you just created and choose OK.
This assigns the new user to the ADSCaller security role.

Creating a Service User in the ABAP Environment
You need to create the service user ADS_AGENT for processing forms between an ABAP and a Java
environment.
Procedure
1. Log on to the ABAP client specified in the profile parameter login/system_client.
2. Choose transaction SU01 (User Management).
3. Enter the name ADS_AGENT in the User field and choose User® Create.
4. Choose the Logon data tab and assign a password.
5. Choose Service as the user type for ADS_AGENT.
6. Choose the Role tab and assign the role SAP_BC_FP_ICF to the user ADS_AGENT.

Creating a Web Service Destination
Here you find information how to create a Web Service Destination.
Procedure
1. Log on to the Visual Administrator of the J2EE engine:
a) On your central instance host, change to the admin directory:
(path: \usr\sap\\\j2ee\admin):
b) Double-click go.bat.
2. On the Cluster tab, choose Server ® Services® Web Services Security.
3. Choose Web Service Clients ® sap.com > tc~wd~pdfobject ®
com.sap.tc.webdynpro.adsproxy.AdsProxy*ConfigPort_Document.
4. From the Authentication list, select BASIC.
5. In the User and Password boxes, enter as user name ADSUser and a password.
6. Choose Save.
7. Activate the authentication data as follows: Navigate to Services® Deploy.
8. Choose the button Application.
9. Choose sap.com/tc~wd~pdfobject in the tree.
10. Choose Stop Application.
11. For restarting the application, choose Start Application.

Creating a HTTP Destination
You have to create a HTTP destination to the back-end where the Adobe document services are installed.
Procedure
1. Start the Visual Administrator of the J2EE Engine.
a) On your central instance host, change to the admin directory:
(path: \usr\sap\\\j2ee\admin):
b) Double-click go.bat.
2. On the Cluster tab, choose Server ® Services® Destinations. Under Runtime, select HTTP. The available destinations are displayed. The information that applies to a selected destination is
displayed in the right pane.
3. Choose New in the navigation panel.
4. In the dialog box that follows, enter the name FP_ICF_DATA_ (where specifies the back-end where the Adobe document services are installed) for the new destination and choose OK.
5. As the target URL, enter the message server (or Web Dispatcher) of the SAP NetWeaver AS ABAP in
the URL field:
http://:
and in case of SSL:
https://:
6. Select the authentication method to use for the connection, and enter the parameters for the authentication method in the corresponding fields (if applicable).
n In the Username field, enter ADS_AGENT (must exist as service user in usage type AS ABAP).
n In the Password field, enter the same password as given for the AS ABAP service user ADS_AGENT.
7. If the connection is to use HTTPS, specify how the connection should handle SSL server authentication.
8. Save your settings.
Creating the ADS Connection in ABAP
You use this procedure to create a connection in the ABAP environment to use when connecting to Adobe document services.
Procedure
1. Log on to the central instance host.
2. Call transaction SM59.
3. Choose Create.
4. Enter at least the following:
n RFC destination: ADS
n Connection type: G
n Description:
5. Choose ENTER .
6. Choose the Technical settings tab and enter at least the following:
n Target host:
Enter the host name where you J2EE engine is located or the host name of the Windows dialog instance.
n Service No.:
l Enter the J2EE HTTP port number.
The following naming convention applies:
500 (50000 for example, if your J2EE instance is 00).
l Or enter the port number of the Windows dialog instance.
n Path prefix:
Enter exactly the string /AdobeDocumentServices/Config?style=rpc or, if you want to set up SSL,
/AdobeDocumentServicesSec/Config?style=rpc
7. Choose the Logon/Security tab and configure the security account to your security requirements.
8. Save your settings.
9. Choose Test Connection.
A screen is displayed. The field status_reason: OK indicates that the test was successful.

Activating the ICF Service FP
The communication between the Destination Service of the SAP NetWeaver AS Java and AS ABAP uses the
Internet Communication Framework (ICF). You have to activate the corresponding service.
Procedure
1. Choose transaction SICF.
2. Choose default_host® sap® bc® fp in the tree.
3. Choose Service/Virt.Host® Activate.
The ICF service is now active.

Initial Technical Configuration for Composite Application Framework Core
SAPinst automatically performs initial technical configuration steps specific to the Composite Application Framework Core (CAF) during the installation.
n However, you have to perform some of these steps manually if:
You upgraded your SAP system to NetWeaver 2004s SR1
n You want to change existing parameters or you want to set additional parameters.
The following steps might be affected:
n Create roles CAFAdmin and CAFUIAdmin
n Set configuration parameters

Configuring the Connection for System Landscape Directory
SAPinst automatically configures the connection for System Landscape Directory according to the parameters
you entered on the related SAPinst screens during the input phase.
This section provides information on how to configure your SAP system for System Landscape Directory (SLD).
You can now configure your SAP System for SLD as follows:
n As an SLD server (and client)
n As an SLD client
Initial Technical Configuration for Enterprise Portal (EP)
SAPinst automatically performs EP-specific initial technical configuration steps during the installation.
However, you might have to perform some of these steps manually if:
n You upgraded your SAP system to NetWeaver 2004s SR1.
n You have installed usage type EP as an additional usage type to an existing SAP system as described in SAP Note 883948.
The following steps might be affected:
n Copying CMS_MAPPING Properties
n Renaming InitialPermissions.xml.template
n Renaming initialPermissionsKMC.xml.template
Copying CMS_MAPPING Properties
Copy file cms_mapping.properties from source directory
\usr\sap\\JCxx\j2ee\cluster\server\apps\sap.com\irj\
servlet_jsp\irj\root\WEB-INF\portal\system\pcd\Migration\mapping\
to target directory
\usr\sap\\SYS\global\pcd\Migration\mapping\.
Renaming InitialPermissions.xml.template
1. Go to directory
\usr\sap\\JCxx\j2ee\cluster\server\apps\sap.com\irj\ .
servlet_jsp\irj\root\WEB-INF\portal\system\xml\acl
2. Rename file initialPermissions.xml.template to initialPermissions.xml.
Renaming initialPermissionsKMC.xml.template
1. Go to directory
\usr\sap\\JCxx\j2ee\cluster\server\apps\sap.com\irj\
servlet_jsp\irj\root\WEB-INF\portal\system\xml\acl
2. Rename file initialPermissionsKMC.xml.template to initialPermissionsKMC.xml.

Initial Technical Configuration for Process Integration (PI)
SAPinst automatically performs PI-specific initial technical configuration steps during the
installation.
However, you might have to perform some of these steps manually if:
n You upgraded your SAP system to NetWeaver 2004s SR1.
n You have installed usage type PI as an additional usage type to an existing SAP system as
described in SAP Note 883948.
Importing the SAP Exchange Profile
.
Note
If SAPinst has finished successfully, the exchange_profile.xml file does not exist on your system.
In this case, you can skip this step.
Procedure
1. On your PI server host, open the following URL:
http://:/exchangeProfile
The following naming convention applies for :
500
50000, for example, if your J2EE instance is 00
2. Enter the logon information:
User Name: PISUPER
Password:
The Exchange Profile page appears
3. Choose Connection.
The Server Settings page appears.
4. Enter the required information for the PI host.
Use the logon information of user PILDUSER.
5. Choose Save.
The Exchange Profile page appears.
6. Choose Import.
The Import Profile page appears.
7. Choose Browse and select the following file:
/usr/sap//SYS/global/exchange_profile.xml
8. Choose Import Data.
The profile will be imported.
Assigning SAP_ALL Rights to User PISUPER
1. Log on to your SAP NetWeaver AS ABAP host as user with SAP_ALL rights (use DDIC or SAP*).
2. Call transaction SU01.
3. Select user PISUPER.
4. Navigate to the Profiles tab and switch to edit mode.
5. In the row Profile, add SAP_ALL.
6. Save your settings.
Activating the ICF Services
The Internet Communication Framework (ICF) is a HTTP framework that provides an ABAP interface for
HTTP requests. Via ICF services, the SAP Web Application Server can use the HTTP protocol for remote
communication as client and as server.
Assigning Roles to Groups
To assign the roles to the different groups, start the Visual Administrator of the J2EE Engine.
Assigning Role "Administrator" to Group SAP_XI_ADMINISTRATOR
1. Choose Cluster® Server® Services® Security Provider®
sap.com.\com.sap.rprof.remoteprofileexchangeprofile.
2. Select Security Roles.
3. Select Administer.
4. Select the group SAP_XI_ADMINISTRATOR.
5. Choose Add and assign the role administrator.
6. Save your settings.
Assigning Security Role "LcrAdministrator" to Group SAP_SLD_ADMINISTRATOR
1. Choose Cluster® Server® Services® Security Provider.
2. On the Runtime tab in the right frame, choose Policy Configuration® Component.
3. Select sap.com/com.sap.lcr*sld.
4. On the right, choose Security Roles and select the role LcrAdministrator.
5. Select the role type Security Role.
6. In the lower frame, add group SAP_SLD_ADMINISTRATOR.
Initial Technical Configuration for Business Information Java(BI Java)
SAPinst automatically performs BI Java-specific initial technical configuration steps during the
installation.
However, you might have to perform some of these steps manually if:
n You upgraded your SAP system to NetWeaver 2004s SR1.
n You have installed usage type BI Java as an additional usage type to an existing SAP system as
described in
SAP Note 883948.
Configuring BI Java Information Broadcasting
For the configuration of the BI Information Broadcasting you need to carry out the following steps
in your
ABAP system:
1. Call transaction SPRO and carry out the following steps:
a) Settings for Information Broadcasting:
Go to SAP NetWeaver® Business Intelligence® Reporting-relevant Settings® Settings for Information
Broadcasting
b) Destinations for Web Dynpro ALV:
Go to SAP NetWeaver®Application Server®Web Dynpro for ABAP®Set-Up Printing for Web Dynpro ABAP ALV
n Create RFC destination in the SAP NetWeaver Portal
n Create RFC destination to the SAP NetWeaver Portal
n Set-Up Web Service destination for the Adobe Document Services
2. Installation of BI Content:
Call transaction RSTCO_ADMIN to check whether the installation has been carried out successfully. If
the installation status is red, restart the installation by calling transaction RSTCO_ADMIN again.
Check the installation log if you need further assistance or information.
For more information, see SAP Note 834280.
Process Chains: Transporting Texts for the Alert Category
Alerts can be triggered and sent for BI process chains that contain errors. Defining the alert
categories
is necessary for this purpose. Alert category BWAC_PROCESS_CHAIN_FRAMEWORK is returned for errors in
background processing of process chains. This category has set texts that are not transported when
the alert category is transported.
Renaming initialPermissionsBI.xml.template
If SAPinst does not rename the initialPermissionsBI.xml.template file automatically, you will need
to rename it yourself.
Procedure
1. Go to directory
\usr\sap\\JCxx\j2ee\cluster\server\apps\sap.com\irj\
servlet_jsp\irj\root\WEB-INF\portal\system\xml\acl
2. Rename file initialPermissionsBI.xml.template to initialPermissionsBI.xml.

Performing the Client Copy
If you install a new ABAP or ABAP+Java system, in most cases you do not need to perform the client
copy for
the ABAP stack. SAPinst creates three ABAP clients during the installation, client 000, client 001,
and client 066.
You can use client 001 for production.
The following procedure describes how to perform a client copy manually. We recommend that you use
client 001 as source client, however you can also use client 000 as source client.
Procedure
1. Maintain the new client with transaction SCC4.
2. Activate kernel user SAP*:
a) Set the profile parameter login/no_automatic_user_sapstar to 0.
b) Restart the application server.
3. Log on to the new client with kernel user SAP* and password PASS.
4. Copy client 000 with transaction SCCL and profile SAP_CUST.
5. Check the log files with transaction SCC3.
6. Deactivate kernel user SAP*:
a) Reset login/no_automatic_user_sapstar to 1.
b) Restart the application server.

SAP TechEd 2007 Shanghai

Oct।7
虽然我们没有IBM,HP那么大牌，资料做得好，但我们最努力，最热情。我们把拆掉的展台都带回家，把公司资料收回来带回家，把SAP的海报带回家，这种精神我们要自己佩服自己了。
SAP的讲座还是有收获的，不过内容到了中国缩水很大，而且SAP发布的技术都是内部很老的东西了。open source谈到用ant delpoy to NetWeaver ,之前在SDN问了很多人，印度佬带我绕了不少圈子，结果发现06年二月就有工具了。谈到利用open source，感觉SAP labs的兄弟过于僵化了，技术的目的是解决问题而不是歧视，他们说open source只是another option， not recommanded for SAP product。但实际上我们已经走到更前了。有讲座谈到SOA realization project，若干UIs，process， services就算比较大的项目了，那我们做的已经very large了。讲到NWDI有说DTR把代码存在database里，如何在NW崩溃后恢复代码，我倒没有研究那么深。
因为看过Sappire2007资料，新名字，新技术，新UI其实已经不算很新了，我们都做过，只是深度的问题。
Oct.6
对SAP TechEd充满了想象，终于现实化了。从何说起呢。在上海国际会议中心。
这是第一次SAP TechEd在中国开，“人空前的多”--谁叫中国人多。我们贵为golden sponsor，其实花了十几万人民币的，于是在主会场的尾端正中排起来摊子，左边是Intel做business one.只有上午keynotes围观的很多，然后分开会议室，人很少了。我们就一大堆年轻小伙发资料，收集名片，发礼物，填联系方式抽奖--除了一位直接说我只想看公司信息，其它都是奔奖品的。而我们把抽奖时间没搞明确，很有点没诚意。旁边发礼物比较实在后来吸引了不少人气。关键我们太嫩，吹不上，还好老大让我们去听讲座，很开明。“不好意思我的名片忘记带了”，这种人可能跟我一样混得不咋样。这个圈子不大，大家都希望交换联系方式的。其实参加的人大多数是软件公司的技术人员，用户方不多。我们跟HP,IBM的差距很远了。
正题，TechEd就是技术与教育大会，SAP教育partner, customer的，而且是买入场券的。基本上没有新东西，加上大部分是中文讲的。提到BW3.0(NetWeaver2004)和BI7.0(NetWeaver2004s)的区别，以前我都说过了。以后会把Visual composer，BPM做到eclipse里了。还演示discovery, SOA, interactive form，这个上半年都搞过。说道SOA中要同时用PI,BI,MDM真得不敢苟同，这个也“太奢侈”了。介绍SAP Business ByDesign,就是A1S，将按月收费，SAP提供托管服务，complete solution，其实就是整合到portal，SAAS,但网络是很不可靠的！
说到最多的是NetWeaver，但实际上我就废在那里。买书，买一送一，BW,XI，05年影印版的，挺老的。

Java 之现状

先说IDE,目前毫无争议Eclipse是主流，而其他商家都以eclipse为基础开发插件，包括SAP,IBM,JBoss,BEA,Borland,Business Object等。有一天你突然发现开发工具都变成eclipse了。--似乎Eclipse自从IBM出来就风光起来。Eclipse open source组织开发了基础的JDT(Java Development Tools),PDE(Plugins Development Environment),WTP(Web Tools Platform),GEF(Graphical Editor Framework),EMF( Eclipse Modeling Framework)等。
商业公司从开发更好的插件赚钱。从支持最新标准JavaEE5,包括JSF,JPA,EJB3，Web Service等看来eclipse并没走在前面，对于提高JEE开发效率做得还不够，第三方插件毕竟是商业的。免费的功能毕竟有限吧。而SUN支持的NetBeans，Oracle的JDev studio感觉不错。插件没那么多，插件多也麻烦，不同插件可能基于eclipse不同版本。NetBeans, JDev只要一次下载，为你提供除了JavaEE5，UML等更多支持，性能也不错．毕竟他们是最早通过JavaEE5 compatible certification的--SUN Java Application Server, Glassfish, Oracle OC4J,& SAP NWCE, later, Apache Geronimo,BEA Weblogic 10, IBM WAS.金蝶也是最早通过认证之一的．而红极一时的JBoss虽然是参与制定JPA标准的重要厂家之一,也支持EJB3,不过还没通过认证．
目前最流行大头都是IDE, Application Server, Database整合在一起，比如SUN的NetBeans+GlassFish再绑定pointbase/Derby,BEA Application Server老大很早就在weblogic server里绑定workshop IDE和DB,不过现在workshop变成eclipse版了．而database老大Oracle则绑定OC4J和免费的JDeveloper．如同microsoft的DotNet platform,SQL server, IIS, SDK,Visual Studio集成在一起．而SAP除了封闭的ABAP Workbench也推出自己的NetWeaver CE Server和IDE．但SAP并没有说要用Java取代ABAP,那样做商业意义少于成本．对于ERP通过Web Service重用．不可否认SAP新技术都是基于Java的，比如portal,XI,Web Dynpro,CAF,甚至ERP2005的安装程序也是Java的．
至于Java framework,struts,hibernate, spring,我想这些东西会让小项目变复杂，而不易于重用，重构，当JavaEE5足够流行的时候会被人们遗忘．
真正计算成本，数据库是否易于管理，MySQL虽然有免费的phpmyadmin web管理工具，还是比较复杂的．对于企业用户当然可以什么都选好的，自己买服务器，租宽带，买Oracle, Weblogic,带来的维护和管理成本也是很高的．
Derby就是一个很小的数据库，engine+JDBC Driver只有2MB,也是IBM贡献的开源软件．JDK6也把它整合进去了．
前面说到各厂商把应用服务器,IDE,DB整合在一起，就是改变以前分了web container, business logic,middle ware,Database等几个层次，让人们集中在业务开发，忘掉复杂的技术问题．
--
28,Oct.
JavaEE Running Times
Geronimo v2.02, Apache software foundation, JavaEE5 certified,不可避免以后会用得很多。管理界面很清凉，类似Weblogic,Sun Java Application Server, 但deploy几个apache开源框架竟然失败，Tomcat下运行成功的，汗。放一边凉快。
JBoss5.0是支持JEE5的，虽然尚未认证，但是比较成熟的。为什么被Redhat收购呢，一定被打压，慢慢遗忘掉。
Sun Java system app server, or Glassfish,实质是一个东西，挂两个名字，拿两个认证。安装后移到另外一个文件夹，要修改十几个配置文件，太弱智了，还算是Java吗。不过和NetBeans亲兄弟，况且Sun JavaEE tutorial都是默认用自家的东西。只是tut sample用了一大堆build.xml，这样子把问题隐藏到ant build里，恐怕不太好。
BEA Weblogic10 JavaEE5 certified,老大没得说，只是小心要收licence fee.workshop10是eclipse做的，大缩水了。万一被Oracle收购了……
Oracle OC4J,JavaEE5 certified,压缩包不到100M,其实JDeveloper, Oracle DB都绑定的有。感觉还不错。其实Oracle还算开放的，技术很标准，不像SAP，混杂个性异类。
SAP NetWeaver J2EE engine, or CE7.1,很难把它看作像其他App Server一样，不稳定，而且另类。我虽然看了所有文档但还是不明白。CE developer Studio基于eclipse3.2，终于好多了，eclipse2真得很弱，是N年前的玩意。7.1以composite application为中心，突出VC,CAF,GP,WD,JavaEE5,portlet，这一点虽然不意外，但还是很震撼，CAF基于EJB3更明显。不过能否流行还要等很久，完美的东西往往适用范围很窄。大部分基于现成的eclipse功能，配置Netweaver App server还是那么别扭。使用SAP特性提示不能deploy到其他app server上，没有SAP特性提示不能deploy到NetWeaver，为什么不像其他app server一样呢？搞什么特殊！流行的管理界面都是web的，它却是swing,只能本地管理。
尽管都是认证的，但目录和jar都不一样。
说到IDE的功能，其实都是从Java project开始，支持jsf,ejb3,jpa不过是加一些jar，build,deploy其实都是ant能力范围之内的。图形化的开发，比如jsp, javascript , jsf, struts, jpa,提供UI或向导工具，本质都是coding。
-----
这两天一两点才睡，昨晚在本本上装了SAP NetWeaver CE Server7.1,启动用了快一个小时。改进很多，只有Java Stack,还是有portal, VC,增加了WS Navigator等。色调变深，JavaScript性能似乎优化了。
SDN上问了很多人，对比起来 NetWeaver和其他JEE Server区别很大。7.0通过J2EE1.3认证，而CE7.1通过JavaEE5认证，但应该用的很少，而且不是一个完整的NetWeaver platform,SAP是要推出新版本还是说以后只有让Java独行？肯定的是SAP 通过JavaEE5认证应该花了不少功夫。说到JEE的升级不知道害了多少人，EJB的区别很大的，EJB3虽然美妙，但意味着升级。而open source的hibernate (即pojo)在servlet container里都可以跑，肯本不存在升级问题，这点白痴都知道。EJB3和hibernate很像，只不过EJB3(JPA)利用JDK5 annotation feature 把mapping 写在Javacode里。昨天用ant build axis2还行，但让产生的Web Service给Web Dynpro用，可能还有点问题。不用JavaEE5的Application Server运行JPA,JAXWS应该有问题。

Oct. 2
做了个hibernate的例子，然后用axis2实现Web Service，用Web Dynpro有点问题。

My blog here

http://sapnw70.blogspot.com
http://nw70.blogspot.com
http://nw70.spaces.live.com
http://shenpng.spaces.live.com