Setting up a track in NetWeaver 7.0 is well documented. You can find it in in Service Marketplace at the CRM installation guides. It is a different story for NetWeaver 7.3. As support for NW 7 is running out, it might be a good idea to set up new projects in a NW 7.3 environment. Therefore we will go through a setup of a track in NW 7.3 and how to connect the track to a run-time system. In this case we will just the NWDI as run-time system. This is not recommended in a live environment. But hey, it’s a sandbox to play with. This tutorial is for people with experience with SAP software and especially the WebChannel application. We will only go through the ERP part. CRM is working accordingly, you just need more SCAs. Please keep this in mind.
You need to have the following components installed:
- Web Application Server Java 7.3 (NetWeaver 7.3)
- Trex 7.1
- IIS or Apache
You must have the following additional software components downloaded from SMP:
- XECO components (newest patchlevel)
These can be found in patches: Support Packages and Patches – E -> SAP ERP -> SAP ERP ENHANCE PACKAGE EHP4 FOR SAP ERP 6.0 -> Entry by Component -> SAP XECO – design time NW7.3
- Engine components (SP/PL of your run-time system)
These can be found in patches: Support Packages and Patches – N -> SAP NETWEAVER -> SAP NETWEAVER 7.3 -> Entry by Component -> AS Java Extensions
Quick NWDI overview
Go to the Development Environment overview by visiting http://<server>:<port>/devinf. This will give you the following screen. Visit the CMS there.
Afterwards we need to make sure, that a CMS user is maintained, that has the appropriate authorizations.
If this is set up, we need to make sure, that the CIM data is mostly current. Therefore visit the SLD on the DI overview page. Then visit the following detail page which gives you the installed version.
For WebChannel in a 7.3 environment you must have at least version CR content version 7! In case this is not the case, you need to install all the delta updates as described in SAP note 669669.
Actual Track setup
We are now ready to set up the track itself. This is basically the same as in a NW 7 environment. Go to the Track Data view. Here you can setup a new track where you can add the track name, description, etc. For ERP as back-end, you only need to add the following software components (SC):
- CUSTCRMPRJ (which will hold your developments)
Make sure to have the release version 7.3 of all the SCs! In case you cannot find the 7.3 version, your CR content update failed. In case you want to use 7.32, you will even need to import the CR content up to CR version 7.1 (not NetWeaver 7.1 but CR content 7.1, this can be confusing…)
The SLD defines which dependencies we have. If you open up the SC’s in the view above, you see which other components the software relies on.
Therefore we have already downloaded the according SCA files which are mentioned in the prerequisites. You now need to check in all these files. This is straight forward and works as nothing has changed. Just go to the Transport Studio, configure the check-in folder (of course place ALL the files there), select all and check-in. Afterwards switch to the „Development“ tab right next to it, select all and import. This will take some time.
In order to configure the run-time systems we go back to the Landscape Configurator and select „Run-time Systems“ within the Track Data. When adding a run-time system we also need to know, that there is no SDM server anymore. The deployment is now done using the P4 port of the system. A wizard will come up which asks you for the host name and the message server HTTP-port.
In case you need to find out which port it is, you can use the SAP MMC.
I will not go into the TREX installation as this is pretty straight forward and has not changed. Just make sure you have enabled the HTTP communication in TREXAdminTool in order to have the IIS site created and the ISAPI plug-in installed.
What has changed: NW 7.3 does not have a Visual Administrator anymore. Therefore you need to maintain the TREX name-server in the NetWeaverAdmin Tool. Go to http://<server>:<port>/nwa. Then go to „Configuration“ / „Infrastructure“. There you will find the menu for „Java System Properties“.
Afterwards go to the „Services“ tab and search for „trex“. Below search for the extended detail „nameserver“. Here you can set a custom value. Make sure to save this!
You can now use the TREXAdminTool to set up the regular RFC connection within the back-end. This works as it used to before. I will not go into this any further.
NetWeaver Developer Studio
You can now start the Developer Studio (NWDS) and import the track configuration. Set the NWDI URL within the preferences
You should now be able to import the configuration like this:
The result should be look like this:
Make sure to have all the DC’s showing up below the two standard SCs!
Setting up the customer specific project
At first a new DC needs to be created in the CUSTCRMPRJ SC. This needs to be of the type „Enterprise Application“.
The next step is to chose a name for the DC. This can be pretty much anything you like. Keep in mind this is reserved in the SLD and can not be deleted easily. Also make sure to select the right Java version! We need to use 1.4!
Now create a project (first entry in the following context menu) of the DCs:
- SAP-SHRAPP – crm/b2b
- SAP-SHRWEB – crm/isa/web/b2b
The last one will lead to a message saying, that the project needs to be migrated. Check that the b2b project will migrated.
You can now switch to the J2EE perspective and finish setting up the customer project. Therefore we need to copy the files below META-INF from the standard application to our customer project. Select all files, use the copy function in the context menu and paste them in your customer META-INF folder.
Change the application.xml to reflect your context root. This will make sure that you have a separate name in the URL and you will not overwrite the standard application during deployment.
Currently the customer project does not have any references to any other components. This needs to be changed by adding the references to the standard application and the customer specific Java developments. First add the reference to the standard application by going to the „Development Configuration“ view and selecting your DC. In the dependencies tab you can add a new reference to crm/isa/web/b2b.
Now add a reference from crm/isa/web/b2b to crm/home/shr/ext.
A newly installed SAP J2EE engine needs to have some dictionary object to be deployed. This can be done from NWDS as well. Open SAP-CRMDIC and sync all archives. The deploy all of them. Alternatively just use JSPM to deploy the SAP-CRMDIC SCA file. If you skip this step, you will receive an error when trying to set up XCM („Initialization of Extended Configuration Management failed“).
Now create a project of crm/tc/web/core in order to get the file web-j2ee-engine.xml. This includes a role mapping between UME roles and application realms. This file get’s restructured during the project migration and needs to be fixed. If you skip this step, there will be an authentication issue when trying to access the /admin folder using the browser. Just copy the role mappings from the core DC to the b2b project’s file. Leave the headers intact! So just copy the area marked in read.
You should now be able to build and deploy your application and access it using the set up context root.
Also don’t forget to check in all the changes you have done.
As there were some questions. When getting an error while trying to access the XCM configuration there are two common error sources:
- You did not deploy all Dictionary-SCAs (see above how to handle this)
- You have installed NetWeaver 7.3 SP 00! There is a known error in the SP (ENGINEAPI.SCA to be precise). You must patch to at least SP03 to resolve the issue.
When having trouble when using RFC connections to backend classes. As of CR cntent 7.1 there is a reference missing to ENGINEAPI from SAP-SHRWEB. Just add the dependency in the track configuration. This should resolve the issue.