Teach Yourself e.net - Syspro

More documents

Recommendations

Info

Licensing As well as all the normal defaults and restrictions, such as default company ID, warehouse and restricted access to inventory costs, etc., there are also e.net solutions specific defaults and restrictions on the "e.net tab" of the operator maintenance. As a named user operator is designed for only one user you can use it to specify these defaults and restrictions such as restricting which customers this operator can access. When a named user successfully logs on to e.net solutions they are allocated a 33 character UseId which is placed in the COMSTATE file along with their state information. Each time that this user uses a business object, a timestamp is updated against this UserID in the COMSTATE file. When a named user logs off of e.net solutions their UserID and matching state information is removed from the COMSTATE file. Only one user can logon to e.net solutions using this operator code at a time. If a second logon is attempted it is assumed that the previous UserID is no longer in use, and is removed from the COMSTATE file when this new entry is added (unless the following XML entry is supplied during the logon process, in which case the second user will be prevented from logging on.) Note that this functionality is only available from SYSPRO 6.0 issue 010 Y The UserID that has been removed can no longer be used. 8.1.3. Concurrency Issues The core SYSPRO product is licensed on a concurrency basis. If you have a license for 16 users, only 16 can logon to SYSPRO at any one time. It doesn't matter which operator code is using which part of SYSPRO, a total of 16 users can logon. If you want to buy an additional module you have to buy it for 16 users. If you want to upgrade from 16 to 20 users you have to do so for all modules that you have. As we have seen, the e.net solutions business objects are grouped together in licensable chunks called functional areas. As we have seen, there are two types of functional areas, 8–5
those for the raw business objects and those for using the business objects with the SYSPRO web-based applications. For the first type of functional areas (the "business object only" items) the operator can be either a "Named user" or a "Guest/anonymous user". We've already discussed named users in Section 8.1.2, “License to Named users or Specific Operator Codes” [8–2]. The idea of the Guest / anonymous users is that you do not need to have one SYSPRO operator for each person that needs the same access to e.net solutions. For example, if a SYSPRO company wishes to provide an application to their customers that allows them to remotely capture sales orders and upload them using web services, they may not want to provide a license for each one. They may have 300 customers, of which some order everyday, some only order once a month and some order infrequently. By working out how frequently their customers order, they can work out the maximum number that could logon during any 30 minute time period. They can then create an operator to process these orders and set it to be a Guest / anonymous user. Against this they set the number of concurrent users during a 30 minute time period. If a user logs on to e.net solutions using the Guest/anonymous operator code, logs off and logs back on again within 30 minutes they have used up two licenses. Therefore it is recommended that this licensing method is only used when it is appropriate, otherwise you could use more licenses than in a named user environment. When the licenses are apportioned, an operator that is set as a Named user will consume only one license. Only one instance of this operator can logon to e.net solutions at a time. If a second instance of this operator code attempts to logon they will either be prevented from doing so, or will force the first instance to be logged out (depending on an option supplied during the logon process). For the second type of functional areas (the "web-based application business object" items) the operator can be either a "Named user", a "Guest/anonymous user" (like "business object only") or part of a "Class". A class is a group of people who perform the same or similar tasks, and are licensed together in a true concurrency model. A SYSPRO operator can only be a member of one class but a class can have almost any number of members. When logging on to e.net solutions web-based applications, operators use their own SYSPRO operator code. As they are a member of a class it will use the class license, but they cannot logon using the class code. When apportioning the access to functional areas for a class, the class consumes the same number of licenses as the class allows concurrent users. It will consume the same number of licenses for all functional areas that this class is licensed to use. Specifying that this class has four concurrent users means that it will consume four of any web-based functional areas that are apportioned to it. This is different to the core product concurrency in that it is only consuming the four licenses for the functional areas that are apportioned to it and not "using up" four users. Many operator codes can have the same 8–6
Page 2 and 3:
Teach Yourself e.net solutions Firs
Page 6 and 7:
Contents Introduction .............
Page 8 and 9:
Teach Yourself e.net solutions 8.1.
Page 10:
List of Figures 2.1. e.net solution
Page 13 and 14:
xii
Page 15 and 16:
xiv 10.14. Setup.Add Method in ASP.
Page 17 and 18:
1.2. Objectives This book also assu
Page 19 and 20:
1-4
Page 21 and 22:
• A component architecture that s
Page 23 and 24:
• Product Configurator • Factor
Page 25 and 26:
Each class is a purposeful interfac
Page 27 and 28:
As SYSPRO e.net solutions is design
Page 29 and 30:
capable than OLE, and it introduced
Page 31 and 32:
(depending on the needs of a projec
Page 33 and 34:
through e.net solutions web-based a
Page 35 and 36:
that will enable a user to 'Update
Page 37 and 38:
We have oversimplified the content
Page 39 and 40:
3-6 Figure 3.2. Abstracting e.net s
Page 41 and 42:
number [0 is the company number of
Page 43 and 44:
If you configure e.net solutions to
Page 45 and 46:
5. Read the license agreement terms
Page 47 and 48:
15. Select 'Everyone' if other user
Page 49 and 50:
Box' install screen. 3. Select the
Page 51 and 52:
4-10 8. Once the install wizard has
Page 53 and 54:
you are dealing with you can click
Page 55 and 56:
4.2.2.5. Check Dataset Compliance S
Page 57 and 58:
4.2.2.12. Windows Explorer 4.2.3. S
Page 59 and 60:
Within the Communication method set
Page 61 and 62:
Within the harness section you are
Page 63 and 64:
2. Getting the Sample XmlIn Each bu
Page 65 and 66:
It is now possible to view the data
Page 67 and 68:
4-26
Page 69 and 70:
Remember that each class is an inte
Page 71 and 72:
XmlParameters pass additional param
Page 73 and 74:
Here is a similar procedure using A
Page 75 and 76:
Example 5.6. ASP.NET C# codebehind
Page 77 and 78:
5.2. Query Class There are five Met
Page 79 and 80:
Example 5.8. ASP.NET Visual Basic c
Page 81 and 82:
5.2.2. Query.Browse Syntax: Query.B
Page 83 and 84:
Example 5.11. ASP.NET Visual Basic
Page 85 and 86: Example 5.12. XmlIn with Query.Fetc
Page 87 and 88: 5.2.4. Query.NextKey Syntax: Query.
Page 89 and 90: Example 5.15. ASP.NET Visual Basic
Page 91 and 92: Now click on the Load XML button to
Page 93 and 94: 5.3. Setup Class There are three Me
Page 97 and 98: Example 5.19. ASP.NET C# codebehind
Page 99 and 100: 5.3.2. Setup.Update Syntax: Setup.U
Page 101 and 102: Response.Write("Unable to run busin
Page 105 and 106: Business objects available to this
Page 107 and 108: } catch (Exception exc) { Response.
Page 111 and 112: XML format to another: Example 6.1.
Page 113 and 114: 6.1.2.1. XSLT as a Template XSLT is
Page 115 and 116: The root node of the XML document i
Page 117 and 118: On executing the code in Example 6.
Page 119 and 120: distinguished from other elements t
Page 121 and 122: XSLT Element xsl:stylesheet xsl:tem
Page 123 and 124: We are not going to go into all the
Page 125 and 126: 6.2.5. Coding 6.2.6. Testing Once t
Page 127 and 128: 1. Build information for sales orde
Page 129 and 130: place invoice details in invoice re
Page 131 and 132: 7-6
Page 133 and 134: Purchase Order Primary Posting func
Page 135: The bottom right pane shows the sel
Page 139 and 140: mistake during the capture of the l
Page 141 and 142: 8.1.4.2. Maintaining the web-based
Page 143 and 144: characters as they cannot logon, an
Page 145 and 146: The list of operators displayed in
Page 147 and 148: 8-16
Page 149 and 150: iii.Internal to custom application
Page 151 and 152: Table 9.2. Error Handling Message F
Page 153 and 154: 9-6 Figure 9.1. e.net solutions Log
Page 155 and 156: Procedure 9.1. Configuring e.net so
Page 157 and 158: 10-2 Operator Name/Code:
Page 159 and 160: Example 10.2. ASP.NET code for usin
Page 161 and 162: Company ID: \ Company Pass
Page 163 and 164: .Append("000019") .Append("") .Appe
Page 165 and 166: 10-10 Company Password:
Page 167 and 168: 'Define the XmlIn to send to SORRSH
Page 169 and 170: "server" Text="Logon"> Please
Page 171 and 172: 10-16 SALARE:Description: T
Page 173 and 174: AddTelephone: Fax: Th
Page 175 and 176: As you can see from the sample code
Page 177 and 178: Example 10.10. Transaction.Build Me
Page 179 and 180: Example 10.12. Transaction.Post Met
Page 181 and 182: Example 10.14. Setup.Add Method in
Page 183 and 184: Example 10.16. Setup.Update Method
Page 185 and 186: Example 10.18. Setup.Delete Method
Page 187 and 188:
All the functions presented here fr
Page 189 and 190:
Example 10.22. Query.Browse Method
Page 191 and 192:
Example 10.24. Query.NextKey Method
Page 193 and 194:
Example 10.26. Query.PreviousKey Me
Page 195 and 196:
10.4.3. Calling the Method Function
Page 197 and 198:
Example 10.29. Creating the Transfo
Page 199 and 200:
Catch Exc As Exception If BubleExc
Page 201 and 202:
Example 10.32. Calling the Build Me
Page 203 and 204:
getElementById('winframe');frame.ro
Page 205 and 206:
Example 10.35. Price Query Code in
Page 207 and 208:
The SampleCode download contains t
Page 209 and 210:
Example 10.39. ASP.NET .aspx Form S
Page 211 and 212:
10-56
Page 213 and 214:
11.3. Building Your Application You
Page 215 and 216:
3. Select, Web Services. The SYSPRO
Page 217 and 218:
A-4
Page 219 and 220:
2. From the auto-run installation m
Page 221 and 222:
4. Check the e.net solutions DCOM r
Page 223 and 224:
B-6
Page 225 and 226:
Note that if the new license is for
Page 227:
C-4
show all

Teach Yourself e.net - Syspro

Create successful ePaper yourself

Delete template?

Save as template?