cancel
Showing results for 
Search instead for 
Did you mean: 

Deploying a custom service

Former Member
0 Kudos

I am trying to create and deploy a service and I can’t seem to get it to deploy. I am using the Deploy Tool per the instructions found in the Development Manual under the ‘Deploying Libraries, Interfaces, and Services’ section. I have created the DLP project, set the properties, and made the archive. Now I am trying to deploy, but the Deploy menu item under Server Components is unavailable, as is the Properties menu item under Deployer menu in the Deployer tab. Is there something I am missing? Is there a tutorial available for creating a service? Any help would be appreciated.

Thanks!

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hello Vasil,

Thanks so much for your help. I am much closer to getting it working, but now I am getting an error on deployment and I can't figure out what the problem is. Below is the error along with my manifest files...

Mar 11, 2004 2:41:34 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Deploy Thread] INFO:

MyService.sda -> Additional log information about the deployment

Mar 11, 2004 2:41:34 PM Info: -


Starting deployment -


Mar 11, 2004 2:41:34 PM Info: Loading selected archives...

Mar 11, 2004 2:41:34 PM Info: Loading archive 'C:\usr\sap\J2E\JC00\SDM\program\temp\temp48469MyService.sda'

Mar 11, 2004 2:41:34 PM Error: com.sap.sdm.util.sduread.IllFormattedSduFileException: The information about the development component

found in the SDA C:\usr\sap\J2E\JC00\SDM\program\temp\temp48469MyService.sda is either missing or incomplete!

Manifest attributes are missing or have badly formatted value:

attribute keylocation is missing

attribute keyname is missing

attribute keyvendor is missing

attribute keycounter is missing

Mar 11, 2004 2:41:34 PM Error: Error while loading selected archives.

Mar 11, 2004 2:41:34 PM Error: -


Deployment was aborted -


-


#MANIFEST.MF

Manifest-Version: 1.0

Implementation-Version: 6.3004.00.0000.20040130180502.0000

Specification-Title: SAP J2EE Engine my test Service

Date: 200402020148

Specification-Version: 6.30

sap-perforceserver: 0000

Implementation-Title: MyService

Perforce-Server: 0000

Implementation-Vendor-Id: sap.com

Implementation-Vendor: SAP

Specification-Vendor: SAP AG

sap-changelistnumber: 70656

dc-replace:

sda-type: service

-


#SAP_MANIFEST.MF

Manifest-Version: 1.0

SDM-SDA-Comp-Version: 1

Ext-SDM-SDA-Comp-Version: 1

softwaretype: primary-service

JarSAP-Version: 20040115.1400

JarSAPProcessing-Version: 20031023.1700

changelistnumber: 70656

perforceserver: 0000

projectname: MyService

deployfile: service.xml

keyname: MyService

keyvendor: sap.com

keylocation: SAP AG

keycounter: 6.3004.00.0000.20040130180502.0000

componentelement: <componentelement name="MyService" vendor="sap.com" componenttype="DC" subsystem="NO_SUBSYS" location="SAP AG" counter="6.3004.00.0000.20040130180502.0000" scvendor="sap.com" scname="SAP-JEECOR" release="6.30" deltaversion="F" scelementtypeid="01200615320200006967"/>

JarSL-Version: 20040127.1200

compress: true

Name: MyService.jar/

AppServer-Change-List: 70656

Project-Dir: AppServer/630_SP_REL

Perfroce-Server: 0000

Checksum: 0xf2722f935ec7e03c7051a95a1466cef0

Build-on: Fri Feb 06 01:30:40 CET 2004

Name: META-INF/service.xml

content:

Name: server/properties

content:

Name: server/provider.xml

content:

Name: server/runtime.properties

content:

Name: MyServiceJar.jar

content:

Thanks again for your help.

-Angela

vasil_vasilev
Employee
Employee
0 Kudos

Hello, Angela,

You have to make it without services, because at this time development of services and interfaces is just for engine internal purposes and is not officially exposed for external customers. The problem is that development and deployment for services is forbidden in the latest versions, but in the first it was allowed so may be the documentation is not up-to-date.

If there is some progress for service development I will contact you with appropriate information.

Best regards,

Vasil

Former Member
0 Kudos

