<rt id="bn8ez"></rt>
<label id="bn8ez"></label>

  • <span id="bn8ez"></span>

    <label id="bn8ez"><meter id="bn8ez"></meter></label>

    Tauruser

    JSF will hibernate in spring.

      BlogJava :: 首頁 :: 新隨筆 :: 聯(lián)系 :: 聚合  :: 管理 ::
      24 隨筆 :: 2 文章 :: 19 評論 :: 0 Trackbacks

    2007年3月10日 #

    物料

    物料用于表示成品、原料或中間產品。每個物料對應于一個最小存貨單位(SKU)。例如,同一個庫存中的兩個不同模型的白襯衫,如果尺寸不同或款式不同,則它們?yōu)閮蓚€不同的 SKU。兩個不同庫存中的同一模型的襯衫也是兩個不同的 SKU。因此如果您要表示不同倉庫中的同一襯衫的庫存,您需要創(chuàng)建不同的物料,并在需要時將它們分在一個物料分組中,從而便于在報告中集合結果。

    資源

    通常情況下,資源被用于建模機器、工具、車輛、設備或工人。不要使用資源來建模正被消耗或生產的物料;請使用物料來完成上述目的。資源可被組合成資源分組,以便更好地組織數(shù)據;例如,改進甘特圖的可見性。資源分組可在主數(shù)據制表符上獲得。

    儲存單元

    儲存單元用來表示物料或場所的物理儲存設施。儲存單元可以為單目的(可以儲存一個物料),也可以為多目的(可以儲存幾個物料)。如果不是附屬于一個一元的資源,那么儲存單元只是一個帶可能的最大儲存能力的場所。它可用來建模一個倉庫。當附屬于一個一元的資源時,儲存單元可以建模一個儲存容器。一元的資源確保容器中各批次的順序。生產活動可能會產出或消耗一些儲存單元中的物料。物料可通過采購或需求的功能在一個特定的儲存單元中獲得。注意當為物料指定一個儲存單元時,任何關于該物料的需求、采購或物料生產都必須指定該儲存單元。注意您必須聲明可儲存的物料,這樣該儲存單元就能夠儲存這些物料。對多場所的問題,儲存單元也可用來建模場所。可為其指定經度、緯度和類別。

    配方

    有關物料清單和程序安排的配方組信息配方通常建模了生產流程,并由活動原型和關聯(lián)的約束所組成。每個活動是批大小為 1 的規(guī)范生產訂單的原型。每個活動可能會使用一個可供選擇的模式按不同的費用在可供選擇的資源上執(zhí)行。模式可從不同的儲存單元進行生產或消耗。

    單元

    單元用來表示消耗或生產的物料數(shù)量的量度單位。這個編輯器允許創(chuàng)建和編輯一個單元,并且在適用的條件下,也允許從公制的標準單位換算成其他單位。一個度量單位沒有維度或標準換算系數(shù)。例如,托盤、被子或盒子根據里面包含的物料可能有不同的換算系數(shù)。其他的度量單位有維數(shù),因為可按照標準的方式換算成公制,如長度、表面積、體積和質量。例如,公制的噸是一個質量的維數(shù),在公制(公斤)中來自維數(shù)的標準單元的換算系數(shù)總是1/1000,它不依賴于被量的物料。 質量的標準單位是公斤,長度的標準單位是米,表面積的標準單位是平方米,而體積的標準單位是立方米。
    所有的計算都是按照物料的主單元來進行的。但是,您可以為用在圖形用戶界面進行顯示的物料定義二級單元。在物料制表符上標記物料的主要和顯示單元。請注意不同換算系數(shù)的幾個物料可能會共享同一個單元。

    物料分組

    物料分組用于集合報告中的結果。一個物料可以為多個分組的成員。

    資源分組

    對一個給定的資源分組類型,資源可為該類型的一個分組的成員。資源分組用來改進數(shù)據結構或資源相關信息的可見型。

    配方分組

    配方分組可用來將配方組合到一起,以用于部分的加載或分解。一個配方可以為多個分組的成員。

    需求

    使用以要求在一個時間窗口內有一定數(shù)量的可交付物料使用以要求在一個時間窗口內有一定數(shù)量的可交付物料

    采購

    使用以輸入從工廠外采購的物料或根據生產的日期給庫存一個使用年限。

    posted @ 2009-07-23 14:24 Tauruser 閱讀(314) | 評論 (0)編輯 收藏

    ILOG's supply chain applications provide powerful and easy-to-use supply chain planning and scheduling capabilities that are complementary to SAP and utilize ILOG's optimization, scheduling and visualization technologies.

    ILOG LogicNet Plus XE

    ILOG LogicNet Plus XE is a network design and planning solution that combines the advanced optimization technology of ILOG CPLEX with an easy-to-use graphical user interface to manage the world’s most complex supply chain.
    ILOG LogicNet Plus XE facilitates quick analysis of the tradeoffs between production, warehousing, transportation costs, carbon footprint, and service requirements; as well as the calculation of the optimal network configuration for different cost and service objectives. A model’s solutions can be viewed, compared and easily exported to tables and graphs for presentations and further analysis.

    ILOG Inventory Analyst

    ILOG Inventory Analyst is a Web-based, multi-echelon inventory optimization solution that provides end-to-end functionality for manufacturers, retailers and distributors. It combines the advanced optimization technology of ILOG CPLEX with an easy-to-use graphical user interface (GUI), to manage the world’s most complex supply chains. It handles both inbound/outbound and distribution-focused business models, allowing companies to answer a broad range of business questions—from determining the right inventory policies and strategic positioning of inventory, to the ongoing setting of safety stocks and inventory levels in operational environments.

    ILOG Product Flow Optimizer

    ILOG Product Flow Optimizer (PFO) is a part of ILOG’s LogicTools Suite of Supply Chain Applications. It is a powerful and easy-to-use integrated stocking and distribution strategy solution for supply chain and inventory optimization. It helps facilitate both strategic and tactical planning, with built-in integration capabilities to easily connect plans to other systems. Users share a common database that fosters fast movement from one module to another.

    With ILOG PFO, businesses can analyze tradeoffs between transportation, warehousing, inventory carrying costs, and service requirements to arrive at the optimal product delivery path for customers. Companies improve profitability and meet their customers' requirements. Solutions can be viewed, compared and easily exported to tables and graphs for presentations and further analysis.

    ILOG Plant PowerOps

    Extend the value of your existing IT investments with ILOG Plant PowerOps (PPO). ILOG Plant PowerOps takes production planning to a new level for managing demand variability and building executable schedules. It's the only application that offers integrated planning and detailed scheduling for the difficult production challenges associated with the fast-moving consumer goods, pharmaceutical and chemical industries. No other supply chain application contributes as much to the efficient management of tanks, cleaning or sterilization-in-place and process step changeover procedures.

    ILOG Plant PowerOps is based on the most effective optimization models ever built for these challenges. It is the perfect extension to your enterprise resource planning (ERP) or supply chain management (SCM) system and it performs beyond the capabilities of traditional advanced planning and scheduling solutions. ILOG Plant PowerOps helps you address key issues in the food and beverage, chemical, pharmaceutical, and other consumer packaged goods (CPG) industries.

    ILOG Transportation Analyst

    Companies must analyze their transportation network strategies and compare multiple what-if scenarios across many dimensions. Existing transportation solutions focus on the operational and are overly complex for strategic use. Spreadsheet analysis is too limited to find the most economical solutions.

    ILOG Transportation Analyst lets you quickly analyze many different strategies so you can promptly determine the best way to deliver your products and utilize your transportation assets. Manage your vehicle shipment assignments and determine your company's pickup and delivery sequencing to minimize costs while adhering to business constraints.


    posted @ 2009-07-22 15:13 Tauruser 閱讀(415) | 評論 (0)編輯 收藏

    Through its Java, .NET, Ajax, C++, Eclipse and Adobe Flex/AIR graphics libraries and components, ILOG provides the industry’s most comprehensive set of graphics tools for creating sophisticated, interactive user displays. ILOG's graphics products enhance decision-making speed and ability by making vast quantities of complex data more comprehensible and manageable for users.
    Including ILOG JViews Diagrammer, ILOG JViews Maps , ILOG JViews Gantt , ILOG JViews Charts , ILOG JViews TGO , ILOG JViews Maps for Defense , ILOG JViews Graph Layout for Eclipse, ILOG Gantt for .NET , ILOG Diagram for .NET , ILOG Views Component Suite , ILOG Server , ILOG DB Link , ILOG Elixir .
    posted @ 2009-07-22 14:51 Tauruser 閱讀(301) | 評論 (0)編輯 收藏

    ILog Optimization Suits is Integrated Tools and Engines for Optimization Modeling and Application Development.
    ILOG has long offered the world's most advanced optimization engines for solving tough business and research problems. ILOG OPL Development Studio provides the most complete integrated development environment (IDE) for developing, debugging and tuning optimization models.
    With the introduction of ILOG Optimization Decision Manager (ODM), ILOG offers complete support for the optimization model-based application development process. Modelers and IT personnel can collaborate in entirely new ways to rapidly develop and deploy state-of-the-art planning and scheduling applications that take decision support to a new level.

    ILOG OPL Development Studio
    ILOG OPL Development Studio is a complete, integrated development environment (IDE) for building, debugging and tuning optimization models across the full range of planning and scheduling problems. ILOG OPL Development Studio supports the complete model development and deployment process and is required in order to use ILOG ODM. It is designed to take maximum advantage of ILOG CPLEX's and ILOG CP Optimizer's advanced features.

    ILOG Optimization Decision Manager (ODM)
    ILOG Optimization Decision Manager (ODM) is a specialized application development and deployment tool that help ILOG OPL Development Studio users build highly interactive, state-of-the-art decision support applications. Business users can participate easily in the model and application development process, ensuring the final planning or scheduling application accurately captures decision-making problems while providing excellence in scenario creation and comparison, constraint relaxation and goal balancing.


    ILOG CPLEX
    ILOG CPLEX delivers high-performance, robust, flexible optimizers for solving linear, mixed-integer and quadratic programming problems in mission-critical resource allocation applications.

    ILOG CP Optimizer
    ILOG CP Optimizer uses domain reduction and constraint propagation to efficiently solve problems that are highly combinatorial with highly logical content—problems that are usually difficult or impossible to represent with linear expressions.



    posted @ 2009-07-22 14:36 Tauruser 閱讀(381) | 評論 (0)編輯 收藏

    Automated decisions, ranging from whether to accept a loan application or pay a health care claim, to whether a credit card transaction should be flagged as suspect or awarded loyalty points, are the lifeblood of business. But defining and changing those decisions (business rules) can be a challenge with traditional software solutions.
    ILOG BRMS solutions allow your organization to make easy, safe and reliable decision changes. We give you the right tools in the right environments for every stakeholder with a role in managing automated decisions.
    With a BRMS, developers and architects can extract the business logic from the traditional code of an application. When business policies are hard-coded into an enterprise application, the process of updating the system requires specialist programming staff, puts the stability of the system at risk, and can take a long time. By externalizing the business logic from a business application with business rules, IT users can develop and run the business logic independently of the application.
    ILOG JRules is a Business Rule Management System (BRMS) that allows both business and IT users to manage the rules that drive business.
    posted @ 2009-07-22 14:16 Tauruser 閱讀(375) | 評論 (0)編輯 收藏

    Activities

    Defines activities in the data model.
    An activity is a task to be completed. Activities are hierarchical in nature. This means that a main activity, called parent activity, can be broken down into subactivities. A subactivity, or child activity, can in turn be a parent activity of other subactivities or, if it is at the very end of a branch of the hierarchy, it is a leaf activity. A leaf activity is an activity that has no child activity.
    In addition to its name and identifier, an activity is defined by its start time and end time, which determine an interval called the duration of the activity. If the start and end times are identical, the duration is equal to 0. A zero-duration activity is commonly called a milestone. Typically, milestones are not rendered by the same renderer as activities with a non-zero duration.

    Resources


    A resource is a means by which an activity can be completed. Resources can be persons, premises, equipment, and so forth. Like activities, resources are also hierarchical in nature.
    If resources are people, the parent resource is a department while the child resources are the individual employees. Likewise, you may want to group resources by physical location or by type of machinery.

    Constraints


    A constraint is a type of condition set between two activities. Constraints are represented by arrowed polyline links.
    Constraints can have one of the following types:
    • start to start
    • start to end
    • end to start
    • end to end

    The source activity—that is, the activity whose start or end controls the start or end of another activity—is called the From activity. Conversely, the target activity—that is, the activity whose start or end depends on the start or end of another activity—is called the To activity.

    Reservations

    When a resource is assigned to an activity, this assignment is called a reservation. In the terminology of JViews Gantt, a reservation represents the assignment of one resource to one activity.
    An activity can have multiple resources reserved and similarly, a resource can be reserved for more than one activity. The activity that reserves the resource cannot be changed after the reservation is created.

    posted @ 2009-07-15 16:15 Tauruser 閱讀(367) | 評論 (0)編輯 收藏

    裝好ILOG后,ILOG使用的是自帶的JDK版本,可以按照下面的方法將ILOG升級到新的JDK版本上去。
    1、安裝新的JDK到機器上,設安裝目錄為%NEW_JDK_HOME%.
    2、找到%ILOG_HOME%\ODME33\Developer\bin\x86_win32\javapath.odmcfg,將里面的內容更新為%NEW_JDK_HOME%/BIN
    3、將%NEW_JDK_HOME%/jre拷貝到%ILOG_HOME%\ODME33\Developer下,當然最好先對原%ILOG_HOME%\ODME33\Developer\jre做一下備份。
    4、打到Eclipse ODM Enterprise,在首選項->Java->已安裝的JRE中添加我們新安裝的JDK。
    5、在首選項Java->編譯器,將JDK的一致性級別設為1.6.

    Done

    posted @ 2009-07-15 10:37 Tauruser 閱讀(406) | 評論 (0)編輯 收藏

    <dependency>
         <groupId>org.apache.struts</groupId>
         <artifactId>struts2-rest-plugin</artifactId>
         <version>2.1.6</version>
    </dependency>
    posted @ 2009-02-09 19:44 Tauruser 閱讀(401) | 評論 (0)編輯 收藏

    在動態(tài)創(chuàng)建控件的時候有時候需要根據現(xiàn)有的控件高度去設置新控件的高度,如何動態(tài)取得已有控件的高度就是一個問題了。可以使用下面的代碼進行取得控件高度。
    dojo.style(dojo.byId("mapRegion"), "height")
    頁面上已有代碼:
    <div dojoType="dijit.layout.ContentPane" region="center" id="mapRegion">
    </div>


    posted @ 2009-02-01 21:35 Tauruser 閱讀(503) | 評論 (0)編輯 收藏

    下面為使用dojo動態(tài)創(chuàng)建Button的代碼段。
    function createButton(id, params){
        
    var button = document.createElement("span");
        button.setAttribute(
    "id", id);
        dojo.byId(
    "somewherePlaceButton").appendChild(button);
                               
        
    new dijit.form.Button(
            params
            ,dojo.byId(id));
    }
    調用例子:
    createScenicSpotButton('button1',{id: "html_Button1",label: "",alt: "My button",title: "Button1",onClick: HandleFunction});


    posted @ 2009-02-01 13:26 Tauruser 閱讀(645) | 評論 (0)編輯 收藏

    把mgscl更名為mgsclp后,文哥就跟我說項目在他的Eclipse里Run不起來了。拋出以下異常。

    嚴重: Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener
    org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 
    'dataSource' defined in class path resource [applicationContext-resources.xml]: Circular placeholder reference 'jdbc.driverClassName' in property definitions
        at org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.processProperties(PropertyPlaceholderConfigurer.java:
    268)
        at org.springframework.beans.factory.config.PropertyResourceConfigurer.postProcessBeanFactory(PropertyResourceConfigurer.java:
    75)
        at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:
    554)
        at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:
    528)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:
    363)
        at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:
    255)
        at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:
    199)
        at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:
    45)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:
    3843)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:
    4342)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:
    1045)
        at org.apache.catalina.core.StandardHost.start(StandardHost.java:
    719)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:
    1045)
        at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:
    443)
        at org.apache.catalina.core.StandardService.start(StandardService.java:
    516)
        at org.apache.catalina.core.StandardServer.start(StandardServer.java:
    710)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:
    578)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
    39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
    25)
        at java.lang.reflect.Method.invoke(Method.java:
    597)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:
    288)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:
    413)

    這個問題在之前bsdts里也遇到過,主要是因為在appfuse生成的項目里配置文件jdbc.properties里都使用了占位符 placeholder,如果項目需要正常在Eclipse的Tomcat里Run里來,這個文件的占位符應該正確的給Replace掉。出現(xiàn)上面的異常 主要就是占位符沒有被正確的Replace掉。好了,既然原因找到了,我們下面來看下如何解決。
    在Bsdts里面遇到這個問題的時候,我們經常是重新在Console下面運行mvn package 或者mvn install后,再重新Deploy就可以了。但是實踐證明在mgsclp里面是行不通的。這是為什么呢?
    經過查看mgsclp里的Target里的jdbc.properties文件,發(fā)現(xiàn)其已經給正確Replace掉了。只是沒有正確地給Eclipse Deploy到tomcat里。
    根據上面,我初步確定是Eclipse配置的問題。
    我們現(xiàn)在知道的情況有哪些呢?
    一是maven是會把placeholder自動replace的.這個我們可以通過查看Target/classes目錄下面的jdbc.properties文件可以看到,經過maven處理后的placeholder是給正確replace了.
    2.在Eclipse里面部署過后的jdbc.properties文件的plackholder沒有被replace掉.

    Solution:
    我們的jdbc.properties文件就是位于src/main/resources目錄下面的.我們可以看到Excluded里面已經有很多 properties給Excluced了.這是i18n的文件,同樣也是需要maven進行編碼處理的,而jdbc.properties文件是要進行 replace plackholder處理.本質上是一樣的.這里把文件加進去后,eclipse也不會進行處理的.所以,我們需要把jdbc.properties文 件同樣加入excluded里面.我們不需要Eclipse對這些文件進行處理.maven處理就行了.這樣子,Eclipse 就不會把maven處理的結果用原來的版本覆蓋了.

    好,現(xiàn)在說回到部署問題.我們的War工程在maven里,只要把target/classes里的東西與src/webapp里面的東西放到 Tomcat就行了.這次相關的配置文件有org.eclipse.wst.common.component. Eclipse是如何知道哪些內容需要部置到Tomcat就是在這個文件里面定義的.關鍵的節(jié)點就是<wb-resource>.由前面所說 我們需要的內容只有兩個target/classes,src/webapp.所以實際上我們只要把這兩個目錄上面的東西放到正確的部署位置就行了.其它 內容都是多余的.于是我只保留下面兩個內容
    <wb-resource deploy-path="/" source-path="src/main/webapp"/>
    <wb-resource deploy-path="/WEB-INF/classes" source-path="target/classes"/>
    這里的部署,只是把這里指定的目錄Copy過去而已不做任務處理,(從我目前觀察的情況是這樣子的).
    我們之前為什么不會呢,就是因為有很多個這樣的節(jié)點.有些節(jié)點會引用沒有處理過的文件.Eclipse再一次把沒有處理過的文件蓋掉處理過的文件,就出現(xiàn)的我們剛開始的時候的問題了.

    好了,今天就到這里。

    posted @ 2008-09-11 23:06 Tauruser 閱讀(3065) | 評論 (0)編輯 收藏

    Last night, I got the book Pragmatic Software Testing-Becoming an Effective and Efficient Test Professional from www.freebookspot.com. I am instrest in the title.
    Recently, most development team try to use the agile process in the development. And most of them are test driven. I also have done many effort to the test. But I still can't do the job well. I hope this book will give me a new vision on the software testing. This page will record my reading note. As you know I can't have the book finished in a short time, so this page will keep updating. Thanks for your reading, If you have any questions and suggestions, plz give a comment.

    Book Structure

    The book was divide into 6 parts, as follow.

    Part I - Goals, Strategies, and Tactics

    Part II - Risk-Based Testing

    Part III - Static Testing

    Part IV - Behavioral Testing

    Part V - Structural Testing

    Part VI - Appendices

    Reading note

    Part I
    Obvious Quesions will be ask, but in many time there is not obvious answer to them. What is effective software testing? What is efficient software testing? What is software testing, anyway? What is quality?
    The answer is important, bacause Your answers to these questions determine what you expect to do as a tester. Other people’s answers to these questions determine what they expect you to do as a tester. Having common expectations up, down, and across the organizational chart and throughout the project team is essential to success. Without such commonality, no matter what you do, someone’s sure to be disappointed. With common expectations, you can all strive for the same goals, and support others in their endeavors.

    Effective as “producing a decided, decisive, or desired result; impressive.”
    Efficient as “productive of the desired effect; especially to be productive without waste.”

    Should look at test effectiveness and efficiency from the project perspective, not the test subproject perspective.
    posted @ 2008-09-05 11:01 Tauruser 閱讀(383) | 評論 (0)編輯 收藏

    昨天,IBM在南校區(qū)信科A講學廳舉行了關于這次SOA大賽的宣講會。我們在東校區(qū)一行四人早早就出發(fā)了,在信科A會合Tomara后,到了講學廳,這次 宣講會到場的人并不多,佑大個講學廳就只有大概二十多人到場,這是出乎我意料之外的。宣講會持續(xù)了一個半小時,從19:00開始到20:30結束,這次宣 講會總體上來,我感覺不錯,讓我更加了解了此次比賽的一個目的與比賽過程中要注意的地方。本來昨天晚上就想動手寫這文章,由于人懶,拖到了現(xiàn)在。

    從這次宣講會上來看,我的理解主要有兩點,一是關注的是參賽團隊對所選問題領域的業(yè)務流程理解,優(yōu)化;二是關注參賽團隊對于IBM提供的整套工具的使用程度。下面我將分別就兩方面談一下我的想法。

    一、關注參賽團隊對所選問題領域的業(yè)務流程理解與優(yōu)化。這一點要求團隊能夠對企業(yè)現(xiàn)有流程進行建模,發(fā)現(xiàn)模型在企業(yè)真正營運當中遇到的問題,何處是流程的瓶頸所在。并針對這些問題與瓶頸所在的地方進行流程重構,優(yōu)化現(xiàn)有的流程。為了在實施前就能夠知道優(yōu)化后的流程是否比現(xiàn)有的流程真正的了改善的地方,需要對流程進行模擬。模擬之后,我們可以基于模型的一系列運行指標(KPI)來比較流程的運行情況。根據模擬的情況可以再對流程進行修改,直到得出一個比較合理的結果。

    在這一部份當中,個人覺得最重要的是對業(yè)務流程的理解,找出問題所在,并能靈活的對其進行調整,以改善企業(yè)運營情況。

    二、關注對IBM提供的整套工具的使用。本次比賽IBM可以說是做到了多贏。一方面提供了一個很好的機會讓在校大學生參與企業(yè)的流程整合工作;一方面為企業(yè)提供了一個機會讓一批有專業(yè)知識的專家與學生為他們現(xiàn)在流程進行義診,提出改進方案;一方面宣傳與推廣了IBM這一套工具,可以說是在市場上一次很好的推廣宣傳。所以,在這次比賽中,一個重要的,對方案評價的標準就是對IBM工具的使用。是否對工具有一個很好的正體把握,是否充分利用的工具提供給我們的功能。宣講當中,李師兄也特別提到了對于規(guī)則引擎的靈活運用。通過這點做到,當業(yè)務規(guī)則變化的時候,普通業(yè)務人員就可以通過規(guī)則引擎的配置做到快速應用新的規(guī)則到業(yè)務系統(tǒng),靈活應對業(yè)務需求的變更。而不需要開發(fā)人員針對變更的需要重新去更改源碼來適應這樣的變更。

     

    總的來說,此次比賽給我的感覺要特別注意這兩點。對問題領域業(yè)務流程整合的深入理解,找出問題,提出優(yōu)化解決方案。有了解決方案后,再使用IBM提供的參賽工具對優(yōu)化方案進行實現(xiàn)。這個實現(xiàn)要求我們對工具有非常深入的了解,能夠靈活應用現(xiàn)有功能實現(xiàn)開發(fā)部署。當然,我們的解決方案也要考慮除業(yè)務外的其它內容。如是否能靈活適應業(yè)務的快速變更。實施變更,是否對現(xiàn)有業(yè)務有影響。變更是否能夠在不停止現(xiàn)有服務的情況下得到部署,即熱部署。等等一系列,我們在下面比賽過程中要深入討論研究的問題。

    淺談至此,希望大家指點批評。

    By Tauruser 2008-5-15


    posted @ 2008-05-15 10:45 Tauruser 閱讀(277) | 評論 (1)編輯 收藏

    今天真是一個好日子,奧運圣火在廣州傳遞,我們Sparkle團隊Blog正式開通,今天下午團隊五位成員將在南校區(qū)第一次正式會面。當然恰逢奧運圣火經過南校,我們還是會去感受一下中國百年奧運夢的盛況。我們先來看一下上午奧運圣火在廣州傳遞的情況吧。


    posted @ 2008-05-07 11:43 Tauruser 閱讀(257) | 評論 (2)編輯 收藏

         摘要: 在Sas IntrNet? Module很多功能都是需要用到CGI(Common Gateway Interface)進行工作。在使用CGI進行工作時候,我們首先要進行CGI服務器的配置。一般情況下可以直接使用Apache來架設CGI服務器。由于我們后期的一些應用可能是在JEE平臺上進行開發(fā),所以在一個可以運行Web Container的Server?上架設CGI服務是有必要的。本文將介紹如何在Tomcat下配置CGI服務。  閱讀全文
    posted @ 2007-09-06 10:40 Tauruser 閱讀(7987) | 評論 (3)編輯 收藏

         摘要: 最近試著用一下了MyEclipse發(fā)現(xiàn)MyEclipse果然比較好用,于是想把以前在Eclipse下的項目轉移到MyEclipse下繼續(xù)開發(fā)。在轉移的過程中出現(xiàn)了一些問題,解決了,寫此文記之。  閱讀全文
    posted @ 2007-03-10 18:33 Tauruser 閱讀(6446) | 評論 (7)編輯 收藏

    主站蜘蛛池模板: 在线观看无码AV网站永久免费 | 最近免费字幕中文大全| 国产又粗又长又硬免费视频| 亚洲一区在线免费观看| 麻豆一区二区免费播放网站 | 亚洲国产精品热久久| 久久狠狠躁免费观看2020| 亚洲AV无码日韩AV无码导航| 日本免费在线观看| 亚洲福利视频网站| 免费看韩国黄a片在线观看| 亚洲妇女熟BBW| 免费国产高清视频| 久久精品无码专区免费| 亚洲爆乳精品无码一区二区三区| 久草免费福利视频| 亚洲成人黄色网址| 日韩视频免费在线| aa级女人大片喷水视频免费| 亚洲成人免费在线| 噼里啪啦电影在线观看免费高清 | 暖暖免费日本在线中文| 亚洲第一页中文字幕| 成人毛片视频免费网站观看| 亚洲国产成人AV网站| 中文字幕在亚洲第一在线| 久久久久久AV无码免费网站下载 | 亚洲av成人一区二区三区在线观看| 一级毛片免费播放试看60分钟| 亚洲AV无码久久寂寞少妇| 国产成人免费高清激情明星| 国产精品亚洲精品久久精品| 亚洲色成人中文字幕网站| 日本黄网站动漫视频免费| 男女超爽视频免费播放| 久久久久亚洲av无码尤物| 日韩精品视频免费在线观看| 91精品成人免费国产| jiz zz在亚洲| 国产亚洲欧洲精品| 在线成人a毛片免费播放 |