Interface development classification summary
1. sap interface call -- jco method
When synchronizing contracts, payments, and other information, the jco method is used to call the interface. The jco method calls need the support of the jco plug-in, which is divided into dll files under windows and so files under linux, and different plug-ins are carried out in different environments. .
2. OA interface call--webservices method
2.1 To-do interface: As long as the specified to-do is sent, it includes approval-type to-do and notification-type to-do. The approval-type to-do interface can only be called after the approval is completed, and the notification-type to-do is only used for notification. Function, you can jump to different pages according to the link address, and browse the information. Of course, if this is to be transferred to our system, we need the support of our system.
2.2 Initiating approval interface: Initiating approval, we will send the specified data to the template according to the needs of the template, and the OA will return the relevant data to our system after the approval is completed according to the relevant process flow.
2.3 Single sign-on: Single sign-on requires us to verify our identity, and we can jump to our system after the verification is passed.
2.4 Result return interface development: After the OA approval is completed, the interface provided by us is called. We design the interface development according to the business type ywlx, business serial number ywxh and other data, which can reduce future interface changes.
2.5 Processing of physical files: There are two processing schemes for physical files, scheme 1: transfer the connection address between systems, you can click the connection address to download and view; scheme 2: directly transfer the file in the form of data stream. Option 2 is not suitable for large files!
3. Scheduled task interface call--calling the webservice method of .net
3.1 Development language problem: Worry about the invocation of interfaces between languages, it turns out that it is completely possible and has no impact.
3.2 Coding problem: In the process of development and debugging, the coding inconsistency between the two systems is encountered. The solution is to convert the Chinese characters into base64 for transcoding and transmission, and then decrypt them when receiving.
4. SMS interface call--send url to call SMS
5. Mail interface call - send mail according to each mail server calling the relevant port
Can be tested by qq, 163 mailbox
jk.email_hostName=smtp.163.com
jk.email_smtpPort=25
[email protected]
jk.email.password=ceshi
[email protected]
jk.email.semailaddress=