on 12-28-2007 9:28 AM
Dear Experts
Req:I have developed an appl in NWDS and configured in the Portal development server.
Now i want to move the appl into Production server.
Plz give me the procedure.
It's urgent
Thanks
Hazrath.G
hi,
if you want to move only one application or two...
then you can simply use the procedure i told you above.
But if u have a lot of stuff to be transported then you will have to use other means.
We also have the same scenario.
we just kept on sending applications one by one.. as development was happening.
regards,
-Amol Gupta
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
GOTO
Window->preferences->SAP J2EE Engine...
you will see the details of the J2EE engine where you are currently deploying your applications.
now u want to shift your application to Production server...
just change the J2EE Engine details to that of production server....
(Also there is a J2EE engine view which shows if the J2EE engine is configured and running properly)
IF the production server is not accesible you can simply take out the EAR file (Enterprise Archive) and deploy it onto the production server.
you can create your application anywhere...
BUT the EAR file should be deployed on the server where you want to use it.
regards,
-Ag.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Create the SCA of your cons track and deploy this SCA in the prod system.
Regards
Ayyapparaj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Hazrath,
Here's how to do it:
What is needed:
- A copy of the sapmake_util.zip file which contains files for sca, par2sda, and epa2sda executables alongside supporting libraries. This can be found in SAP note 696084.
- An installed copy of Net Weaver Developer Studio
- Access to all of the SDAs, EARs and PARs generated by the various components of your application.
1. Getting the SCA build tools installed on your machine, and making sure that your system can find them reliably.
a. First go to SAP note 696084, download the zip file, and unpack the directory called sapmake_util into the SAP parent directory of your NWDS installation.
i. NOTE: This application assumes that your NWDS is installed in the path \SAP\JDT\eclipse\... and that you are creating sapmake_util in \SAP Thus, if your path is something like \SAP\IDE\IDE70\eclipse, or you place your sapmake_util somewhere else, you will have to edit the sapmake.bat file so that it finds the NWDS libraries.
ii. NOTE: This application also assumes that you might be using old libraries. Thus, you might also have to double check to make sure the libraries that the batch file are accessing exist and update the batch-files accordingly (you might have to add 2.0.0 to several of them).
b. After this, you create an environment variable called SAPIDE_HOME that points to the directory containing sapmake_util.
i. To create a system variable in Microsoft Windows, click the link
c. In the environment variables control panel, set %SAPIDE_HOME%\sapmake_util to your Path variable, so that the command line can see all of the .bat files in sapmake_util
d. Make sure you have a JAVA_HOME system variable set to point to the directory containing your J2SE installation.
2. Collecting your Deployable objects
a. SDAs and EARs: Back end code.
i. All of the code that is generated in NWDS will create a deployable EAR or SDA file. All of these files need to be collected into one file that the SCA command can build into one SCA file.
1. For Development Components, the deployable file is usually located in [project_name]\_comp\gen\default\deploy
2. Note that CAF development components have multiple deployable objects (look in all the folders under the project, _comp, dictionary, ejbmodule, etc for deployable objects)
3. You will have to have built these DCs before their EAR and SDA files are generated.
3. Compile your deployable objects into SCAs
a. Back-end content. Here, you just need to wrap up all the data you collected into your SCA folder into an actual SCA by calling sca [content folder] [sca-name]. SCA will run an ant build and compile all the objects together
The above example takes a combination of EAR and SDA files collected in the file SCAGroup and will compile it into a file called [sca-name].sca.
Once built deploy the SCA file using JSPM or SDM. If you have GPs and other Portal Components, you'd need to build those also into the SCA before deploying.
Regards,
P.Manivannan.
Hi Hazrath,
Deployment Steps:
1. Login to SDM with a valid user name and password.
2. Go to Deployment Tab and click on Add SCA/SDA to Deployment List
3. Select the .sca files available with your Business package.
4. Click on next and start deployment.
5. Once the deployment is complete, confirm Deployment. Repeat the same process for each .sca file supplied or we can add everything in the deployment list at once and proceed with deployment.
Regards,
P.Manivannan.
Hi Hazarath,
check the following link
1.http://help.sap.com/saphelp_nw70/helpdata/en/d6/772240da03e569e10000000a155106/frameset.htm
2.http://help.sap.com/saphelp_nw70/helpdata/en/a3/782240da03e569e10000000a155106/frameset.htm
3.http://help.sap.com/saphelp_nw70/helpdata/en/50/842240852e8f5ce10000000a155106/frameset.htm
Regards,
P.Manivannan.
User | Count |
---|---|
91 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.