Migrating and Specifying Services for Web Integration
- 格式:pdf
- 大小:93.31 KB
- 文档页数:18
FortiCare Professional ServicesIntroductionAs networks and threats rapidly evolve, it’s critical to make sure security capabilitiescan keep up. Given the global cybersecurity skills shortage, today’s organizationsoften lack the in-house expertise or enough staff to deploy, operate, and maintainthe new technologies required to close security gaps. FortiCare ProfessionalServices delivers expert help to ensure Fortinet deployments are optimized for eachcustomer’s unique needs. Our experts reduce risk with:n Accelerated implementationn Operational enablement for IT teamsn Capability optimization to provide the best security Further, we can assist with ongoing operations of the Fortinet Security Fabric.SERVICE BRIEF FortiCare Professional Services is available for all Fortinet products and is customized to meet each customer’s needs.Streamlined Deployment, Capability Optimization, and Ongoing OperationsHit the Ground Running With New CapabilitiesFast-track return on investment (ROI) with streamlined expert deployment. Consultants with multivendor experience help swiftly migrate from legacy technologies and adopt new capabilities. Driven by proven methodology, FortiCare Professional Services plans and executes implementations efficiently and effectively.Achieve Performance and Configuration ExcellenceAs a business evolves, it needs to adapt protections when there are changes in users, applications, and traffic patterns.Professional Services provides regular reviews of configuration, performance, and policies, for reliability and sustained security.Extend In-house Teams With Dedicated ResourcesIn-house IT teams can focus on more critical duties while Fortinet dedicated resources handle escalation and issueresolution by working closely with Fortinet subject matter experts. Our engineers are domain experts who will get to know each business they are assigned to. Offload redundant operational tasks including configuration, upgrades, and technical incident management. Our experts work closely with in-house teams to maximize productivity by transferring technical and Operational knowledge.Extend In-house Teams With Dedicated ResourcesIn-house IT teams can focus on more critical duties while Fortinet dedicated resources handle escalation and issue resolutionProfessional Services OfferingsAll service engagements include operational enablement and knowledge transfer to ensure in-house staff is able to operate and maintain the solutions after the service is complete. Although designed to be delivered remotely, on-site options are available. Ensure Security Deployments Are Effective and EfficientOperational teams face challenges when deploying any new technology, and the complexities of today’s enterprise networks make it increasingly important to architect and configure security solutions correctly. FortiCare Professional Services gives organizations expert resources to implement and integrate security deployments quickly, while ensuring they are optimized for each unique environment. Copyright © 2022 Fortinet, Inc. All rights reserved. Fortinet, FortiGate, FortiCare and FortiGuard, and certain other marks are registered trademarks of Fortinet, Inc., and other Fortinet names herein may also be registered and/or common law trademarks of Fortinet. All other product or company names may be trademarks of their respective owners. Performance and other metrics contained herein were attained in internal lab tests under ideal conditions, and actual performance and other results may vary. Network variables, different network environments and other conditions may affect performance results. Nothing herein represents any binding commitment by Fortinet, and Fortinet disclaims all warranties, whether express or implied, except to the extent Fortinet enters a binding written contract, signed by Fortinet’s General Counsel, with a purchaser that expressly warrants that the identified product will perform according to certain expressly-identified performance metrics and, in such event, only the specific performance metrics expressly identified in such binding written contract shall be binding on Fortinet. For absolute clarity, any such warranty will be limited to performance in the same ideal conditions as in Fortinet’s internal lab tests. Fortinet disclaims in full any covenants, representations, and guarantees pursuant hereto, whether express or implied. Fortinet reserves the right to change, modify, transfer, or otherwise revise this publication without notice, and the most current version of the publication shall be applicable.April 14, 2022 3:20 PM。
GigaVUE Cloud Suite for AZURENetwork Visibility into Public CloudOrganizations are migrating to public cloud Infrastructure-as-a Service (IaaS) to take advantage of scale, elasticity and availability.IaaS cloud providers operate under a Shared Responsibility model — the cloud provider isresponsible for security of the cloud infrastructure, whereas the customer is responsible for their data, applications, access and identity management. GigaVUE Cloud Suite resides in the Azure VNets and aggregates flows from all compute sites, including from Azure virtual TAPs. This suiteprovides advanced network traffic processing and optimally distributes traffic to the appropriate network monitoring and security tools. This helps ensure effective and comprehensive cloud security.KEY FEATURES• GigaSMART intelligence – slice, sample and mask packets, header decapsulation and NetFlow/IPFIX generation • Traffic acquisition with Azure virtual TAPs or with GigaVUEvTAPs with IPsec and pre-filtering • Publish REST APIs: integrate with third-party systems to dynamically orchestrate new traffic policies • Centralized orchestration and management with a single pane of glass GUI using GigaVUE-FMKEY BENEFITS• Delivery of optimized traffic to the proper security and networking monitoring tools • 100 percent visibility into your Azure infrastructure • Reduction in applicationdowntime: there is no need to redesign applications when adding new tools • Discovery of new workloads, proper traffic direction and adjustment of the visibility tier, all without manual interventionFigure 1: Microsoft’s shared responsibilitiesmodel for different cloud servicesResponsibility Data classification & accountability On-PremIaaSPaaSSaaSClient & end-point protection Identity & access management Application level controls Network controlsPhysical securityCloud CustomerCloud ProviderHost infrastructureGIGAVUE CLOUD SUITE FOR AZURE | SOLUTION BRIEFTHE SOLUTIONGigamon CloudVUE Cloud Suite forAzure delivers intelligent networktraffic visibility for workloadsrunning in Azure and enablesincreased security, operationalefficiency and scale across VNets.Organizations can optimize costswith up to 100 percent visibility forsecurity without increasing loadon compute instances as moresecurity tools are deployed.Figure 3: Centralized management, automation and straightforwardprocess with Azure and Gigamon Fabric ManagerGigaVUE G-vTAPsFor traffic acquisition, light weight G-vTAPs are deployed within compute instances that mirror traffic to the V Series. Key benefits include:• Single, lightweight instance minimizes impact on compute nodes• Reduction in application downtime — there is no need to redesign applications when adding new tools• Agent filters traffic of interest prior to sending it via IPSecto the GigaVUE V Series to reduce application and data egress costs GigaVUE V Series NodesTraffic aggregation, intelligenceand distribution occurs withinthe GigaVUE V Series nodes,which are deployed within thevisibility tier (see figure 2). Keybenefits include:• Automatic Target Selection(ATS): Automatically extracttraffic from any workload withan agent deployed withoutexplicitly specifying VNets• Flow Mapping®: Selection ofL2-4 traffic• NetFlow/IPFIX generation:Create flow records fromnetwork traffic to determine IPsource and destination• Header Transformation: Modifyheader content (L2-L4) toensure security and segregationof sensitive information• GigaSMART intelligence: Slice,sample and mask packets tooptimize traffic sent to tools,reducing tool overload• Fully interoperable with nativeAzure virtual TAPsGigaVUE-FabricManager (FM)Centralized orchestration andmanagement are done byGigaVUE-FM. This single paneof glass creates policies forworkloads within Azure. Keybenefits include:• Detect compute node changes ina VNet and automatically adjustthe visibility tier, through pre-builtintegration with Azure APIs• Publish REST APIs: Integratewith third-party systems andtools to dynamically adjusttraffic received or to orchestratenew traffic policies• Auto-discover and visualizeend-to-end network topology,including VNet workloads byusing an intuitive drag-and-dropuser interface• Eliminate manual processesand errors by automaticallyidentifying each new workloadand their associated trafficmirroring via ATS, and thenconfiguring the trafficmirroring to direct traffic tothe V Series NodesGIGAVUE CLOUD SUITE FOR AZURE | SOLUTION BRIEF© 2019-2020 Gigamon. All rights reserved. Gigamon and the Gigamon logo are trademarks of Gigamon in the United States and/or other countries. Gigamon trademarks can be found at /legal-trademarks . All other trademarks are the trademarks of their respective owners. Gigamon reserves the right to change, modify, transfer, or otherwise revise this publication without notice.Worldwide Headquarters3300 Olcott Street, Santa Clara, CA 95054 USA +1 (408) 831-4000 | ConclusionWhether your organization is already using Azure or considering a future migration, GigaVUE Cloud Suite for Azure provides intelligent network traffic visibility for workloads running in the cloud. Integration with Azure APIs automatically deploys a visibility tier in all VNets, collects aggregated traffic and applies advanced intelligence prior to sending selected traffic to existing security tools. With GigaVUE, organizations can obtain consistent insight into their infrastructure across Azure and their on-premises environment.。
Cargo Clearance Authorization Letter[Your Name][Your Address][City, State, ZIP Code][Email Address][Phone Number][Date][Recipient's Name][Recipient's Title][Company Name][Company Address][City, State, ZIP Code]Dear [Recipient's Name],I am writing to authorize [Consignee's Name] to act as my agent for the purpose of clearing goods through customs during the importation process.I understand that this authorization grants [Consignee's Name] the authority to make all necessary declarations and payments on my behalf, in accordance with the laws and regulations of the customs authority.I confirm that [Consignee's Name] is fully authorized to represent me in all matters related to the importation of the goods, including but not limited to:1. Preparing and submitting all required customs documents, such as bill of lading, commercial invoice, packing list, and any other relevant documents.2. Paying any duties, taxes, and other charges imposed by the customs authority in connection with the importation of the goods.3. Representing me in any customs audit or investigation conducted by the customs authority in relation to the goods.4. Taking all necessary actions to ensure the timely clearance of the goods through customs and their delivery to the designated destination.I acknowledge that [Consignee's Name] is not responsible for any errors or omissions in the customs declarations made on my behalf, except to the extent that such errors or omissions are the result of [Consignee's Name]'s gross negligence or willful misconduct.I further authorize [Consignee's Name] to engage the services of any third-party agents or carriers as necessary to facilitate the importation and clearance of the goods. I understand that any additional costs incurred by [Consignee's Name] in connection with the engagement of such third-party agents or carriers will be my responsibility.I hereby represent and warrant that all information provided in connection with the importation of the goods is true, accurate, and complete to the best of my knowledge and belief. I acknowledge that any false or misleading statements may result in penalties, fines, or other legal consequences under applicable laws and regulations.This authorization shall remain in effect until the goods have been successfully cleared through customs and delivered to the designated destination. However, I reserve the right to revoke this authorization at any time by providing written notice to [Consignee's Name].I understand that this authorization is a legal and binding document, and I hereby affix my signature below as a testament to my consent and authorization.Sincerely,[Your Signature][Your Name]。
IBMTCM CommunityProfiles -Communities -WikisIBMTRIRIGA► TRIRIGA Wiki Home► Facilities Management & Space P ...Facilities Maintenance► Environmental & Energy Manage ...► Real Estate Management► Capital Project Management► CAD Integrator-Publisher and BIM► IBM TRI R IGA Connector for Wats ...► IBM TRIRIGA Anywhere► IBM TRI R IGA Application Platform► Release Notes► Media Library► Best Practices► Upgrading► Troubleshooting-UX F rameworkUXArticles► UX A pp Building• UX Perceptive Apps• UX in Foundation Tools• UX A pp Designer ToolsUX B est Practices-UX i n Foundation DocsWhat is the UX f rameworkUX i n Application BuildingUX i n Application Building -C ...UX i n Globalization User Guide• UX i n Object Migration User .. .UX i n User Experience User G .. .UX C omponent Docs► UX T ips & TricksUXVideos• UX A rchivesIndexMembersTrash... Tags Find a Tag.,analysis application availability_sectionbest_practices cad change_managementchanges compare compare_revisionscustomizations customize database db2exchange find_available_times gantt_chartgantt_scheduler group memory_footprintmodifications modify object_labelobject_revision operating_system oracleperformance platform problem_determination reports reservereserve_performance revision revisioningsingle_sign-on snapshot space sql_serversso support systemsystem_performance tags:track_ c ustomizations tri r i Q 8troubleshoot tuning upgrade ux versionversioningCloud List► Members ., -I .. This Wiki -Search Sign in Register Q. 0 Q Log in to participate You are in: IBM TRIRIGA > UX Framework > UX in Foundation Docs > UX in Object Migration User Guide UX in Object Migration User Guide §I Updated 10/8/19 by Jay.Manaloto I Tags: None Page Actions -UX F r amewo r k ux Component Doc See the UX A rticle 5 "Classic Docs & UX" PDF for previous versions of this content. What UX content affected the Object Migration User Guide? The IBM T RIRIGAAP-P-lication Platform 3 Object Migration User G uide [3.6.0 PDF] provides information about moving customized applications from one platform environment to another. Migrating objects > Object migration overview> Object types Exporting objects > Object export overview > Object migration export tips Exporting objects > Object finder search parameters Exporting objects > Specifying objects to add to the export package > Adding UX objects to an export package Importing objects > ComparingNew object types that are supported ■Application ■Object Label ■Web Component New paragraph You can select the Application or Web Component object type to search for and add applications or web components to your export package. By default, all metadata that is related to the application or web component, including dependent metadata, is automatically selected for inclusion in the package. You can use the search parameters to limit the dependent data. New tip: Dictionary Record Data Use the Globalization Manager instead of Object Migration to export and import Dictionary (triDictionaryEntry) record data. If you choose to use Object Migration, make sure to remove existing Dictionary records from the target environment before you import the package that contains your Dictionary records. The Dictionary record name is mapped from a control number. The control number sequence in the source environment might not match the sequence in the target environment; therefore, duplicate records might occur on import. New content for the Module parameter (underlined) This parameter does not display for the object types AP-P-lication, Budget Token, Document, Form Style, Group, Module, Navigation Collection, Navigation Item, Portal, Portal Section, and Web ComP-onent. New content for the Modified By (User) parameter (underlined) The supported object types for this parameter are AP-P-lication, Business Object, Document, Form, Group, Module, Navigation Collection, Navigation Item, Query, Record Data, Web ComP-onent, and Workflow. New content for the Object Label parameter Filter the search to objects that contain a specific object label. This parameter displays for the object types All, Application, Business Object, Form, Module, Report, Web Component, and Workflow. When All is selected, only Application, Business Object, Form, Module, Report, Web Component, and Workflow objects are searched, as they contain object labels. The objects that are not labeled are not searched. This parameter searches only for the objects that currently contain the object label. In Object Label Manager, the Labeled Objects tab for the object label definition contains not only objects that currently have the label but also objects that previously had the label. New topic: Adding UX objects to an export package You can select the A pplication or Web Component object type to search for and add UX applications or web components to your export package. About this task By default, when you select Search, all metadata that is related to the application or web component, including dependent metadata, is automatically selected for inclusion in the package. An Include Dependents check box is displayed when the search completes and the search results contain applications or web components. The check box is selected by default. If you want to limit the dependent data such as Queries, Business Objects, and Workflows in the package, deselect the Include Dependents check box. Then, use the search parameters to search for and add the dependent data that you want. UX dependents of applications andweb components, such as Models and Data Sources, are always included at the time you export the package.The Include Dependents check box is displayed only if your search results containapplication or web component object types. It is only with these object types that dependent data can be automatically selected for inclusion in a package. If your search contains other objects that are not associated with an application or web component, the Include Dependents check box has no bearing on those objects. For those objects, you must use the standard method of using Find Dependencies to locate and add the dependent data that you want. If you select the Application or Web Component object type and add a search term to the Object Name field and select Search, the term is cleared after the results are displayed. The term is cleared so that all dependent objects that are associated with the application or web component are selected, not only those objects whose name contains the term. If you want to go back to your search criteria, select Back.。
wZ Wordalizerin InDesign CS4 / CS5 / CS6 / CCw Z2 . System requirements• Mac OS X 10.6 or later,or Windows XP / Vista / 7 / 8 (x86 or x64 editions).• CPU with a minimum clock rate of 3 GHz.• Main memory (RAM) of at least 4GB (8GB recommended).• 1000×800 pixel screen-resolution or greater.• Adobe InDesign CS4, CS5, CS5.5, CS6, or CC.3 . TRY vs. PRO versionYou can download a free tryout version of Wordalizer at: /blog/public/scripts/WordalizerTry.zip . It offers all the features of the PRO release, but it will automati-cally add on the word ‘Wordalizer’ into the final artwork.OOTEWe strongly encourage you to install and test the TRY version before you purchase the PRO license of the product. Always make sure that your system meets the requirements.The main dialog of Wordalizer has a very similar look-and-feel in both Mac OS and Windows environments. The followinglanguages are available (depending on your InDesign locale):▶ English (default) ▶ FrenchWordalizer both supportsCC 9.x and CC 2014w Z1 ) In InDesign, open the Scripts panel as follows:• CS4: Window ▶ Automation ▶ Scripts.• CS5, CS5.5, CS6, and CC: Window ▶ Utilities ▶ Scripts.3 ) You should now see a Scripts Panel folder. Drag WordalizerPro.jsxinto there. Congratulations, Wordalizer is now installed!MAC OS XRIGHT-CLICK CLICK DRAG INTOWINDOWSRIGHT-CLICKCLICKDRAG INTOw Zw Zw Z▶ Use last Wordalizer settingsSelect this option to reload the latest items and settingsused in Wordalizer disregarding the current context.This button is useful in particular when InDesign hasjust re-started.▶ Get the word list from the current cloudThis option is available when the active documentis a word cloud previously produced by Wordalizer.You can then reload its specific word list and settingsin order to either change some parameters (Update),or to create a new cloud based on the same model(Create).Select this option to quicly create a trial list based onrandom lorem-ipsum-fashioned words. By default,100 words are generated. You can change this numberfrom the preferences panel.2 .Specifying a languageWords captured from an InDesign document, book, or from theclipboard, can be automatically filtered and/or refined througha language-aware scanner. Its main purpose is to skip irrele-vant words, e.g. in English, ‘the,’ ‘is,’ ‘that,’ ‘by,’ etc. Wordalizermanages specific stop words for each supported language.w Zpressing Enter—if the existing weight already fits your needs.OOTE If you need to discard the current language, just clickthe active flag button to turn it off. Wordalizer will thenscan the entire text without removing stop words.w Zw Zvalues are entirely redistributed basing on that order.2 ) Click one of the following buttons:▶THEME100% StonesCHARACTERS100%0CLOUDBalance entry weightsDistribute numbers as linearly as possible—as if weights had toalign on a straight line.▶ LISTTHEME100%Stones100%Boost high entry weightsGradually increase high weights.▶ THEME100% StonesCHARACTERSBoost low entry weightsGradually decrease low weights.(where ¶ denotes a new line, spaces being optional.)OOTEThe whole word list cannot have more than 10,000 characters; each word item must have at most 50 characters; each weight must be a sequence of digits.3 ) Once your list is ready, copy it in the clipboard if you have used an external text editor, then go back to InDesign.4 ) Run Wordalizer and select either the source (get the list from the clipboard). OOTE The option “Detect word list” tends to slow down Wordalizer’sstartup. We recommend you turn it off if you don’t use it.Example ofweighted word list.w Zw ZCreate Close 20%0°0.2Create Close Update 20%0°0.2Myriad Pro Create CloseUpdate 20% Myriad Pro Regular FONT 4Create Update Stones20%00°0.2100%020%0°0.2100%0CLOUD 20%0°0.2100%0CLOUD 100%20%0°0.2Lemniscate Propeller Trefoil Hourglass Explosionw ZWordalizer PRO 1.508Licensedto:***********************wZ tectam 76borios 55issim 32sinctia 24dolorisi 82alicae 79magnima 76ipsant 72ulpa71hello world50Myriad Pro RegularFONT 3Myriad Pro RegularFONT 4Close 0°0.2Losange Create Close0°0.2Close0°0.2AstroidRectangularwordcloud based on the square pattern with W/H = 40%. (Theme: Museum .)w ZVerticality: 50 % + Shake angle: 10°Verticality: 50 % + Shake angle: 45°Verticality: 100 %w Zw Z Battleship Bloody Elves 2IPuppet Show Power Brickw Zw Z Native Theme Edited Themew Zw Ztion time. Lower values lead Wordalizer to run faster, but at the cost of raw approximation in computing and positioning vector artworks. Conversely, high precision will produce more consis-tent results but in a much greater delay.Increasing the precision may be effective whether the number of words to be processed does not exceed 300, and provided that very complex typefaces are not involved.The parser is the module by which Wordalizer scans a sourcetext and retrieve relevant words.• Change the “Min. frequency” value to eliminate low-fre-quency occurrences, often due to typos and/or hapax.• Turn on “Smart case” to allow the parser to detect case variants—such as InDesign vs. Indesign vs. INDESIGN—and then to keep the best form. If “Smart case” isSee Section 8. in“Manage yourWord List.”w Zand CC 2014. In particular it adjusts to InDesign dark theme if used—as shown below. In the case you change your interface preferences during a session, restart InDesign before you re-run Wordalizer.OOTE Wordalizer, of course, remains backwards compatible withInDesign CS4, CS5, and CS6 (Mac OS X and Windows).As Adobe is constantly updating InDesign CC, you may still experience issues that we cannot anticipate despite the many tests we perform. Please, feel free to report any new bug at ***********************.5 .Migrating from Wordalizer 1.25Wordalizer 1.25 for InDesign CS4 / CS5 is not supportedanymore. Although it can still be used in old environmentswithout causing conflict with the current version, we encourageyou to discover the features of Wordalizer 1.5.Note also that word clouds built from version 1.25 are fully rec-ognized by version 1.5, so you can easily update—and improve!—existing creations.Wordalizer’s main dialogas rendered in InDesign CCwhen a dark theme ischosen via Preferences ▶Interface ▶ Appearance.wZ Wordalizer 1.5w w w.i n d i s c r i p t s.c o mA plug-in for Adobe® InDesign® based on Adobe® ExtendScript and ScriptUI. Created and developed by Marc Autret. Designed by Dominique Chiron and Marc Autret. User Interface available in English and French.My very special thanks to Jonathan Feinberg (), Theunis de Jong (), Dominique Chiron () and Jean-Christophe Courte (). I also wish to thank the people who have helped improve and promote this produc t, in no partic ular order: Klaus Nordby, David Blatner (InDesignSecrets), Stéphane Baril (Adobe France), Loïc Aigon (Ozalto), Laurent Tournier (Indigrep), Cécile Mazin (Ac tuaLitté), Alexander Charc har (Smashing Magazine), Rinniee Ginsburg (Webgranth), Ingo Wilsinger, Jan Mirus—not forgetting those graphic designers, trainers, authors, and InDesign gurus who have all contributed at some level to the success of Wordalizer: Sandee Cohen and Diane Burns (authors of “Digital Publishing with Adobe InDesign”), Pariah Burke, Erica Gamet, Haeme Ulrich, Khaled Galal, Jennifer Blatz, Phillip Southgate and so many others!Main Product Page: /category/projects/WordalizerTryout version: /blog/public/scripts/WordalizerTry.zip Technical Support: ***********************Purchasing Wordalizer: /store/WDLZEnd User License Agreement: /pages/eulaTerms and Conditions of Sale: /pages/cgvCopyright Notice: /pages/copyrightThis manual, as well as the software documented in it, is released under license and may be used or copied only in accordance with the terms of that license. The content of this document is subject to change without notice. Every effort has been made to ensure that the information in this document is accurate. However, Indiscripts assumes no responsibility or liability for any error that may appear in this document. InDesign, the InDesign logos, are trademarks of Adobe Systems Incorporated.© Indiscripts, 2010-2015.All rights reserved. Made in France.。
关于空运服务的附件1.本附件适用于影响定期或不定期空运服务贸易及附属服务的措施。
各方确认在本协定项下承担的任何具体承诺或义务不得减少或影响一成员在《WTO协定》生效之日已生效的双边或多边协定项下的义务。
2.本协定,包括其争端解决程序,不得适用于影响下列内容的措施:(a)业务权,无论以何种形式给予;或(b)与业务权的行使直接有关的服务,但本附件第3款中的规定除外。
3.本协定适用于影响下列内容的措施:(a)航空器的修理和保养服务;(b)空运服务的销售和营销;(C)计算机预订系统(CRS)服务。
4.本协定的争端解决程序只有在有关成员己承担义务或具体承诺、且双边和其他多边协定或安排中的争端解决程序已用尽的情况下方可援引。
5.服务贸易理事会应定期且至少每5年一次审议空运部门的发展情况和本附件的运用情况,以期考虑将本协定进一步适用于本部门的可能性。
6.定义:(a)“航空器的修理和保养服务”指在航空器退出服务的情况下对航空器或其一部分进行的此类活动,不包括所谓的日常维修。
(b)“空运服务的销售和营销”指有关航空承运人自由销售和推销其空运服务的机会,包括营销的所有方面,如市场调查、广告和分销。
这些活动不包括空运服务的定价,也不包括适用的条件。
(C)“计算机预订系统(CRS)服务”指由包含航空承运人的时刻表。
可获性、票价和定价规则等信息的计算机系统所提供的服务,可通过该系统进行预订或出票。
(d)“业务权”指以有偿或租用方式,往返于一成员领土或在该领土之内或之上经营和/或运载乘客、货物和邮件的定期或不定期服务的权利,包括服务的地点、经营的航线、运载的运输类型、提供的能力、收取的运费及其条件以及指定航空公司的标准,如数量、所有权和控制权等标准。
Annex on Air Transport Services back to top1. This Annex applies to measures affecting trade in air transport services, whether scheduled or non-scheduled, and ancillary services. It is confirmed that any specific commitment or obligation assumed under this Agreement shall not reduce or affect a Member’s obligations under bilateral or multilateral agreements that are in effect on the date of entry into force of the WTO Agreement.2. The Agreement, including its dispute settlement procedures, shall not apply to measures affecting:(a) traffic rights, however granted; or(b) services directly related to the exercise of traffic rights,except as provided in paragraph 3 of this Annex.3. The Agreement shall apply to measures affecting:(a) aircraft repair and maintenance services;(b) the selling and marketing of air transport services;(c) computer reservation system (CRS) services.4. The dispute settlement procedures of the Agreement may be invoked only where obligations or specific commitments have been assumed by the concerned Members and where dispute settlement procedures in bilateral and other multilateral agreements or arrangements have been exhausted.5. The Council for Trade in Services shall review periodically, and at least every five years, developments in the air transport sector and the operation of this Annex with a view to considering the possible further application of the Agreement in this sector.6. Definitions:(a) “Aircraft repair and maintenance services” mean such activities whenundertaken on an aircraft or a part thereof while it is withdrawn from service and do not include so-called line maintenance.(b) “Selling and marketing of air transport services” mean opportunities for the aircarrier concerned to sell and market freely its air transport services including allaspects of marketing such as market research, advertising and distribution. These activities do not include the pricing of air transport services nor the applicableconditions.(c) “Computer reservation system (CRS) services” mean services provided by computerised systems that contain information about air carriers’ schedules, availability, fares and fare rules, through which reservations can be made or tickets may be issued.(d) “Traffic rights” mean the right for scheduled and non-scheduled services to operate and/or to carry passengers, cargo and mail for remuneration or hire from, to, within, or over the territory of a Member, including points to be served, routes to be operated, types of traffic to be carried, capacity to be provided, tariffs to be charged and their conditions, and criteria for designation of airlines, including such criteria as number, ownership, and control.。
整理好的LC用语整理好的L/C 英语Kinds of L/C1.revocable L/C/irrevocable L/C 可撤销信用证/ 不可撤销信用证2.confirmed L/C/unconfirmed L/C 保兑信用证/ 不保兑信用证3.sight L/C/usance L/C 即期信用证/ 远期信用证4.transferable L/C(or)assignable L/C(or)transmissible L/C /untransferable L/C 可转让信用证/ 不可转让信用证5.divisible L/C/undivisible L/C 可分割信用证/ 不可分割信用证6.revolving L/C 循环信用证7.L/C with T/T reimbursement clause 带电汇条款信用证8.without recourse L/C/with recourse L/C 无追索权信用证/ 有追索权信用证9.documentary L/C/clean L/C 跟单信用证/ 光票信用证10.deferred payment L/C/anticipatory L/C 延付信用证/ 预支信用证11.back to back L/Creciprocal L/C 对背信用证/ 对开信用证12.-------------------------------------------------------------- traveller's L/C(or:circular L/C) 旅行信用证Names of Parties Concerned1.opener 开证人(1)applicant 开证人(申请开证人)(2)principal 开证人(委托开证人)(3)accountee 开证人(4)accreditor 开证人(委托开证人)(5)opener 开证人(6)for account of Messrs 付(某人)帐(7)at the request of Messrs 应(某人)请求(8)on behalf of Messrs 代表某人(9)by order of Messrs 奉(某人)之命(10)by order of and for account of Messrs 奉(某人)之命并付其帐户(11)at the request of and for account of Messrs 应(某人)得要求并付其帐户(12)in accordance with instruction received from accreditors 根据已收到得委托开证人得指示2.beneficiary 受益人(1)beneficiary 受益人(2)in favour of 以(某人)为受益人(3)in on e's favour ... 以为受益人(4)favouring yourselves 以你本人为受益人3.drawee 付款人(或称受票人,指汇票)(1)to drawn on (or :upon) 以(某人)为付款人(2)to value on 以(某人)为付款人(3)to issued on 以(某人)为付款人4.drawer 出票人5.advising bank 通知行(1)advising bank 通知行(2)the notifying bank 通知行⑶advised through …通Onk . 银行通知⑷advised by airmail/cable through 通过?……银行航空信/电通知6.opening bank 开证行(1)opening bank 开证行(2)issuing bank 开证行(3)establishing bank 开证行7.negotiation bank 议付行(1)negotiating bank 议付行(2)negotiation bank 议付行8.paying bank 付款行9.reimbursing bank 偿付行10.the confirming bank 保兑行Amount of the L/C 信用证金额1.amount RMB Y… 金额:人民币2.up to an aggregate amount o f Hongkong Dollars 累计…金额最高为港币……3.for a sum (or :sums) not exceeding a total of GBP 总金额不得超过英…镑……4.to the extent of HKD 总金额…为港币……5.for the amount of USD 金额…为美元……6.for an amount not exceeding total of JPY 金额的总数不…得超过……日元的限度- The Stipulations for the shipping Documents1.available against surrender of the following documents bearing our credit number and the full name and address of the opener 凭交出下列注名本证号码和开证人的全称及地址的单据付款2.drafts to be accompanied by the documents marked( )below 汇票须随附下歹列注有( x) 的单据3.accompanied against to documents hereinafter 随附下歹单据4.accompanied by following documents 随附下歹单据5.documents required 单据要求6.accompanied by the following documents marked( )in duplicate x随附下列注有(x)的单据一式两份7.drafts are to be accompanied by … 汇票要随附(指单据) ......- Draft(Bill of Exchange)1.the kinds of drafts 汇票种类(1)available by drafts at sight 凭即期汇票付款(3) draft(s) drawn under this credit to be marked(issu ing date of credit) 根据本证”岀得汇票须注明期)第??…号不可撤销信用证项下开立”Drawn under … Bank L/C No. …… Dated 凭…?银行……年??…月……日(按开证日(4) drafts in dupl icate at sight bearing the clauses 式两份,注明根据……银行信用证……号,日期??…?开具(5) draft(s) so drawn must be in scribed with the number and date of this L/C 上本证的号码和日期(6) draft(s) bearing the clause :“ Drawn under documentary credit No. of …Bank 汇票注明根据??…银行跟单信用证……号(如上所示)项下开立 ---Invoice1. signed commercial invoice 已签署的商业发票(in duplicate 一式两 in triplicate 一式三份 in quadruplicate 一式四份 in quintuplicate 一式五份 insextuplicate 一式六份 in septuplicate 一式七份 in octuplicate 一式八份 in nonuplicate 一式九份 in decuplicate一式十份 )2. beneficiary's original signed commercial invoices at least in 8 copies issued in the name of the buyer indicating (showing/evidencing/specifying/declaration of) the merchandise, country oforigin and any other relevant information. 以买方的名义开具、注明商品名称、原产国及其他有关资料,并经签署的受益人的商业发票正本至少一式八份3.Signed attested invoice combined with certificate of origin and value in 6 copies as reuired for imports into Nigeria. 以签署的,连同产地证明和货物价值的,输入尼日利亚的联合发票一式六份4. beneficiary must certify on the invoic e …have been sent to theaccountee受益人须在发票上证明,已将……寄交开证人5.4% discount should be deducted from total amount of the commercial invoice 商业发票的总金额须扣除 4% 折扣6.invoice must be showed: under A/P No.…date of expiry 19th Ja 发票须表明:根据第 ... 号购买证,满期日为 1981 年 1 月 19 日 7.documents in combined form are not acceptable不接受联合单据/doc/50999c4b750bf78a6529647d272 84b73f342363f.html bined invoice is not acceptable 不接受联合发票 Bill of Loading ---提单(2)draft(s) to be drawn at 30 days sight(3)sight drafs 即期汇票 (4)time drafts 远期汇票开立 30 天的期票2.drawn clauses 出票条款(注:即出具汇票的法律依据) (1)all darfts drawn under this credit must contain the clause “ Drafts drawn Under Bank of …credit No. …date 本证项下开具的汇票须注明本汇票系凭……银行……年……月……日第…号信用证下开具”的条款 (2)drafts are to be drawn in duplicate to our order bearing the clause Drawn underUnitMalayan Banking Corp.Bhd.Irrevocable Letter of Credit 份,以我行为抬头,并注明“根据马来西亚联合银行项下开立”No.…dated July 12, 1978 汇票一'式两 1978 年 7 月 12 日第……号不可撤销信用证Drawn under …L 即期汇票一…dated开具的汇票须注… (shownabove)1.full set shipping (company's) clean on board bill(s) of lading marked "Freight Prepaid" toorder of shipper endorsed to …Bangcbuytifyi全套装船(公司的)洁净已装船提单应注明运费付讫”作为以装船人指示为抬头、背书给??…?银行,通知买方2.bills of lading made out in negotiable form 作成可议付形式的提单3.clean shipped on board ocean bills of lading to order and endorsed in blank marked "FreightPrepaid" notify: importer(openers,accountee)洁净已装船的提单空白抬头并空白背书,注明“运费付讫”,通知进口人(开证人)4.full set of clean "on board" bills of lading/cargo receipt made out to our order/to order and endorsed in blank notify buyers M/S … Co. calling for shipment fr om China to Hamburg marked"Freight prepaid" / "Freight Payable at Destination" 全套洁净“已装船”提单/货运收据作成以我(行)为抬头/空白抬头,空白背书,通知买方??…?公司,要求货物字中国运往汉堡,注明运费付讫”/运费在目的港付”5.bills of lading issued in the 提单以……为抬…头6.bills of lading must be dated not before the date of this credit and not later than Aug. 15,1977 提单日期不得早于本证的日期,也不得迟于1977 年8 月15日7.bill of lading marked notify: buyer, not acceptable 提单注明通知买方,“ Freight Prepaid ”“ Liner terms ”“ received forship“运费预付”按“班轮条件”,“备运提单”不接受- Certificate of Origin1.certificate of origin of China showing 中国产地证明书stating 证明evidencing 列明specifying 说明indicating 表明declaration of 声明2.certificate of Chinese origin 中国产地证明书3.Certificate of origi n shipme nt of goods of …产地gS ,prOh 允许e装运的产品4.declaration of origin 产地证明书(产地生明)5.certificate of origin separated 单独出具的产地证6.certificate of origin "form A" 格式A"产地证明书7.genetalised system of preferenee certificate of origin form "A" 普惠制格式“ A”地证明书- Packing List and Weight List1.packing list deatiling the complete inner packing specification and contents of each package 载明每件货物之内部包装的规格和内容的装箱单2.packing list detailing 详注……的装箱单3.packing list showing in detail 注明……细…节的装箱单4.weight list 重量单5.weight notes 磅码单(重量单)6.detailed weight list 明细重量单7.weight and measurement list 重量和尺码单- Inspection Certificate1.certificate of weight 重量证明书2.certificate of inspection certifying quality & quantity in triplicate issuedby C.I.B.C.品检验局出具的品质和数量检验证明书一式三份3.phytosanitary certificate 植物检疫证明书由中国商4.plant quarantine certificate 植物检疫证明书5.fumigation certificate 熏蒸证明书6.certificate stating that the goods are free from live weevil 无活虫证明书(熏蒸除虫证明书)7.sanitary certificate 卫生证书8.health certificate 卫生(健康)证书9.analysis certificate 分析(化验)证书10.tank inspection certificate 油仓检验证明书11.record of ullage and oil temperature 空距及油温记录单12.certificate of aflatoxin negative 黄曲霉素检验证书13.non-aflatoxin certificate 无黄曲霉素证明书14.survey report on weight issued by C.I.B.C. 中国商品检验局签发之重量检验证明书15.inspection certificate 检验证书16.inspection and testing certificate issued by C.I.B.C. 中国商品检验局签发之检验证明书- Other Documents1.full tet of forwarding agents' cargo receipt 全套运输行所出具之货物承运收据2.air way bill for goods con dig ned to …quot ing our crd以tnuimber货人,注明本证号码的空运货单3.parcel post receipt 邮包收据4.Parcel post receipt show in g parcels addressed to …a/c accofin包收据注明收件人:通过……转交开证人5.parcel post receipt evide ncing goods con dig ned to ?…and quoti ng our ictedlitinUmber收货人并注明本证号码的邮包收据6.certificate customs invoice on form 59A combined certificate of value and origin fordeveloping countries 适用于发展中国家的包括价值和产地证明书的格式59A 海关发票证明书7.pure foods certificate 纯食品证书/doc/50999c4b750bf78a6529647d272 84b73f342363f.html bined certificate of value and Chinese origin 价值和中国产地联合证明书9.a declaration in terms of FORM 5 of New Zealand forest produce import and export and regultions 1966 or a declaration FORM the exporter to the effect that no timber has been used in the packing of the goods, either declaration may be included on certified customs invoice 依照1966 年新西兰林木产品进出口法格式5条款的声明或出口人关于货物非用木器包装的实绩声明,该声明也可以在海关发票中作出证明10.Canadian custtoms invoice(revised form)all signed in ink showing fair market value in currency of country of export 用出口国货币标明本国市场售价,并进行笔签的加拿大海关发票(修订格式)11.Canadian import declaration form 111 fully signed and completed 完整签署和填写的格式111 加拿大进口声明书- The Stipulation for Shipping Terms1.loading port and destinaltion 装运港与目的港⑴despatch/shipment from Chinese port to 从中国港口发送/装运往.....(2)evidencing shipment from Chi na to …CFR by steamer in transit Saudi Arabia not later than15th July, 1987 of the goods specified below 列明下面的货物按成本加运费价格用轮船不得迟于1987年7月15日从中国通过沙特阿拉伯装运到……2.date of shipment 装船期(1)bills of lading must be dated not later than August 15, 1987 提单日期不得迟于1987 年8 月15 日(2)shipment must be effected not later than(or on)July 30,1987 货物不得迟于(或于) 1987 年7 月30 日装运(3)shipme nt latest date .................. 最迟装运日期:(4)evidencin g shipment/despatch on or before 歹列明货物在…年…月…日或在该日以前装运/发送(5)from China port to … not later t han 31st August, 19不87迟于1987 年8月31 日从中国港口至……3.partial shipments and transhipment 分运与转运(1)partial shipments are (not) permitted (不)允许分运(2)partial shipments (are) allowed (prohibited) 准许(不准)分运(3)without transhipment 不允许转运(4)transhipment at Hongkong allowed 允许在香港转船(5)partial shipments are permissible, transhipment is allowed except at 允许分运,除在……外允许转运(6)partial/prorate shipments are perimtted 允许分运/按比例装运(7)transhipment are permitted at any port against, through B/lading 凭联运提单允许在任何港口转运--- D ate & Address of Expiry1.valid in …for negotiation until在....... 议付至?止2.draft(s) must be presented to the negotiating(or drawee)bank not later than 汇票不得迟于……交议付行(受票行)3.expir y date for presention of documents 交单满期日…4.draft(s) must be negotiated not later than 汇票要不迟于……议付5.this L/C is valid for negotiation in China (or your port) until 15th, July 1977 本证于1977 年7月15 日止在中国议付有效6.bills of exchange must be negotiated within 15 days from the date of bills of lading but notlater than August 8, 1977 汇票须在提单日起15天内议付,但不得迟于1977年8月8日7.this credit remains valid in China until 23rd May, 1977(inclusive) 本证到1977 年5 月23 日为止,包括当日在内在中国有效8.expiry date August 15, 1977 in country of beneficiary for negotiation 于1977年8月15日在受益人国家议付期满9.draft(s) drawn under this credit must be presented for negoatation in China on or before 30th August, 1977 根据本证项下开具的汇票须在1977 年8月30 日或该日前在中国交单议付10.this credit shall cease to be available for negotiation of beneficairy's drafts after 15th August,1977 本证将在1977 年8 月15 日以后停止议付受益人之汇票11.expiry date 15th August, 1977 in the country of the beneficiary unless otherwise 除非另有规定,(本证)于1977 年8 月15 日受益人国家满期12.draft(s) drawn under this credit must be negotiation in China on or before August 12, 1977after which date this credit expires 凭本证项下开具的汇票要在1977 年8 月12 日或该日以前在中国议付,该日以后本证失效13.expiry (expir ing) date 满期日14.…if negotiation on or before 在. 日或该日以前议付15.negoation must be on or before the 15th day of shipment16.this credit shall remain in force until 15th August 197 in China 止在中国有效自装船日起15 天或之前议付本证到1977 年8 月15 日为17.the credit is available for negotiation or paymentabroad until 期到……为止本证在国外议付或付款的日…18.documents to be presented to negotiation bank within 15 days after shipment 单据需在装船后15 天内交给议付行19.documents must be presented for negotiation within lading/after the date of issuance of forwarding agents' … days after the on board date of bill of 单据需在已装船提单/运输行签发之货物承运收据日期后……天内提示议付- The Guarantee of the Opening Bank1.we hereby engage with you that all drafts drawn under and in compliance with the terms of this creditwill be duly honored 我行保证及时对所有根据本信用证开具、并与其条款相符的汇票兑付2.we undertake that drafts drawn and presented in conformity with the terms of this credit will be duly honoured 开具并交出的汇票,如与本证的条款相符,我行保证依时付款3.we hereby engage with the drawers, endorsers and bona-fide holders of draft(s) drawn under and in compliance with the terms of the credit that such draft(s) shall be duly honoured on due presentation and delivery of documents as specified (if drawn and negotiated with in the validity date of this credit) 凡根据本证开具与本证条款相符的汇票,并能按时提示和交出本证规定的单据,我行保证对出票人、背书人和善意持有人承担付款责任(须在本证有效期内开具汇票并议付)4.provided such drafts are drawn and presented in accordance with the terms of this credit, we hereby engage with the drawers, endorsors and bona-fide holders that the said drafts shall be duly honoured on presentation 凡根据本证的条款开具并提示汇票,我们担保对其出票人、背书人和善意持有人在交单时承兑付款5.we hereby undertake to honour all drafts drawn in accordance with the terms of this credit 所有按照本条款开具的汇票,我行保证兑付- In Reimbursement1.instruction to the negotiation bank 议付行注意事项(1)the amount and date of negotiation of each draft must be endorsed on reverse hereof by the negotiation bank 每份汇票的议付金额和日期必须由议付行在本证背面签注(2)this copy of credit is for your own file, please deliver the attached original to the beneficaries 本证副本供你行存档,请将随附之正本递交给受益人(3)without you confirmation thereon (本证)无需你行保兑(4)documents must be sent by consecutive airmails 单据须分别由连续航次邮寄(注:即不要将两套或数套单据同一航次寄出)(5)all original documents are to be forwarded to us by airmail and duplicate documents by sea-mail 全部单据的正本须用航邮,副本用平邮寄交我行(6)please despatch the first set of documents including three copies of commercial invoices direct to us by registered airmail and the second set by following airmail 请将包括3 份商业发票在内的第一套单据用挂号航邮经寄我行,第二套单据在下一次航邮寄出(7)original documents must be snet by Registered airmail, and duplicate by subsequent airmail 单据的正本须用挂号航邮寄送,副本在下一班航邮寄送(8)documents must by sent by successive (or succeeding) airmails 单据要由连续航邮寄送(9)all documents made out in English must be sent to out bank in one lot 用英文缮制的所有单据须一次寄交我行2.method of reimbursement 索偿办法(1)in reimbursement, we shall authorize your Beijing Bank of China Head Office to debit our Head Office RMB Yuan account with them, upon receipt of relative documents 偿付办法,我行收到有关单据后,将授权你北京总行借记我总行在该行开立的人民币帐户(2)in reimbursement draw your own sight drafts in sterling on …Bank and forward them to ourLondon Office, accompanied by your certificate that all terms of this letter of credit have beencomplied with 偿付办法,由你行开岀英镑即期汇票向??…?银行支取。
Full Material Declarations: Removing Barriers to Environmental Data ReportingRoger L. FranzTE ConnectivityMiddletown, PA USAAbstractSince the European Directives, RoHS (Restriction of Hazardous Substances) and REACH (Registration, Evaluation, Authorization and Restriction of Chemicals), entered into force in 2006-7, the number of regulated substances continues to grow. REACH adds new substances roughly twice a year, and more substances will be added to RoHS in 2019. While these open-ended regulations represent an ongoing burden for supply chain reporting, some ability to remain ahead of new substance restrictions can be achieved through full material declarations (FMD) specifically the IPC-1752A Class D Standard (the “Standard”), which was developed by the IPC - Association Connecting Electronic Industries. What is important to the supply chain is access to user-friendly, easily accessible or free, fully supported tools that allow suppliers to create and modify XML (Extensible Markup Language) files as specified in the Standard. Some tools will provide enhancements that validate required data entry and provide real-time interactive messages to facilitate the resolution of errors. In addition, validation and auto-population of substance CAS (Chemical Abstract Service) numbers, and Class D weight rollup validation ensure greater success in the acceptance of the declarations in customer systems that automate data gathering and reporting.A good tool should support importing existing IPC-1752A files for editing; this capability reduces the effort to update older declarations and greatly benefits suppliers of a family of products with similar composition. One of the problems with FMDs is the use of “wildcard” non-CAS numbers based on a declarable substance list (DSL). While the substances in different company’s lists tend to have some overlap, no two DSL’s are the same. We provide an understanding of the commonality and differences between representative DSLs, and the ability to configure how much of a non-DSL substance percent is allowed. Case studies are discussed to show how supplier compliance data, can be automatically loaded into the customer’s enterprise compliance system. Finally, we briefly discuss future enhancements and other developments like Once an Article, Always an Article (O5A) that will continue to require IPC standards and supporting tools to evolve.IntroductionFull material declaration of product content in electronics and other industries continues to be a challenge for both suppliers and customers alike. For suppliers, managing substance-level data for all the materials in products is not usually a part of normal business operations, but rather, is an added burden and therefore cost to doing business. Customers, from mid-supply chain enterprises to OEM’s, must have processes and systems to request, manage, and utilize the data to ensure compliance with worldwide substance regulations. These issues call out for easy to use software solution to aid reporting.The IPC-1752A Materials Declaration Management Standard (/1752) which is aligned with IPC-1751A Generic Requirements for Declaration Process Management (/1751) is widely used for environmental reporting today. The standard specifies an XML (Extensible Markup Language) schema for mandatory and required data, including support for Class D FMD’s for homogenous materials and substances required by the RoHS Directive (the full citation for the current “RoHS Recast” legislation is “Directive 2011/65/EU of the European Parliament and of the Council of 8 June 2011 on the restriction of the use of certain hazardous substances in electrical and electronic equipment.”)In this paper, we focus on requirements for tools that enable rapid and accurate reporting of Class D FMD’s that can be used by suppliers primarily in the base of the supply chain, e.g. raw materials and smaller components. We also provide examples of how this data can be used by the supplier’s immediate customer to build more complex FMD data for product-level assemblies.Why Take the Road to FMD?One of the advantages of the FMD approach is that it is the only way a company can stay ahead of the ongoing addition of regulated substances. RoHS has been relatively static in this regard -- with only changes being to allowable Exemptions and additional documentation requirements. Otherwise, the basic 6 restricted substance have stayed the same from its initial entry into force through its “Recast”in 2011. The next addition of four additional substances, per the European Commissions Delegated Directive 2015/863/EU, will enter into force July 22, 2019. However, customers across the supply chain are already asking for data and compliance conclusions for these substances. This pre-enactment customer driven activity clearly demonstrates just how valuable FMD’s can be since suppliers with FMD data can already satisfy their customer’s requests about the presence of newly (and yet-to-be) restricted substances.Since RoHS exemptions have set expiration dates, it is also prudent to know what exempted substance is present, besides just knowing you are Compliant with Exemption but not exactly why. Since exemptions are substance-specific, this level of information is very useful as a warning that a noncompliance could develop when a product that was once acceptable to ship is no longer compliant because the exemption has expired! FMD data provides the ability to look ahead in time for exemptions that are set to expire, allowing the company to take early action through product redesign or finding alternate suppliers.REACH (Registration, Evaluation, Authorization and Restriction of Chemicals), promulgated by a separate agency, ECHA, (European Chemicals Agency), is much more dynamic and adds new Substances of Very High Concern (SVHC) to the Candidate list roughly twice a year ever since 2008. Figure 1 shows the number of substances added to REACH since its beginning in Oct., 2008 through the last date as of this writing. Shorter gray bars count the substances added each date, with the larger black bars indicating the cumulative total of substances.Figure 1 – Number of REACH SVHCs from 2008-PresentNote that there is some double counting in the Figure 1 data, since a few of the substances were listed a second time due to different toxicological reasons. Also, note that the count is based on just the primary list of SVHC posted by ECHA in its main table (https://echa.europa.eu/candidate-list-table) but the actual individual substance count by CAS number is even greater if one consults the ECHA supporting documentation. Further, it is noted that Amendment 3 of IPC-1752A, which is not fully published as of the time of this writing, will contain a non-exhaustive list of substances and their CAS numbers as a convenient reference to this ever-growing list of substances.Useful information about the Standard and its implementation and advantages may be found on the IPC web page “Data Exchange Standards” (/ContentPage.aspx?pageid=Materials-Declaration). Additional advantages of FMD have been published, for example, by companies offering such services, companies nee ding FMD’s from their suppliers, industry conferences, and articles in electronics journals (1, 2).The story continues and the message remains clear: companies need a way to stay ahead of the growing list of new substances they are required to manage. FMD’s are the best way to do so.Requirements Part One – The Schema is the RoadbedIn the next sections, we list and explain the value of functional requirements that a good, basic FMD reporting tool should have. At the most basic level, the tool by its nature will be software, and to be used for reporting up the supply chain the XML declaration file must conform to the IPC Standard itself. In recent years, the chairs and participants in the IPC 2-18b Materials Declaration Task Group have graciously offered their time and expertise to help review, on a blind submission basis, XML files including Class D FMD’s. Using software tools that are available for checking conformance to the schema as specified in the Standard, as well as a review by IPC 2-18b participants, those software solution providers that have beenverified in this review process and found to conform to the schema in their test files are listed by IPC (also at /ContentPage.aspx?pageid=Materials-Declaration.)As the relatively recent history of the IPC review process shows in Table 1, a handful of solution providers have supported and continue to support Class D FMD’s, as well as the other reporting classes A and C (not shown). It may be concluded that there are enough competent software solution providers to offer a choice, yet not be overwhelming for companies just embarking on the journey to generate FMD’s. Specific company names can be found on the IPC web site as cited above.Some of the basic requirements for conformance to the standard schema include the following:•All mandatory data elements (tags) are present, which must be completed when entering data into the tool, if not already present from some prior data entry or load. These elements include data like supplier and customer ID’s and part numbers, and homogenous materials in the product broken down by substances and their weights.•Ability to enter the most useful optional data elements as desired, or as requested by the customer. For example, substance weight is mandatory, but concentration is optional.•Ability to incorporate a legal statement, either with a standard boilerplate or by entering a custom statement.•Tags identifying the data as Class D (FMD) based on substance reporting at the homogeneous material level; class C substance category reporting at the product level; or Class A Query/Reply format (true/false compliance statements).•Further details including a complete list of Mandatory and Optional data may be found in the IPC-1752A standard. Requirements Part Two – Lanes of Chemical DataSince FMD is all about the chemical data, and suppliers in the electronics industry may not have extensive chemical expertise, this set of functionality is critical to generating Class D XMLs as correct and error-free as possible. Clearly, to even begin generating FMDs requires having the product’s chemical composition data, and unfortunately there is no magic to manage this complexity other than a materials and substances database or spreadsheets to manage the list of ingredients to be reported. Some of the major CAD systems are offering functionality to select raw materials from a database coupled to the CAD system, which is logical since the designer is specifying the materials in the first place. More about how to develop basic “what’s in the product” documentation may be a good topic for another report, since by some accounts this is still the greatest obstacle to begin any FMD.Next, we briefly highlight important functional requirements for any tool used to generate FMDs from materials and substance data.Ability to select substances from a list by CAS number prevents errors, since CAS number is a key for many receiving systems and is the Authority tag specified in the IPC standard. A CAS number lookup list should be provided in the tool, which has the advantage of speeding up data entry and selecting matches quickly from valid selections provided by the tool. The tool may also validate the format of the CAS number format itself, which must be 10 digits separated into 3 groups by hyphens, with the last digit being a check digit. These rules are published by CAS (https:///content/chemical-substances/checkdig). This type of validation may be useful to allow newer, valid CAS numbers that are not in the lookup table to still be entered. The problem of “wildcard” or declarable/reportable substance lists will be covered in the next section, since it remains a problem in the industry.A lookup of substance names can also expedite entering substances data, again by ensuring that a valid substance name is used and a valid CAS number goes along with it. The advantage is that a substance name may be more easily recognized and used by a human than a CAS number. This approach to validation has the disadvantage that compounds and even pure elements may have many different synonyms, in which case the direct CAS number lookup would be more useful.The input screen for materials and substances data may look something like Figure 2. This kind of table is the heart of a FMD, where each Material is composed of its constituent Substances, all with reported weights in the product. Optionally, data like attachment files and concentration ranges may be accommodated. If Exemptions apply at the Material level, they may also be selected.Figure 2. Example of Material and Substance Input Screen (3)Direct entry into a reporting tool is likely to be of interest to suppliers making raw materials or simple components, rather than OEM’s. But this data becomes the basis of creating FMD’s for more complex products. S uppliers of the following kinds of items might be in the best position to take advantage of the kinds of tools being discussed here.o Solder and solder flux (separately or in paste or wire)o Bulk material like sheets, or parts made of a homogenous materialo Metal alloys, or parts made from themo Wireo Mold compound; molded partso Underfillo Conformal coatingo Plating, painted or dipped coating, or other types of coatingo Adhesives, lubricants or sealantsFMD’s for these items can allow the next tier customer to use it for reporting at the next assembly level. Companies on the more complex end of the supply chain may need to use larger enterprise systems to collect this data and run final reports, so the more basic FMD generating tools may be of less interest to them. Figure 3 shows how the data cascade works. As originally envisioned with the first release of IPC-1752 in 2006, the data cascade is still deserving of more widespread understanding and more thorough implementation today. We realize the complexity of electronic products, since even small personal use devices may contain hundreds to thousands of components, the key point here is that having good tools at the very beginning stage can be useful as the data builds in complexity up to reports for more complex products.Figure 3. Cascade of FMD DataRequirements Part Three – The Wildcard DetourBy necessity, companies and standards organizations themselves have used Reportable or Declarable Substances Lists (DSL) for years. One of the early lists was the Joint Industry Guide (JIG) which went through several updates. Amendment 3 to IPC-1752A includes the following statement: The IEC 62474 database of restricted and declarable substances replaced the Joint Industry Guide (JIG) in January 2014.Meanwhile, most companies have created their own DSLs so that they will receive:o Data on those substances currently with regulatory restrictionso Data on industry-specific substanceso Data on other substances the company’s customers expect to know abouto Substances that are not yet under any regulatory restrictions, but could be at some future date.This latter case is exactly the REACH situation shown at the beginning of this paper. While there are some ways to get advanced information about the next substances to be added to REACH, these are not usually foolproof. Therefore, companies tend to cast a rather wide net to ensure future substanc es are being included in their suppliers’ declarations.The IEC62474 database (http://std.iec.ch/iec62474) as of this writing was most recently revised on Sept. 3, 2017, and contains 137 Declarable substances and 482 Reference substances. Many companies have nonetheless found it necessary, for the reasons listed above, to develop more comprehensive lists of their own. Without mentioning specific company DLS’s here, a general review of some of the many that are used in the electronics industry shows two basic trends: o Substances listed in common as a core set of substances, including those in common with the IEC62474 listo Substances that are less frequently found and not part of a common core listSince homogeneous material reporting is at the substance level, with authority being the CAS number, this presents a data handling/segregation dilemma.In a good reporting tool, then, some accommodation must be made for accepting these “wildcard” substances which inherently have no CAS number. We have seen a commonly but not universally accepted limit of 10% per homogenous material can be checked in the tool to ensure this limit is not exceeded. A good tool should also allow for a choice of a customer-specific wildcard substance name, which is not subject to checking from a CAS number list or a CAS format validation routine. Based on our review, if proper warnings are provided, this appears to be the best way at present to handle such data.Requirements Part Four – Fewer Barriers, More Open RoadSo far, we have presented desirable features to help generate FMD’s. The real power, though, is only realized through ability to revise, reuse, and build on data once it has been initially entered into a tool.First of these capabilities is ability to quickly edit the substances in a material. For companies making a family of items with related composition, changing just a few entries, or modifying the percentages of them, can be done in seconds and saved under a different product name and XML file, with version tracking as desired in the file name. This should be allowed during an existing session, or combined with the next feature.Once a complete XML FMD is generated, productivity is enhanced if that file can be easily imported again at a later date and edited as required. This portability and flexibility of data allows a supplier further down the supply chain to utilize a growing library of common materials and their formulations, and to quickly create new ones without having to repeat some or even most of the data entry. In most cases, the company’s own information, like company ID, contact and authorizer, will be repeated over many declarations. If contact and authorizer are the same person, they could be copied directly with a choice in the tool.While we are focusing here on the Class D FMD, ability to generate Class A or Class D declarations at the same time may be useful. These should be selected, or de-selected as desired, or as required by the customer. Class A query/response answers should be straightforward, as should selection of exemptions from a list. Similarly, the substance data in the Class D data section should be quickly erased to enter fresh data while retaining the rest of the information already entered.Interactive helps should provide guidance to first time and infrequent users. Checks along the way improve speed and accuracy without having to consult a user’s manual, which incidentally should also be easily accessible for those who wish to read the instructions first. Finally, the tool should prevent hang-ups and errors. Support services should be provided, and a process to investigate and resolve bugs, or perceived bugs, should be easy to submit and provide timely responses.At the end of data entry there should be a final validation of the XML, included mandatory information has been entered and the weights of substances add up to each homogenous material being reported. These checks help ensure that the XML will successfully load to the customer’s system.Conclusions - To the SuperhighwayAccording to some observers, FMD still has too many barriers to really catch on. We disagree. Supply chain reporting has to begin somewhere, by providing data to middle supply chain companies, and so forth up to chain to the OEM. FMD is the only reporting approach that helps to minimize the ongoing burden of keeping up with the ever-growing lists of regulated substances and expiring exemptions.We have mentioned that the IEC 62474 database is now invoked as the reportable substance list in IPC-1752A Amendment 3. In addition, development of an IEC 62474 international standard for reporting is in process, which will also specify anXML format. Work is underway to harmonize the schema of both IPC and IEC standards via communication and common participants in both IPC and IEC standards development, but differences should still be expected. Development of the IEC reporting standard nevertheless underscores the interest and need for FMD realization in XML format.Further enhancements can also be realized in the future; to name a few:•Integration with manufacturing data for mixed, compounded or formulated materials•Availability of integrated materials selection with design tools for more complex products•True Business-to-Business methods to request data as well as provide data all in standard machine-readable formats •Enhanced error checking, validation of common-sense rules, and agreement between, for example, a Class A declaration that says RoHS Compliant = True, yet the Class D file for the same item reports a RoHS substance over the threshold percent.•Support for updated guidance from ECHA on Once an Article, Always and Article, which changes substance percent reporting from any top-level assembly to the lowest level Article exceeding the 0.1% SVHC threshold. It is becoming clear that this will require a new data attribute to flag Articles, as distinct from unshaped Materials or Complex Objects. It is our understanding that this will be considered in the development of a revised IPC-1752B Standard.In addition to the motivation of staying ahead of the growing number of regulated substances, a business processes and procedures that support FMD can also be useful. The expectation that FMDs must be provided can be a requirement for gaining new business or for qualification of an item as a prerequisite to be purchased. A company can also include FMD responsiveness in ongoing supplier evaluation performance ratings that may influence awarding future business. Once an FMD is received in well-formed XML format, loading this data to the customer’s system can be automated for maximum efficiency and reused through the FMD cascade process. We have seen it work and only need more FMDs entering the road. References1. M. Myles, “Supply Chain Data Exchange for Material Disclosure.”Journal of Surface Mount Technology, Vol. 19-1, 2006. https:///knowledge/journal detail.cfm?ARTICLE ID=1232. R. Franz, “Beyond “Lead-Free”: An Update on the IPC-1752A Standard for Materials Declaration.” Electronics Design, Jan. 8, 2015. /components/beyond-lead-free-update-ipc-1752a-standard-materials-declaration3. https:///fmdcomplete/ © 2017 Assent Compliance Inc.IntroductionA customer emails you and says,“Please provide your FMD’s for this list of parts”Your reaction?IPC Standardso IPC-1752A Materials Declaration Management Standardo IPC-1751A Generic Requirements for Declaration Process Managemento Both specify XML (Extensible Markup Language) machine-readable formato IPC-1752A Class D supports FMD with Homogenous Materials and Substances IEC 62474 also under revision for better harmonization with IPC-1752 XML format Good tools are needed to generate FMD XML at the beginning of the supply chainEnd of presentation… but not “The End.”Thank you for your attention : )AcknowledgementThe dedication, innovation and ongoing work of the IPC 2-18b Materials Declaration Task Group is gratefully appreciated –including founding members, current members, chairpersons, andfuture users of IPC-1752.[1]https:///fmdcomplete/ © 2017 Assent Compliance Inc.。
Internal database backup after the upgradeOld backups of the internal database created with dbtool.pl are not usable with Data Protector.You must configure a new backup specification to back up the internal database and configuration.See the online Help index:“IDB,configuring backups”.Apart from using a tape device,the IDB backup in Data Protector differs from Application Recovery Manager in the following details:•the Data Protector services are not stopped during the backup as with dbtool.pl•the VSS database is not backed upUpgrade of backup specificationsBackup specification in Application Recovery Manager do not contain tape devices.After theupgrade to Data Protector,the backup specifications can be used only for ZDB to disk.To use tape functionality(ZDB to disk+tape,ZDB to tape),you must reconfigure the backup specifications,specifying the tape device.Changes in omnib usageIf no options are specified,Data Protector defaults to ZDB to disk+tape.Application RecoveryManager backup sessions started from the CLI using the omnib command will therefore fail dueto missing tape devices.To keep your existing backup specifications without reconfiguring themfor ZDB to disk+tape,use the-disk_only option to run ZDB to disk.Upgrading from Solaris8to Solaris9If you have Data Protector6.20Disk Agent(DA)installed on Solaris8,and you want to upgrade the operating system to Solaris9,consider the impact of this upgrade on Data Protector.It isrecommended to replace the generic Solaris DA installed on the system with the Solaris9DA toensure proper operation of Data Protector and enable advanced backup options for Solaris9,such as backup of extended attributes.Perform the upgrade in the following sequence:1.Upgrade the operating system from Solaris8to Solaris9.For more information,see Solarisdocumentation.2.Remotely install the Disk Agent on the upgraded system using an Installation Server.This willreplace the generic Solaris Disk Agent with Solaris9Disk Agent.See“Remote installation”(page74)or the ob2install man page.Migrating from HP-UX11.x(PA-RISC)to HP-UX11.23/11.31(IA-64) This section describes the procedure for migrating your existing Cell Manager from a PA-RISCarchitecture based HP-UX11.x system to an HP-UX11.23/11.31system for the Intel Itanium2(IA-64)architecture.LimitationsFor details on supported operating system versions,platforms,processor architectures and DataProtector components as well as required patches,general limitations,and installation requirements, see the HP Data Protector Product Announcements,Software Notes,and References.•The migration is supported only from the Data Protector6.20Cell Manager on a PA-RISC based HP-UX11.x system.•For the supported combinations of MoM configurations,see“MoM specifics”(page177).Upgrading from Solaris8to Solaris9175Prerequisite•Before the migration,the Data Protector Cell Manager on a PA-RISC architecture based HP-UX11.x system must be upgraded to Data Protector6.20.LicensesThe new Cell Manager(IA-64system)will have a different IP address as the old Cell Manager,therefore you should apply for the licenses migration prior to the migration.For a limited amountof time,licenses on both system will be operational.If licenses are based on an IP range and the new Cell Manager’s IP address is within this range,no license reconfiguration is necessary.See“License migration to Data Protector6.20”(page205)for details.Migration procedurePerform the migration procedure as follows:1.Install a Data Protector client on the IA-64system and import it to the old Cell Manager’s cell.If you are planning to configure Data Protector in a cluster,install the client on the primarynode.See“Installing HP-UX clients”(page51).2.Run the following command on the old Cell Manager to add the hostname of the IA-64systemto the list of trusted hosts on secured clients:omnimigrate.pl -prepare_clients New_CM_Name,where the New_CM_Name is theclient name of the IA-64system from the previous step.For more information about trusted hosts and securing Data Protector clients,see“Securingclients”(page135)and“Host trusts”(page143).3.Back up the IDB.Make sure that the used media can later be accessed on the new CellManager system.See the online Help index:“IDB backup”.4.Restore the IDB to a temporary location on the IA-64system.See the online Help index:“IDBrestore”.5.Uninstall the Data Protector client from the IA-64system.See“Uninstalling a Data Protectorclient”(page146).6.Install Data Protector Cell Manager on the IA-64system.If you are planning to configure DataProtector in a cluster,install the Cell Manager on the primary node as a standalone CellManager(not cluster aware).See“Installing the Data Protector Cell Manager(CM)andInstallation Server(s)(IS)”(page26).7.If you changed the default Data Protector Inet port on the old Cell Manager,set the same Inetport also on the new Cell Manager.See“Changing the default Data Protector Inet port”(page230).8.Move the restored IDB(residing in a temporary location on the new Cell Manager),andconfiguration data to the same location on the new Cell Manager as it was on the old CellManager.See the online Help index:“IDB restore”.If the old Cell Manager was cluster-aware,comment out the SHARED_DISK_ROOT andCS_SERVICE_HOSTNAME variables in the /etc/opt/omni/server/sg/sg.conf file.This is necessary even if the new Cell Manager will be cluster-aware.9.To migrate the IDB and clients to the new Cell Manager,and to reconfigure the Cell Manager’ssettings,perform the following steps on the new Cell Manager:•If you want to configure a standalone IA-64Cell Manager,run the omnimigrate.pl -configure command.See the omnimigrate.pl man page.•If you want to configure a cluster-aware IA-64Cell Manager:176Upgrading to Data Protector6.20a.Run the omnimigrate -configure_idb command to configure the IDB from theold Cell Manager for use on the new Cell Manager.See the omnimigrate.plman page.b.Run the omnimigrate -configure_cm command to reconfigure the configurationdata transferred from the old Cell Manager for use on the new Cell Manager.Seethe omnimigrate.pl man page.c.Export the old virtual server from the cell by running the omnicc -export_hostOld_CM_Name.d.Configure the primary and secondary Cell Manager.See the online Help index:“MC/ServiceGuard integration configuring”.e.Run the omnimigrate -configure_clients command to migrate the clientsfrom the old Cell Manager to the new Cell Manager.Note that the old Cell Managerwill keep the clients in the configuration files although it will not be their Cell Manageranymore.NOTE:If the/etc/opt/omni/server directory is located on the shared clustervolume,the configuration changes made by the omnimigrate.pl script will affect allnodes in the cluster.NOTE:The old Cell Manager will automatically become a client in the new cell.You canuninstall the Cell Manager component from the old Cell Manager,because it is not necessaryanymore.See“Changing Data Protector software components”(page154).10.Configure the licenses on the new Cell Manager.See“Data Protector6.20product structureand licenses”(page203).11.Additional steps are required if the following is true:•Your cell is a part of the MoM environment.See“MoM specifics”(page177).•Your cell works across a firewall.Reconfigure all firewall related settings on the new Cell Manager.See the online Help index:“firewall environments”.•You want to have an Installation Server on your new Cell Manager.See“Installation Server specifics”(page178).MoM specificsIf the new Cell Manager will be configured in the MoM,additional steps are required after thebasic migration procedure has been completed.The required steps depend on the configurationof the MoM for the old and new Cell Managers in your environment.The supported combinations are:•The old Cell Manager was a MoM client;the new Cell Manager will be a MoM client of the same MoM Manager.Perform the following steps:1.On the MoM Manager,export the old Cell Manager from the MoM Manager cell andimport the new Cell Manager.See the online Help index:“client systems exporting”.2.Add the MoM administrator to the users list on the new Cell Manager.See the onlineHelp index:“MoM administrator,adding”.•The old Cell Manager was a MoM Manager;the new Cell Manager will be a MoM Manager.If the old MoM Manager was the only client in the MoM,no action is necessary.Otherwise,perform the following steps:1.On the old MoM Manager(the old Cell Manager),export all MoM clients.2.On the new MoM Manager(the new Cell Manager),import all MoM clients.3.Add the MoM administrator to the users list on all MoM clients.Migrating from HP-UX11.x(PA-RISC)to HP-UX11.23/11.31(IA-64)177。
Migrating and Specifying Services for Web IntegrationYing Zou, Kostas KontogiannisDept. of Electrical & Computer EngineeringUniversity of WaterlooWaterloo, ON, N2L 3G1, Canada{yzou, kostas}@uwaterloo.caAbstract. With the explosive growth of the Internet, businesses of all sizes aim on applying e-business solutions to their IT infrastructures, migrating their legacy business processes into Web-based environments, and establishing their own on-line services. To facilitate process and service integration, a complete and information rich service description language, is essential for server processes to be specified and for client processes to be able to locate services that are available in Web-enabled remote servers.Within the context of emerging technologies, such as XML, the Internet, and Network-Centric Computing, we propose an architecture that allows for Web-based integration of distributed components and services. The architecture is based on component wrapping, a service description language that allows for the specification of services, and on techniques that support service registration and dynamic service localization.1 IntroductionTremendous changes are taking place in the business world today due to the frequent introduction of new technologies. As these technologies become the mainstream, the focus of e-commerce activities is shifting from customer-to-business transactions, to an e-business to business (B2B) model [8], which integrates business services and business process models, across corporate Intranets or the Internet. Towards this objective, multi-tier architectures, networking, and distributed object technologies have made possible for organizations to deploy complex software applications over the Internet.Modern software systems must conform to requirements, such as flexibility, adaptability, time to market, and ability to withstand continued business process reengineering. Driven by these requirements, the migration and integration of legacy systems towards new platforms and operating environments provide an effective strategy for organizations to maintain their competitive edge [1]. In this context, many consulting firms such as the Gartner Group are predicting that organizations that integrate new development with the existing legacy systems will have a higher success rate, at optimal cost, in the implementation of client/server applications.In this paper we present an architecture that allows for the migration and integration of existing stand-alone services into distributed environments.Fig. 1. Overall ArchitectureIn the core of the system lies a service description language that provides standard, enriched, and well-understood information about the interfaces and the functionality of the offered services. A service registration tool allows for services to be easily registered with the environment. Finally, a search engine can effectively locate services according to specific search criteria, allowing thus for service location transparency.This paper is organized as follows. Section 2 introduces the architecture for Web-based Integration. The issues that arise in Web-based service integration are addressed in section 3. The issues pertaining to the migration of software components as legacy services are presented in section 4. Section 5 discusses the major components of a service description language. The service registration and localization modules are presented in section 6 and 7 respectively. An application scenario is illustrated in section 8. Finally, section 9 provides a summary and the conclusion of the paper.2 Architecture for Web-based Service IntegrationThe Web-based service integration architecture focuses on the use of Web as an open infrastructure where e-business related services and tasks can be defined, composed, and enacted in a fully customizable way.As e-commerce services can be scattered virtually everywhere on the Web, we need an architecture that allows for the separation of business application logic from the client-side presentation logic. The three-tier architecture is instrumental for the deployment of the distributed objects on a Web-enabled environment.We present an open, multi-tier infrastructure, where a service can publish itself, and easily be integrated with other legacy components and services. The proposedarchitecture is depicted in Fig. 1. The first layer (top) consists of a wide range of Web clients, including Web browsers for handheld and embedded systems, or Java/Pure and CORBA based applications running on fully loaded desktops. The second layer relates to services provided by the Web server and application server. The Web server captures the requests from Web clients and directs the requests to the Application server. The application server has been widely adopted as the runtime environment of choice for integrating heterogeneous applications. The core part of the architecture is the underlying services that are added to the application server, including Service Management, Service Localization, and Service Composition and Invocation.The Service Management module maintains a database of the descriptions of the available services. It enables the deployed services to dynamically register their information in a repository. The Service Management module provides a repository for the client processes to use in order to locate available services and compose them for the completion of elaborate business tasks. A service description language provides a customizable way to represent distributed services with enriched information.The Service Localization module is responsible for selecting the required services among many available ones, according to the criteria set by the client process. The service localization enables the clients to search the service by functionality, signatures, performance, and customizability.Finally, the Service Composition and Invocation module provides a framework and a scripting language for dynamically enacting and composing remote services. This module serves as an integrator that allows back-end services and legacy systems to be composed seamlessly.In order to enable the integration of legacy applications in a Web-based environment, we adopt the CORBA standard. The standard allows for legacy applications to be encapsulated in remote objects using wrapper classes and behave as distributed components. This wrapping technology allows clients in virtually any software or hardware platform to invoke remote legacy components in their native operating environments. The legacy application is resident on the CORBA server, which acts as the gateway for the integration. Such a framework provides system support for the invocation and integration of legacy back-end services from any clients.3 Web-based Service Integration MechanismThe generic three-tier architecture can be further separated into four layers [11]: a) presentation layer (Web client); b) content layer (Web server); c) application layer (application server); and d) back-end data and services layer, as shown in Fig. 2. The Web server is responsible to accept HTTP requests from Web clients, and deliver them to the application server, while the application server is in charge of locating the services and returning responses back to the Web server. On the other hand, a thin client in the presentation layer has little or no application logic.Fig. 2. Control Flows in Three-Tire ArchitectureThe Web server can maintain a content repository, or a file system, where the information-based resources are stored and serve as static HTML pages. Upon receiving a request from the client, the Web server retrieves the requested document from the content repository and sends it to the client. In this case, the client entirely relies on the Web server. Programming languages, such as Java, and scripting languages, like CGI, can be used to access the database.To provide the dynamic information generated by software services, the Web server needs to constantly interact with the application server. A servlet provides the dynamic HTML content to clients. When the Web server receives the request for a servlet, it re-directs the client’s request along with the parameters to the application server, which loads the servlet and runs it. Servlets not only have all the features of Java like automatic memory management, advanced networking, multithreading, and so forth but also, allow for enterprise-wide connectivity in the form of JNI (Java Native Interface), JDBC, EJBs, RMI, and CORBA. Servlets can make calls to back-end services, other servlets, or to the Enterprise JavaBeans [12].Once the servlets are deployed on an application server, they can be accessed from any other Web server. This can be achieved provided that the client’s request contains the URL of the servlet with the correct name, type, parameters, and initial values. The combination of EJBs and Servlets, CORBA objects and Servlets, and RMI objects and Servlets, can be used to invoke back-end services accessed by the Web clients via HTTP connections. However, CORBA and Enterprise Java Beans are not a panacea for all problems that may arise when integrating services in a distributed environment, but they provide the building blocks for distributing applications over a diverse range of platforms and operating environments.4 Example Service Migration to a CORBA EnvironmentIn order to integrate existing systems that encapsulate valuable business logic, the first step is to re-engineer these systems so that they can be used in a distributed environment. In the approach discussed in this paper, we utilize reverse engineering and design recovery techniques to identify specific components that encapsulate valuable business logic for a specific application. These techniques have been investigated as part of another project with IBM and are presented in [13, 14]. Once specific legacy components are identified through the use of program analysis, their behavior must be specified in terms of well-defined interfaces. In order to integrate the identified components to a heavily heterogeneous Web-enabled distributed environment, we must define an appropriate middleware. The CORBA specification provides a suitable infrastructure for integration, due to its platform, language, and vendor independence.The component interface hides the implementation details inside the component and allows only signatures of services to be published to its clients. Moreover, it defines a set of properties and behaviors that represent a component’s API. Properties are represented in terms of attributes, which can be accessed by accessors and mutators. Similarly, method parameters and return types can be represented by IDL interfaces.In a related software migration case study we have used reverse engineering techniques in order to analyze and migrate the AVL GNU tree libraries from C procedural code to a new C++ object oriented implementation [13, 14]. The new migrant object oriented AVL tree library can be considered as a component, consisting of several classes. In this section we present how such a collection of C++ classes from the GNU AVL tree library cab be migrated in a CORBA environment.In a nutshell, the interface for the new AVL tree component consists of several stub interfaces that correspond to wrapper classes. To migrate the standalone identified components into a distributed computing environment, the object wrapping approach can be adopted. The wrappers implement message passing between the calling and the called objects, and redirect method invocations to the actual component services. The concrete process to accomplish wrapping is implemented in terms of three major steps.The first step focuses on the specification of components in CORBA IDL as shown in Fig. 3.The second step deals with the CORBA IDL compiler to translate the given IDL specification into a language specific (e.g. C++), client-side stub classes and server-side skeleton classes. Client stub classes and server skeleton classes are generated automatically from the corresponding IDL specification. The client stub classes are proxies that allow a request invocation to be made via a normal local method call. Server-side skeleton classes allow a request invocation received by the server to be dispatched to the appropriate server-side object. The operations registered in the interface become pure virtual functions in the skeleton class.The third step focuses on wrapper classes that are generated and implemented as CORBA objects, directly inheriting from the skeleton classes. The wrapper classes encapsulate the standalone C++ object by reference, and incarnate the virtual functions by redirecting them to the encapsulated C++ class methods. The newmodule AVL{interface corba_ubi_btRoot;interface corba_ubi_btNode;interface corba_SampleRec;typedef char corba_ubi_trBool;interface corba_SampleRec{void putName(in string val);string getName();void putNode(in corba_ubi_btNode val);corba_ubi_btNode getNode();long getDataCount();void putDataCount(in long aval);};interface corba_ubi_btNode {void putBalance(in char val);char getBalance();long Validate();//......};interface corba_ubi_btRoot{corba_ubi_trBool ubi_avlInsert(in corba_ubi_btNode NewNode,in corba_SampleRec ItemPtr,in corba_ubi_btNode OldNode );// ......};};Fig. 3. AVL Component Interface Definitionfunctionality of the legacy object can be added in the wrapper class as long as the method name is registered in the interface.For example, the SampleRec class is one of the classes identified within the AVL tree component. The wrapper_SampleRec inherits from the skeleton class sk_AVL::_sk_corba_SampleRec, which is generated from the CORBA IDL to C++ compiler. The wrapper class, wrapper_SampleRec, encapsulates a reference of SampleRec class as shown in Fig. 4.When a client invokes a method through CORBA, it passes the CORBA data type parameters. The wrapper classes need to translate the CORBA specific data types from the client calls to the data types used by encapsulated C++ classes. Fig. 5 illustrates the transformation from the CORBA specific type such as corba_SampleRec_ptr to the SampleRec used in the C++ function. In the same way, the wrapper classes convert the returned values from the C++ class to the CORBA specific data type.class wrapper_SampleRec : public _sk_AVL::_sk_corba_SampleRec{private:SampleRec& _ref;char *_obj_name;public:wrapper_SampleRec(SampleRec& _t,const char *object_name = NULL):_ref(_t),_sk_AVL::_sk_corba_SampleRec(object_name);SampleRec* transIDLToObj(AVL::corba_SampleRec_ptr obj);void putNode(AVL::corba_ubi_btNode_ptr val);AVL::corba_ubi_btNode_ptr getNode();~wrapper_SampleRec(){delete &_ref;free (_obj_name);};//......};Fig. 4. An Example Wrapper ClassSampleRec* wrapper_SampleRec::transIDLToObj(AVL::corba_SampleRec_ptr obj){if (CORBA::is_nil(obj)) return NULL;// set up the data members of _ref object_ref.putName(obj->getName());_ref.putDataCount(obj->getDataCount());//translate the ubi_btNode to corba_ubi_btNode_ptr by wrapper//class NodeWrapubi_btNode *NodeImp = new ubi_btNode();wrapper_ubi_btNode NodeWrap(*NodeImp, _obj_name);//translate corba_ubi_btNode_ptr type returned from//obj->getNode() to ubi_btNode * by transIDLToObj() in//wrapper object NodeWrap._ref.putNode(NodeWrap.transIDLToObj(obj->getNode()));return &_ref;}Fig. 5. Example for Object Type TranslationSince IDL does not support overloading and polymorphism, each method and data field within the interface should have a unique identifier, in order to disambiguate references to programming entities that correspond to different languages. For example, C++ supports overloading, but C does not. If the polymorphism and overloading methods occur in one class, it is necessary to rename these methods by adding the prefix or suffix to the original name when they are registered in the interface, avoiding changing the identified objects. This “naming” technique allows unique naming conventions throughout the system, without violating code style stand-Fig. 6. Key Element of Service Specificationards. The wrapper classes are responsible to direct the renamed overloaded and polymorphic methods to the corresponding client code.If the polymorphism and overloading methods occur in the inheritance relationship, we can take advantage of C++ upcast feature, only register the sub-class in the component interface, and upcast the sub-class to its super class when the polymorphic or overloading methods in super class are invoked.5 Service Description LanguageIn this section, we present the prototype of a service description language that provides a standard format to represent, register, and store information related to back-end services. To facilitate the integration of back-end services, a meta level description language is essential to effectively locate registered services. The meta-level description for the software services can be published at the same time as the distributed objects are deployed onto the application servers, or some time later when the enterprise would like to make their software services available.5.1 Structure of Service Description LanguageG enerally, a service can be represented in a multi-faceted way, by specifying, for example, vendor, run time specifications, compile time requirements, method signatures, as well as, pre- and post-conditions. Each of these aspects is denoted as a Service Description Fact. Different Description Facts specify different properties of the services.In a nutshell, the specification of the software services is divided into two layers namely General propertie s and Service Interface properties, as illustrated in Fig. 6.<?xml verstion="1.0"?><SDL><GeneralInfo><ServiceDef><ServiceName> <!-- Specify service ID and name -- ></ServiceName><ServiceCatalog><!--Specify service category--></ServiceCatalog><URL > <!-- Specify service URL linke --></URL><VersionNumber /> <!--Specify version number--></ServiceDef><Manufacturer> <!-- Specify vendor information--></Manufacturer><RunTimeEnv> <!-- Specify run-time environments--><OSs><OS name="" version=""/></OSs></RunTimeEnv><CompileTimeEnv> <!-- Specify compile time environments--></CompileTimeEnv><Funcationality><!-- Specify abstract and detailed information --><!-- about service funcationality--></Functionality></GeneralInfo><ServiceInterface><Types><!--Lists the Types of components inside the service interface. --></Types><ServletML><!--Lists the servlet interface --><Parameters><Parameter><Name /><Type /><Value /></Parameter></Parameters></ServletML><EJBML> <!--Specify the EJBs interface --></EJBML><CORBAML> <!--Specify the CORBA interface --></CORBAML></ServiceInterface></SDL>Fig. 7. Overall Structure of Service Description LanguageEach layer contains specific information at different levels of abstraction. The structure of a service description document is illustrated in Fig. 7.To enable a service binder to locate the requested correct service with high precision and recall levels, the General properties should contain facts that relate to such aspects as general service definition, manufacture information, run-time and compile-time properties, signatures, version numbers, implementation language, and functional descriptions. For example, for a CORBA wrapped service object, it is important to specify the ORB agent address, which is responsible for invoking the requested CORBA object by the name and URL address of the object.For the purpose of Web-based service integration, it is important to disclose the interface of the distributed components to client processes. Similarly, the Service<?xml version="1.0"?><!ELEMENT newTags (newTag)+><!ELEMENT newTag (startingPoint, tagDef)><!ELEMENT startingPoint (#PCDATA)><!ELEMENT tagDef(tagName, attList*, containedTags*)><!ELEMENT tagName (#PCDATA, tagContent*)><!ELEMENT attrList (attr)+><!ELEMENT tagContent (#PCDATA)><!ELEMENT containedTags (tagDef+, group)><!ELEMENT group (group* | tagName*)><!ATTLIST group groupName CDATA #REQUIRED><!ATTLIST group groupType (SEQ|OR) #IMPLIED ><!ATTLIST group groupOccurs(once|optonal|requried) #IMPLIED><!ATTLIST tagDef occurs(once|optional|required) #REQUIRED><!ATTLIST attr attrName CDATA #REQUIRED><!ATTLIST attr attrType CDATA #REQUIRED><!ATTLIST attr attrValue CDATA #IMPLIED>Fig. 8. DTD for Adding New Fact and ContentInterface layer specifies the APIs of the registered components. As stated earlier, there are different technologies to make the back-end services available to remote clents. These technologies include servlets, EJBs, and CORBA. Each type of back-end services is registered by its own specific interface description.For servlets, the inputs are embedded in HTML forms, which contain the HTML types of inputs, the names of parameters and the allowable values. For the EJBs, the back-end services can be composed of several beans (session beans, or entity beans) in one jar file. Each bean has its own home interface and remote interface. When a service is implemented by the CORBA standard, it may include several CORBA IDL interfaces as encapsulated in the CORBA IDL “module” name scope. For the interface within CORBA and EJBs components, it is necessary to declare the available methods, parameters and the types of method parameters and return values. To reduce the complexity in definition of service description language, we inherit the interface from EJBs and CORBA IDL by inserting them under the <EJBML> tag and <CORBAML> tag respectively.5.2 Extensibility of the Service Description LanguageThe extensibility of the service description language is crucial for representing services in distributed Web-enabled environments. For example, new service categories can be added or existing service descriptions can be extended.The DTD for the Service Description Fact specifies its syntax and allows for such Service Descriptions to be proven syntactically valid. The DTD for the Service Description language is illustrated in Fig. 8. New Service Description facts can be added by using the newTag element contained in the newTags element.<?xml version="1.0"?><!DOCTYPE newTags SYSTEM "patSpec.dtd"><newTags><newTag><startingPoint>SDL.GeneralInfo</startingPoint><tagDef occurs="once"><tagName>RunTimeEnv</tagName><containedTags><tagDef occurs="required"><tagName>OSs</tagName><containedTags><tagDef occurs="required"><tagName> OS </tagName><attList><att attrName="name" attrType="CDATA" /><att attrName="version" attrType="CDATA" /></attList></tagDef></containedTags></tagDef></containedTags></tagDef></newTag></newTags>Fig. 9. Run Time Environment Fact DefinitionWith the fact specification DTD, the addition of new facts is uniquely identified and inserted in a way that maintains the syntactic validity of the description. In Fig. 9, for example, the addition of the Run-time environment fact is illustrated. In this example, the new fact is inserted under the GeneralInfo element with the tag name of RunTimeEnv. RunTimeEnv element can occur once under GeneralInfo element. It contains an OS element, which specifies the operating systems to run the service. The OS element may occur one or more times, and can have attributes that denote its name and version number.Meanwhile, new content can be easily introduced into the existing service description under the tag <ServiceCatalog> category (Fig. 7).5.3 Structure of DatabaseService Descriptions and fact specifications (D TDs) require a database for the persistent storage of the XML encoded component and service interface description.To keep the database management simple and achieve flexibility in the service description, we use one table to map the service ID and the external XML filename for each service description. Each fact consisting of a service description is stored in a separate table. The primary key of these tables is the service ID generated during registration. In the same way, another table is created to store the file name of the DTD for each fact.The Service Management module (shown in the Fig. 1) is responsible to maintain the service database. It can insert a new service description, delete, and modify the existing one. For this task, we utilize the IBM DB2 XML extender to map XMLFig. 10. Service Specification Fact ListService Descriptions to DB2 tables. In general, the service manager retrieves from the database table the description filename, and then extracts the whole XML document by using traditional SQL queries. When a service is registered, the service manager can check for duplicate definitions, generate the service ID, and insert the description into the database. The Service Management Module is implemented by Enterprise Java Bean, which provides the support for transactions.6 Service RegistrationFor the service registration, we have designed a Web based interface to serve as a service registration authoring tool, which allows for the user to specify the service description by filling in forms in a Web interface, as shown in Fig. 10. Then the service description is generated automatically from the information provided.As mentioned earlier, in order to provide maximum customizability, the service description language is separated into independent facts. Moreover, the environment allows for new facts to be added at anytime. This interface allows the user to select the required facts by filling predefined forms. Some facts are indispensable, such asService Definition. After submission, the Web Interface will create an HTML form asFig. 11. Service Description Interfaceshown in Fig. 11, where the user can add more information about the newly registered service.For example, once the legacy components are wrapped as distributed objects, as discussed in section 4, their information can be described through the Web interface and registered into the service repository.7 Service LocalizationA prototype service localization mechanism allows for distributed software services to be located much like a search engine locates content (data) in Web pages.The system can provide two ways for clients to submit search queries, via the Web HTML Interface, or by an XML formatted document that may be part of a client’s request for a service.The design of the query language aims to allow users to provide as many featuresas possible in order to specify the services being sought. The service description facts。