AVQ Zusammenfassung Homepage www.cram.com Teil 1
Karteikarten aus Seite http://www.cram.com/flashcards/export/2711515
Karteikarten aus Seite http://www.cram.com/flashcards/export/2711515
Set of flashcards Details
Flashcards | 289 |
---|---|
Language | Deutsch |
Category | Computer Science |
Level | Other |
Created / Updated | 27.03.2015 / 08.05.2016 |
Weblink |
https://card2brain.ch/box/avq_zusammenfassung_homepage_www_cram_com_teil_1
|
Embed |
<iframe src="https://card2brain.ch/box/avq_zusammenfassung_homepage_www_cram_com_teil_1/embed" width="780" height="150" scrolling="no" frameborder="0"></iframe>
|
– Low Priority:, processed by BGP: PRCQ_1 (ID: 905)): 20 PRCQs, High Priority:, processed by BGP: PRCQ_2 (ID: 906)): 14 PRCQs, STEX (parallel processing):, processed by BGP: PRCQ_3 (ID: 907)): 6 PRCQs, Bulk orders and Security events:, processed by BGP
– Priority (1 = highest / 9 = lowest), Timeslot (period of time when the corresponding PRCQ entries are processed before the linked BGP switches to the next PRCQ)., The keep period: How long work requests are being retained., The user: Each PRCQ is ass
OMDs, APIs, TOAD, Sources
– Requires technical know how and detailed knowledge of table architecture., The parameterisation specialist needs to know the table architecture of Avaloq., Consistency is not guaranteed. E.g. a source may affect 10 tables or more., There is no contro
– text in column TEXT, TEXT_GE, TEXT_FR, … (respective session language), text defined in TEXT_XX (default language), text in column NAME
Translations for specific parts
ID, USER_ID, INTL_ID, NAME, ACTIV
ADT is the external parameterisation repository of Avaloq. It also serves as backup of the parameterisation of the Avaloq Instance.
Meta data. The PL/SQL code is generated by the macros from Modules.xls (delivered by Avaloq).
Yes
Source Type Key Definition"."
Source Types Code Table Data" and "Code Table Definition""
Source Type DDIC""
The source may get overwritten by Avaloq with the next release.
A source's state is Corrupt when it compiles without an error in Avaloq but Oracle returns an error. A source's state is Error when the Avaloq compiler returns an error.
– Table Definition, Table Data
No, clients have always a source versioning system (ENV).
No, a source belongs to one component only.
No, a source version always belongs to a change.
We need to write the documentation.
We may see them in the Change View, in the Expression View, in the Orderbook…
All the granted users may modify the sources in a change.
No, we can compile it directly (remotely) on a DB.
No, we can create new versions (and modify) or close sources.
Via the Avaloq Client we cannot look for information in sources without specifying more information.
Yes, we can. This is for example what we do in the Expression View.
Business Type Config (BTC)
APIs take care of triggers and are re–runnable.
For example, by running it via an SQL client.
Business Type Config
No, we still have to compile that source on the selected Avaloq instance.
By comparing two versions for example.
That view is called the Expression View.
True
It depends on the rights that that person was assigned.
The boxes are a set of possibilities; Avaloq can implement more for the client.
False: ENV allows it and makes it easier.
Yes, it does.
So called flat files"."
The project organisation shows how a project is organized and who is responsible for what. The project plan may show the responsibilities on a task level.