I was using 6.30, and now I am using 6.40. Still having the same problems. Matter of fact, I noticed that the documentation for deploying a service has been removed from 6.40. Are custom services supported in these early releases?

vasil_vasilev
Employee
Employee
0 Kudos

Hello Angela,

You are right for 6.30, but from version 6.40 there is no online deployment of services and interfaces as a JAR files any more. You can deploy only libraries online via Deploy Tool. Deployment of services and interfaces now is offline procedure, and for this purpose you have to create SDA archives, because offline deployment is deployment via SDM, when WEB AS is stopped.

First you must create service JAR file from Deploy Tool. In this archive you have to specify all service properties, and its JAR files. For this purpose start Deploy Tool; create new project; select ServerComponents tab; add new service; select main node to add needed JAR files; select child SERVER/DISPATCHER node to specify needed properties; save project; create archive.

For creating of SDA archive you have to add in the created from Deploy Tool JAR archive for this service new entries in the “META-INF” folder. There are 3 needed files:

META-INF/MANIFEST.MF

META-INF/SAP_MANIFEST.MF

META-INF/service.xml

Description of: META-INF/MANIFEST.MF

Manifest-Version: 1.0

Implementation-Version: 6.3004.00.0000.20040130180502.0000

Specification-Title: SAP J2EE Engine deploy Service

Date: 200402020148 /you can specify the date here/

Specification-Version: 6.30

sap-perforceserver: 0000 /you can type perforce server name if you use it/

Implementation-Title: ServiceName /you can type service name here/

Perforce-Server: 0000 /you can type perforce server name if you use it/

Implementation-Vendor-Id: sap.com

Implementation-Vendor: SAP

Specification-Vendor: SAP AG

sap-changelistnumber: 0000 /you can type change list number in perforce server if you use it/

dc-replace:

sda-type: service

Description of: META-INF/SAP_MANIFEST.MF

Manifest-Version: 1.0

SDM-SDA-Comp-Version: 1

Ext-SDM-SDA-Comp-Version: 1

softwaretype: primary-service

JarSAP-Version: 20040115.1400

JarSAPProcessing-Version: 20031023.1700

changelistnumber: 70656

perforceserver: 0000 /you can type perforce server name if you use it/

projectname: ProjectName /you can specify the project name here/

deployfile: service.xml

keyname: ServiseName /here you have to type the service name as it is in the MANIFEST.MF/

keyvendor: sap.com

keylocation: SAP AG

keycounter: 6.3004.00.0000.20040130180502.0000

componentelement: <componentelement name=" ServiceName" vendor="sap.com" componenttype="DC" subsystem="NO_SUBSYS" location="SAP AG" counter="6.3004.00.0000.20040130180502.0000" scvendor="sap.com" scname="SAP-JEECOR" release="6.30" deltaversion="F" scelementtypeid="01200615320200006967"/> /here must be careful and replace ServiceName with the name of your own service/

JarSL-Version: 20040127.1200

compress: true

/Description of included JAR file – for everyone included JAR file have to create following lines/

Name: ServiceName.jar/ /you have to type JAR name here/

AppServer-Change-List: 0000

Project-Dir: /here you can type project directory/

Perfroce-Server: 0000 /you can type perforce server name if you use it/

Checksum: /* A fingerprint is calculated from the given file by using MD5 algorithm 128 bit and the result is returned in a string variable by converting every 8 bit block to a hexadecimal 2 character representation (like 0x19f9148673414)*/

Build-on: /* Date of build in format: Mon Feb 02 01:11:38 CET 2004 */

Name: META-INF/service.xml /this one must be described as it is/

content:

/Description of other included files – for every one of the other archive entries:/

Name: /entry name for included file(with path if it is necessary to have path in the archive)/

content:

Description of: META-INF/service.xml

<?xml version="1.0" ?>

<SDA>

<SoftwareType>primary-service</SoftwareType>

<engine-deployment-descriptor version="2.0"/>

</SDA>

After creating this archive rename it to *.sda and use SDM to deploy it offline.

Good Luck!

We decided to add functionality to create SDA archives from Deploy Tool and in SP5 will be button for this function.

If there are any questions, please don’t hesitate to contact me (vasil.vasilev@sap.com).

Best regards,

Vasil

Former Member
0 Kudos

Hello Angela,

what version of Web AS are You using?

Cheers

Ivo