Administration -> Setup -> General -> Security -> Read-Only DB user

Size: px

Start display at page:

Download "Administration -> Setup -> General -> Security -> Read-Only DB user"

Bruno Fields
5 years ago
Views:

13 Administration -> Setup -> General -> Security -> Read-Only DB user

The license service is part of the SAP Business One server tools and can be installed on a central machine that can support multiple SAP Business One systems and Company Databases.

) in 2004 you could also use the IP address; no port could be specified (the port used was owned by DCOM).

18 The license service is part of the SAP Business One server tools and can be installed on a central machine that can support multiple SAP Business One systems and Company Databases. From version 2005 on, it is a CORBA service instead of COM service as of version 2004 You need to set port (default = 30000) + PC name (not IP address!) in 2004 you could also use the IP address; no port could be specified (the port used was owned by DCOM) technology solves the domain problem with the DCOM service as of 2004 When you connect to SAP Business One the system receives from the license service the modules the user is licensed. Whenever a form is clicked to be opened, it checks if the form is part of the license package the user has. One named user can access multiple systems with just one license. The license service does not need to be installed on a separate machine. It can of course also be installed on the SAP Business One database server. The partner solution (= Add-on) identifies itself via SDK The license check for partner solutions is done via SAP Business One client resp. SDK DI API Two different SAP Business One database server (e.g. test system and productive system) can use one license service. To simplify the handling of licenses it s recommended to use one central license service for the whole SAP Business One system landscape

19 Hardware Key available in the SAP Business One About screen and the Properties of the License Service

21 Regarding Historical Licenses : In the license file you will still find entries for Implementation License and Compatibility License. Compatibility License has been kept to support non-registered Add-ons technically. Implementation License may not make much sense in this context. It has been kept for backward compatibility reasons though.

27 The Add-On Identifier String needs to be assigned to the Add-On Identifier Property before calling the connect method in the APIs Connections should be re-used to avoid wasting licenses for the same user. Add-on solutions using the UI and DI API should set the Add-On Identifier only in the UI API and first connect to the UI API and then to the DI API. Another connection through the DI API would use up another license If the Add-On is assigned to the Mandatory start group, a user that has not been assigned a license for this Add-On cannot logon to the particualr company.

The Implementation Mode is meant to be used during the implementation and development of small implementation Add-Ons Allows to create and run small implementation Add-Ons in a specific customer

31 The Implementation Mode is meant to be used during the implementation and development of small implementation Add-Ons Allows to create and run small implementation Add-Ons in a specific customer environment without applying for an Add-On License Key Name. Add-Ons with implementation identifier strings run only in the environment (license server) the identifier was created in. The Development Mode is targeted to be used during the development phase of Add-On solutions (Please note: Concurrent user mode applies) A development license for the SAP Business One SDK must be available The Solution Mode will be used running Add-On solutions at the customer site This mode was created to check valid licensing for partner Add-On solutions for SAP Business One The logged on user must have been assigned a (named user) license for this Add-On. The installation of the SDK runtime version is a prerequisite for Add-ons using DI API or Java Connector, but there s no additional license check for the SDK in this license mode The Compatibility Mode is available to support old Add-Ons that have been developed before release 2004 and do not use the Add-On Identifier string Older Add-Ons still run with SAP Business One release 2004 to ensure compatibility Add-Ons that do not set the AddonIdentifier property are assumed to be old Add-Ons. several modes for different Add-ons are possible in one SAP Business One system landscape / can run with the same SAP Business One application

Process for the License Key Request: Go to http://service.sap.com/licensekey Select the Installation Number a license file should be requested for.

32 Process for the License Key Request: Go to Select the Installation Number a license file should be requested for. The respective systems for this Installation Number will be displayed To modify an existing license choose the respective System, change data and request a new license file. Go to Request New System Link to request an new license file for a new license landscape Fill in data and choose Next Step In this screen the licenses of the different SAP Business One components and Certified and Uncertified Partner Solutions can be selected and will be included in the license file. Customer specific solutions are shown in a personalized list for the partner only. If a customer runs a customer specific solution, the partner has to order the license file (with the same transaction). The partner can register his/her customer-specific solution via his/her license request form. His/Her solution is then shown in his/her personalized license request form and can be selected for a license file for the customer. Also expiration dates can be set to give partners the possibility to send out demo or test licenses for their solutions.

In your Add-On documentation make sure that beyond the documentation of any User-Defined Tables, Fields etc document each event and form in the SAP Business One application that you handle or

36 In your Add-On documentation make sure that beyond the documentation of any User-Defined Tables, Fields etc document each event and form in the SAP Business One application that you handle or manipulate. Include the following information: Expected situation (prerequisite) Action that is performed (change of data) Condition for a break in event chain (i.e. when you set parameter BubbleEvent = False) Situation that can be expected by possible successors (other Add-Ons) handling the same event

After you ve finished to develop the add-on for your customer the most important thing is to deliver and install it correctly on your clients station.

(the prerequisites are detailed available system setup documentation) All the relevant components are installed on your client station We recommend you to create an installation package with one of

37 After you ve finished to develop the add-on for your customer the most important thing is to deliver and install it correctly on your clients station. Before installing the Add-on on the customer s station make sure that: Customers station complies with the prerequisites for running SAP Business One. (the prerequisites are detailed available system setup documentation) All the relevant components are installed on your client station We recommend you to create an installation package with one of the available tools in the market (for example: Microsoft package and deployment, Installed Shield) in this way you can be sure that all the relevant components (dll, OCXs, etc ) will be packed in the package or to use the installation wizard which is included in the B1DE (SAP Business One Devlopment Environment) toolset which is available through SDN.. Do you remember (just because it happened often that partners disregarded that fact )? An Add-On can connect to UI API in two different modes: Development Mode Using the predefined connection string (don t confuse it with the Add-On Identifier!!!) within your code C C F C C006F006 D Customer Mode (Runtime mode) Connect using the connection string that comes as the commandline parameter

38 See UI API helpfile for more details Please note the EndInstall is deprecated!

40 Please note that during installation exceeding the Estimated Install Time will cause a message box to pop up. In the message box the user can confirm or deny the successful installation of the Add-On at a later time.

42 In contrast to using B1DE to implement add-ons no B1DE DLL files have to be shipped together with the installer. You can use the B1DE installer wizards without using B1DE for your add-on project!

43 Also try to install the Add-Ons you implemented in the exercises before and / or the Video Library course project you ll develop later

Setting Company Preferences The Add-On Administration tool lets you set different company-wide preferences for each company-assigned add-on.

50 Setting Company Preferences The Add-On Administration tool lets you set different company-wide preferences for each company-assigned add-on. To set these preferences, you must assign the add-on to the company (if you haven't done so already during the registration process) by moving the add-on from the Available Add-On list to the Company Assigned Add-On list using the icons. The company preferences include: See slide

53 In case an Add-On terminates the user will be informed about that fact including options to continue working or logoff from thr current company.