HTTP Analyzer IE Add-in Edition 1.7.4.2 serial key or number
HTTP Analyzer IE Add-in Edition 1.7.4.2 serial key or number
Spray-Drying of Antioxidant-Rich Blueberry Waste Extracts; Interplay Between Waste Pretreatments and Spray-Drying Process
Abstract
This study aimed to establish an efficient route for converting blueberry waste material (BWM) into antioxidant-rich powders. Extracts were produced from BWM by an aqueous method using water acidified with citric acid, in the absence or presence of Pectinex Ultra SP-L and Cellubrix. All BWM extracts contained antioxidants including phenolic acids, anthocyanins, and flavonoids (total phenolic content (TPC) 3655–4369 mg gallic acid equivalent (GAE) and total anthocyanin content (TAC) 219–296 mg cyanidin-3-glucoside equivalents (CyGE) per 100 g dry extract). Extractions at 50 °C yielded higher TPC and TAC but lower vitamin C and pectin contents than extractions at 20 °C. Spray-drying BWM extracts produced at 50 °C (no enzymatic treatments) and an encapsulant (alginate or inulin) at an inlet temperature 150 °C and feed temperature 50 °C yielded powders with desired dark purplish blue color, water activity (0.25–0.33), flowability, reconstitution time (23–46 s in water or milk), TPC (25–30 mg GAE/g), TAC (17–20 mg CyGE/g), storage stability, and Bifidobacterium-boosting properties. Enzymatic pretreatments of BWM did not confer any advantages in preserving antioxidants in powder products, suggesting that some intrinsic BWM components (e.g., pectins) may play an important role in the encapsulating process. The use of alginate as the encapsulant/drying aid afforded higher powder yields, superior protection of antioxidants, better stability over a prolonged storage or elevated temperature storage, greater retention of TPC/TAC under simulated gastrointestinal conditions, and greater Bifidobacterium-boosting effects, compared to powders prepared using inulin. Thus, simple aqueous extraction methods and spray-drying technology hold enormous promise for producing antioxidant-rich powders from blueberry processing by-products or waste.
This is a preview of subscription content, log in to check access.
References
Akiyama, H., Endam, T., Nakakita, R., Murata, K., Yonemoto, Y., & Okayama, K. (1992). Effect of depolymerized alginates on the growth of bifidobacteria. Bioscience Biotechnology Biochemistry, 56, 355–356.
CASArticle Google Scholar
Arranz, S., Saura-Calixto, F., Shaha, S., & Kroon, P. A. (2009). High contents of nonextractable polyphenols in fruits suggest that polyphenol contents of plant foods have been underestimated. Journal of Agricultural and Food Chemistry, 57, 7298–7803.
CASArticle Google Scholar
Avila, M., Hidalgo, M., Sanchez-Moreno, C., Pelaez, C., Requena, T., & de Pascual-Teresa, S. (2009). Bioconversion of anthocyanin glycosides by Bifidobacteria and Lactobacillus. Food Research International, 42, 1453–1461.
CASArticle Google Scholar
Balasundram, N., Sundram, K., & Samman, S. (2006). Phenolic compounds in plants and agri-industrial by-products: antioxidant activity, occurrence, and potential uses. Food Chemistry, 99, 191–203.
CASArticle Google Scholar
Bener, M., Shen, Y., Apak, R., Finley, J. W., & Xu, Z. (2013). Release and degradation of anthocyanins and phenolics from blueberry pomace during thermal acid hydrolysis and dry heating. Journal of Agricultural and Food Chemistry, 61(27), 6643–6649.
CASArticle Google Scholar
Bodera, P. (2008). Influence of prebiotics on the human immune system (GALT). Recent Patents on Inflammation & Allergy Drug Discovery, 2, 19–153.
Article Google Scholar
Brand-Miller, J., Atkinson, F., & Rowan, A. (2013). Effect of added carbohydrates on glycemic and insulin responses to children’s milk products. Nutrients, 5, 23–31.
CASArticle Google Scholar
Bronnum-Hansen, K., Jacobsen, F., & Flink, M. J. (1985). Anthocyanin colourants from elderberry (Sambucusnigra, L.). 1. Process considerations for production of liquid extract. Journal of Food Technology, 20, 703–711.
Article Google Scholar
Cano-Chauca, M., Stringheta, P. C., Ramos, A. M., & Cal-Vidal, J. (2005). Effect of the carriers on the microstructure of mango powder obtained by spray drying and its functional characterization. Innovative Food Science and Emerging Technology, 6, 420–428.
CASArticle Google Scholar
Condon, J. B. (2006). Surface area and porosity determinations by physisorption: measurements and theory (1st ed.). Boston: Elsevier.
Google Scholar
Corcoran, B. M., Stanton, C., Fitzgerald, G. F., & Ross, R. P. (2005). Survival of probiotic lactobacilli in acidic environments is enhanced in the presence of metabolizable sugars. Applied and Environmental Microbiology, 71, 3060–3067.
CASArticle Google Scholar
Delgado-Vargas, F., & Paredes-López, O. (2003). Anthocyanins and betalains. In F. Delgado-Vargas & O. Paredes-Lopez (Eds.), Natural colorants for food and nutraceutical uses (pp. 167–219). Boca Raton: CRC Press.
Google Scholar
Dolara, P., Luceri, C., De Filippo, C., Femia, A. P., Giovannelli, L., Caderni, G., Cecchini, C., Silvi, S., Orpianesi, C., & Cresci, A. (2005). Red wine polyphenols influence carcinogenesis, intestinal microflora, oxidative damage and gene expression profiles of colonic mucosa in F344 rats. Mutation Research, 591, 237–246.
CASArticle Google Scholar
Dragovic-Uzelac, V., Savic, Z., Brala, A., Levaj, B., Kovačević, D. B., & Biško, A. (2010). Evaluation of phenolic content and antioxidant capacity of blueberry cultivars (Vaccinium corymbosum L.) grown in the northwest Croatia. Food Technology and Biotechnology, 48(2), 214–221.
CAS Google Scholar
Erlandson, J. A., & Wrolstad, R. E. (1972). Degradation of anthocyanins at limited water concentration. Journal of Food Science, 37, 592–595.
CASArticle Google Scholar
Gardiner, G., Ross, R. P., Stanton, C., Lynch, P. B., Collins, J. K., & Fitzgerald, G. (1999). Evaluation of cheddar cheese as a food carrier for delivery of a probiotic strain to the gastrointestinal tract. Journal of Dairy Science, 82, 1379–1387.
CASArticle Google Scholar
Georg, J. M., Knudsen, J. C., Viereck, N., Kristensen, M., & Astrup, A. (2012). Functionality of alginate based supplements for application in human appetite regulation. Food Chemistry, 132, 823–829.
Article Google Scholar
Giusti, M. M., & Jing, P. (2008). Analysis of anthocyanins. In C. Socaciu (Ed.), Foods colorants chemical and functional properties (pp. 479–506). Boca Raton: CRC. Press.
Google Scholar
Giusti, M. M., & Wrolstad, R. E. (2001). UNIT F1.2 characterization and measurement of anthocyanins by UV-visible spectroscopy. In R. E. Wrolstad (Ed.), Current protocols in food analytical chemistry (pp. 1–13). New York: Wiley.
Google Scholar
Hutchings, J. B. (1999). Food color and appearance. Gaithersburg: Aspen Publishers.
Google Scholar
Imeh, U., & Khokhar, S. (2002). Distribution of conjugated and free phenols in fruits: antioxidant activity and cultivar variations. Journal of Agricultural and Food Chemistry, 50(22), 6301–6306.
CASArticle Google Scholar
Iwata, E., Hotta, H., & Goto, M. (2009). The screening method of a bifidogenic dietary fiber extracted from inedible parts of vegetables. Journal of Nutritional Science and Vitaminology, 55, 385–388.
CASArticle Google Scholar
Jacob, J. K., Hakimudin, F., Paliyath, G., & Fischer, H. (2008). Antioxidant and antiproliferative activity of polyphenols in novel high-polyphenol grape lines. Food Research International, 41, 419–428.
CASArticle Google Scholar
Jaya, S., & Das, H. (2004). Effect of maltodextrin, glycerol monostearate and tricalcium phosphate on vacuum dried mango powder properties. Journal of Food Engineering, 63(2), 125–134.
Article Google Scholar
Jaya, S., & Das, H. (2009). Glass transition and sticky point temperatures and stability/mobility diagram of fruit powders. Food and Bioprocess Technology, 2, 89–95.
CASArticle Google Scholar
Jayamanne, V. S., & Adams, M. R. (2009). Modelling the effects of pH, storage temperature and redox potential (eh) on the survival of bifidobacteria in fermented milk. International Journal of Food Science & Technology, 44, 1131–1138.
CASArticle Google Scholar
Kader, F., Rovel, B., Girardin, M., & Metche, M. (1997). Mechanism of browning in fresh highbush blueberry fruit (Vaccinium corymbosum L.). Partial purification and characterization of blueberry polyphenol oxidase. Journal of the Science of Food and Agriculture, 73, 513–516.
CASArticle Google Scholar
Kalt, W., Joseph, J. A., & Shukitt-Hale, B. (2007). Blueberries and human health: a review of current reseach. Journal of the American Pomological Society, 61(3), 151–160.
Google Scholar
Kelishomi, Z. H., Goliaei, B., Mahdavi, H., Nikoofar, A., Rahimi, M., Moosavi-Movahedi, A. A., Mamashli, F., & Bigdeli, B. (2016). Antioxidant activity of low molecular weight alginate produced by thermal treatment. Food Chemistry, 196, 897–902.
CASArticle Google Scholar
Keppler, K., & Humpf, H. U. (2005). Metabolism of anthocyanins and their phenolic degradation products by the intestinal microflora. Bioorganic & Medicinal Chemistry, 13, 5195–5205.
CASArticle Google Scholar
Khanal, R. C., Howard, L. R., & Prior, R. L. (2010). Effect of heating on the stability of grape and blueberry pomace procyanidins and total anthocyanins. Food Research International, 43(5), 1464–1469.
CASArticle Google Scholar
Kim, M., & Kerr, W. L. (2013). Vacuum-belt drying of rabbiteye blueberry (Vaccinium ashei) slurries: influence of drying conditions on physical and quality properties of blueberry powder. Food and Bioprocess Technology, 6, 3227–3237.
Article Google Scholar
Li, C., Krewer, G. W., Ji, P., Scherm, H., & Kays, S. J. (2010). Gas sensor array for blueberry fruit disease detection and classification. Postharvest Biology and Technology, 55, 144–149.
CASArticle Google Scholar
Lima, J. C., Vautier-Giongo, C., Lopes, A., Melo, E., Quina, F. H., & Maçanita, A. L. (2002). Color stabilization of anthocyanins: effect of SDS micelles on the acid − base and hydration kinetics of malvidin 3-glucoside (Oenin). Journal of Physical Chemistry A, 106(24), 5851–5859.
CASArticle Google Scholar
Liyana-Pathirana, C., & Shahidi, F. (2005). Optimization of extraction of phenolic compounds from wheat using response surface methodology. Food Chemistry, 93(1), 47–56.
CASArticle Google Scholar
Markowski, A. S., & Mujumdar, A. S. (1995). Safety aspects of industrial dryers. In A. S. Mujumdar (Ed.), Handbook of industrial drying (2nd ed., pp. 1277–1312). New York: Marcel Dekker Inc..
Google Scholar
Mitsuoka, T. (1990). Bifidobacteria and their role in human health. Journal of Industrial Microbiology, 6, 263–268.
Article Google Scholar
Molan, A. L., Lila, A. A., Mawson, J., & De, S. (2009). In vitro and in vivo evaluation of the prebiotic activity of water-soluble blueberry extracts. World Journal of Microbiology and Biotechnology, 25, 1243–1249.
CASArticle Google Scholar
Montanuci, F. D., Pimente, T. C., Garcia, S., & Prudencio, S. H. (2012). Effect of starter culture and inulin addition on microbial viability, texture, and chemical characteristics of whole or skim milk Kefir. Ciência e Tecnologia de Alimentos, 32(4), DOI: 10.1590/S0101-20612012005000119
Mortensen, P. B., & Clausen, M. R. (1996). Short-chain fatty acids in the human colon: relation to gastrointestinal health and disease. Scandinavian Journal of Gastroenterology, 31, 132–148.
CASArticle Google Scholar
Nakamura, K., Nishimura, Y., Hatakeyama, T., & Hatakeyama, H. (1995). Thermal properties of water insoluble alginate films containing di- and trivalent cations. Thermochimica Acta, 267, 343–353.
CASArticle Google Scholar
Oliveira, R. P. D., Perego, P., De Oliveira, M. N., & Converti, A. (2011). Effect of inulin as a prebiotic to improve growth and counts of a probiotic cocktail in fermented skim milk. LWT - Food Science and Technology, 44, 520–523.
Article Google Scholar
Oozeer, R., Rescigno, M., Ross, R. P., Knol, J., Blaut, M., Khlebnikov, A., & Doré, J. (2010). Gut health: predictive biomarkers for preventive medicine and development of functional foods. British Journal of Nutrition, 103, 1539–1544.
CASArticle Google Scholar
Padayachee, A., Netzel, G., Netzel, M., Day, L., Zabaras, D., Mikkelsen, D., & Gidley, M. J. (2012a). Binding of polyphenols to plant cell wall analogues—part 1: anthocyanins. Food Chemistry, 134(1), 155–161.
CASArticle Google Scholar
Padayachee, A., Netzel, G., Netzel, M., Day, L., Zabaras, D., & Mikkelsen, D. (2012b). Binding of polyphenols to plant cell wall analogues—part 2: phenolic acids. Food Chemistry, 135(4), 2287–2292.
CASArticle Google Scholar
Paes, J., Dotta, R., Barbero, G. F., & Martínez, J. (2014). Extraction of phenolic compounds and anthocyanins from blueberry (Vaccinium myrtillus L.) residues using supercritical CO2 and pressurized liquids. Journal of Supercritical Fluids, 95, 8–16.
CASArticle Google Scholar
Páscoa, R. N. M. J., Machado, S., Magalhães, L. M., & Lopes, J. A. (2015). Value adding to red grape pomace exploiting eco-friendly FT-NIR spectroscopy technique. Food and Bioprocess Technology, 8(4), 865–874.
Article Google Scholar
Pasqualetti, V., Altomare, A., Guarino, M. P. L., Locato, V., Cocca, S., Cimini, S., Palma, R., Alloni, R., De Gara, L., & Cicala, M. (2014). Antioxidant activity of inulin and its role in the prevention of human colonic muscle cell impairment induced by lipopolysaccharide mucosal exposure. PloS One, 9(5), e98031. doi:10.1371/journal.pone.0098031.
Article Google Scholar
US20120036049A1 - System and method for software integration and factory deployment - Google Patents
Info
- Publication number
- US20120036049A1 US20120036049A1US13/160,715US201113160715AUS2012036049A1US 20120036049 A1US20120036049 A1US 20120036049A1US 201113160715 AUS201113160715 AUS 201113160715AUS 2012036049 A1US2012036049 A1US 2012036049A1
- Authority
- US
- United States
- Prior art keywords
- software
- bom
- series
- system
- test
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034methodsMethods0.000claimsdescription86
- 238000004519manufacturing processMethods0.000claimsdescription42
- 239000002585basesSubstances0.000claimsdescription30
- 239000000463materialsSubstances0.000claimsdescription27
- 230000001419dependentEffects0.000claimsdescription8
- 230000000694effectsEffects0.000description14
- 239000000203mixturesSubstances0.000description12
- 238000002360preparation methodsMethods0.000description9
- 238000001914filtrationMethods0.000description6
- 238000004458analytical methodsMethods0.000description4
- 238000005516engineering processesMethods0.000description3
- 238000004364calculation methodsMethods0.000description2
- 230000026676system processEffects0.000description2
- 238000005094computer simulationMethods0.000description1
- 238000004141dimensional analysisMethods0.000description1
- PCHJSUWPFVWCPO-UHFFFAOYSA-NgoldChemical compounddata:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0nMS4wJyBlbmNvZGluZz0naXNvLTg4NTktMSc/Pgo8c3ZnIHZlcnNpb249JzEuMScgYmFzZVByb2ZpbGU9J2Z1bGwnCiAgICAgICAgICAgICAgeG1sbnM9J2h0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnJwogICAgICAgICAgICAgICAgICAgICAgeG1sbnM6cmRraXQ9J2h0dHA6Ly93d3cucmRraXQub3JnL3htbCcKICAgICAgICAgICAgICAgICAgICAgIHhtbG5zOnhsaW5rPSdodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rJwogICAgICAgICAgICAgICAgICB4bWw6c3BhY2U9J3ByZXNlcnZlJwp3aWR0aD0nMzAwcHgnIGhlaWdodD0nMzAwcHgnIHZpZXdCb3g9JzAgMCAzMDAgMzAwJz4KPCEtLSBFTkQgT0YgSEVBREVSIC0tPgo8cmVjdCBzdHlsZT0nb3BhY2l0eToxLjA7ZmlsbDojRkZGRkZGO3N0cm9rZTpub25lJyB3aWR0aD0nMzAwJyBoZWlnaHQ9JzMwMCcgeD0nMCcgeT0nMCc+IDwvcmVjdD4KPHRleHQgZG9taW5hbnQtYmFzZWxpbmU9ImNlbnRyYWwiIHRleHQtYW5jaG9yPSJzdGFydCIgeD0nMTI0LjYzNicgeT0nMTU2JyBzdHlsZT0nZm9udC1zaXplOjQwcHg7Zm9udC1zdHlsZTpub3JtYWw7Zm9udC13ZWlnaHQ6bm9ybWFsO2ZpbGwtb3BhY2l0eToxO3N0cm9rZTpub25lO2ZvbnQtZmFtaWx5OnNhbnMtc2VyaWY7ZmlsbDojM0I0MTQzJyA+PHRzcGFuPkF1PC90c3Bhbj48L3RleHQ+Cjwvc3ZnPgo=data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0nMS4wJyBlbmNvZGluZz0naXNvLTg4NTktMSc/Pgo8c3ZnIHZlcnNpb249JzEuMScgYmFzZVByb2ZpbGU9J2Z1bGwnCiAgICAgICAgICAgICAgeG1sbnM9J2h0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnJwogICAgICAgICAgICAgICAgICAgICAgeG1sbnM6cmRraXQ9J2h0dHA6Ly93d3cucmRraXQub3JnL3htbCcKICAgICAgICAgICAgICAgICAgICAgIHhtbG5zOnhsaW5rPSdodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rJwogICAgICAgICAgICAgICAgICB4bWw6c3BhY2U9J3ByZXNlcnZlJwp3aWR0aD0nODVweCcgaGVpZ2h0PSc4NXB4JyB2aWV3Qm94PScwIDAgODUgODUnPgo8IS0tIEVORCBPRiBIRUFERVIgLS0+CjxyZWN0IHN0eWxlPSdvcGFjaXR5OjEuMDtmaWxsOiNGRkZGRkY7c3Ryb2tlOm5vbmUnIHdpZHRoPSc4NScgaGVpZ2h0PSc4NScgeD0nMCcgeT0nMCc+IDwvcmVjdD4KPHRleHQgZG9taW5hbnQtYmFzZWxpbmU9ImNlbnRyYWwiIHRleHQtYW5jaG9yPSJzdGFydCIgeD0nMTcuNTAwOScgeT0nNDcuNzk1NScgc3R5bGU9J2ZvbnQtc2l6ZTozOHB4O2ZvbnQtc3R5bGU6bm9ybWFsO2ZvbnQtd2VpZ2h0Om5vcm1hbDtmaWxsLW9wYWNpdHk6MTtzdHJva2U6bm9uZTtmb250LWZhbWlseTpzYW5zLXNlcmlmO2ZpbGw6IzNCNDE0MycgPjx0c3Bhbj5BdTwvdHNwYW4+PC90ZXh0Pgo8L3N2Zz4K[Au]PCHJSUWPFVWCPO-UHFFFAOYSA-N0.000description1
Images
Classifications
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading, distribution or shipping; Inventory or stock management, e.g. order filling, procurement or balancing against orders
- G06Q10/087—Inventory or stock management, e.g. order filling, procurement, balancing against orders
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading, distribution or shipping; Inventory or stock management, e.g. order filling, procurement or balancing against orders
- G06Q10/087—Inventory or stock management, e.g. order filling, procurement, balancing against orders
- G06Q10/0875—Itemization of parts, supplies, or services, e.g. bill of materials
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/20—Point-of-sale [POS] network systems
- G06Q20/203—Inventory monitoring
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce, e.g. shopping or e-commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping
- G06Q30/0621—Item configuration or customization
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce, e.g. shopping or e-commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping
- G06Q30/0623—Item investigation
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce, e.g. shopping or e-commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping
- G06Q30/0631—Item recommendations
Abstract
Description
- This application claims priority from U.S. provisional application 60/722,130, filed Sep. 29, 2005, incorporated herein by reference.
- The present invention relates generally to systems and methods for software integration and factory deployment of the software.
- Producing consumer electronics and in particular computers that might incorporate, in addition to operating systems with various configurations and suites of applications, several subsystems, each in turn with their own software drivers, can be complicated. Not only must a bill of materials (BOM) be defined, managed, and conformed to, but product defects and corrective actions must also be managed in way that ensures corrective action can be known and taken across the globe.
- Because of the complexity inherent in the above considerations, it can happen that more than a single management system might develop over time, complicating efforts to integrate knowledge and data. As recognized herein, it is desirable to have a management system that can integrate the knowledge and input of designers, engineers, software integrators, etc. in ways that reduce engineering lead times and provide ease of tracking defects and cures to the defects in a single, globally shared system within an enterprise, while providing an easy way to manage regional differentiation of software offerings, sharing information between business groups within the enterprise, and eliminating duplicative data maintenance.
- For example, many computers are sold on a configure to order/build to order (CTO/BTO) basis. Each software part can have a multidimensional relationship with each stock keeping unit (SKU) that represents a product when region, language, various operating system versions, and platforms are factored in. Thus, each software part can potentially have dozens of version releases to accommodate all of these variables. As but one example of the complexity of providing CTO/BTO computers, one version of a “click to DVD” software may be used only on French Windows MCE SR series SKUs that are sold only in Quebec, but another version may be designed to work on any model using Windows XP Home Edition Spanish Version regardless of region.
- As another example of complexity, consider that there are currently about ten Sony VAIO platforms worldwide, and each platform may contain multiple VAIO models with variations on CPU, RAM, HDD capacity, wireless (WLAN, WWAN, and Bluetooth), graphics chipset, etc. Several major regions that include an even greater number of languages in many different countries, along with plural operating system variations, may require support. Still further, each model of VAIO for each region/language/country/OS variation contains well over one hundred pieces of software, each of which may be a unique version for only that model, or may be used for multiple models of VAIO, giving an idea of the exponential scope of the relationship between software and computer models the database must be designed to support. In summary, the relationships between software parts and the platforms they are used on have become extremely complex, and with this critical recognition in mind, the invention herein is provided.
- In addition, the present invention critically recognizes that the quality of the final product is important. As understood herein, each piece of software may contain defects, or when combined in an image with other software may cause defects to be generated.
- As set forth further below, processes and tools are provided herein for quickly assessing the quality of a project by relating the defects to part releases, which are in turn related to projects. For example, if a major flaw is found in a particular release version of a part, this defect is related to the appropriate part release or releases so that the defect is instantly related to all the projects that use the particular part release. Given the complexity of the software BOMs, without the present invention this task would be difficult and time consuming to do manually.
- Thus, preferred implementations of the present invention correlate the relationships between software parts, the platforms they are used on, and the quality of those parts.
- A method is disclosed for managing computer production in an enterprise. The method includes receiving a block of software offerings, with each block being associated with at least one product series. A product series component structure is received that defines parts for a respective product series. Parts that are required for a product series are added to the block associated with the series, with parts being assigned to each software class and related software specification pair in a block based on the part or parts required for the pair to thereby define a design structure. The method includes establishing a software bill of materials (BOM) based on the design structure using a template and/or a snapshot.
- In non-limiting implementations the method includes defining software offerings. A software offering includes at least one software class and at least one associated software specification. Software offerings are associated with respective product series to establish a configuration, with configurations cumulatively defining a configuration range that contains product offerings of the enterprise for all regions in which the enterprise does business. The method may include grouping classes into blocks. A block is associated with at least one product series.
- The non limiting method may also include defining which classes are dependent on each other, and defining which blocks are base blocks. Defects can be associated with related classes and corrective actions associated with respective defects.
- If desired, the method can includes associating a respective installation file with each software offering. Each installation file may include a data file format version number, a version number of an installation data snapshot, an installation order for modules, data required for confirming successful installation, cyclic redundancy check (CRC) data for each binary file, path information thr locating files in a file store, partition size information for recovery and customer partitions. Also, installation anal recovery tools may use a list of software releases directly instead of microcode, which is used only for customer recovery, with microcode bit mappings being constrained to respective recovery media sets.
- In another aspect, a software management database on a computer readable medium can contain data structures supporting computer software provisioning for a range of CTO/BTO variations, language variations, region variations, and operating system variations.
- Non-limiting data structures may include bill of materials (BOM) entities containing information related to parent BOMs and child BOMs, if any. Each BOM entity can also include an engineering part ID, a software release ID, a major version ID, a group ID, a component ID, a planning parts ID, and a software series ID. A plan parts entity can also be provided that includes launch dates for software base releases, import dates for software bases indicating when the bases were imported into computers, and identifications for software bases.
- Other non-limiting entities in the database may include component entities including launch dates for software base releases, import dates for software bases, identifications for software bases. Software release entities containing a base ID, a name, a file path, a launch date can also be provided, as can be software release status entities that include data representing status and name of a software release. Additional database entities may include: a group entity containing data representing a name and launch of a type, a series entity containing a software series ID, base ID, name, an indication of being active, a launch date, an import date, an engineering parts entity containing an engineering part ID, a base ID, a type ID, a name, a launch date, and indication of dependent parts, an engineering parts major revision entity containing information related to default use, an engineering part software release entity containing information on a related engineering part entity, a related engineering parts major revision entity, a related language code entity, and a language entity containing information related to a language name and a language code.
- In another aspect, a computer-implemented system for creating bills of materials (BOMs) includes logic that can be executed by a computer and stored on a computer readable medium. The logic facilitates creation of BOMs using templates and/or snapshots. BOMs can be automatically generated based on part attributes and groups of parts, major versions, and releases. The logic can automatically check BOMs to reduce errors.
- In still another aspect, a computer system executing logic stored on a computer readable medium enters, into a first database, first software data. The first software data includes operating systems and configure to order build to order (CTO/BTO) options. The system transfers at least some of the first software data in the first database to a comprehensive global database, referred to herein colloquially as “ePic.” Second software data such as operating system updates, device drivers, and utilities is automatically adding to a bill of materials (BOM) through the comprehensive global database. Also, software along with metadata that describes the software can be checked into the comprehensive global database by users, and the BOM for a specific series/language/region can be frozen/locked and the process to create factory deliverables including software image, software modules, and data can then begin.
- The database tracks defects and relates them to parts, stores test cases which are related to parts which in turn allows test strategies to be auto-generated.
- The details of the present invention, both as to its structure and operation, can best be understood in reference to the accompanying drawings, in which like reference numerals refer to like parts, and in which:
- In the present non-limiting implementation, only part of the software data is contained in a data store referred to below as “DB Hero”. Specifically, software data that is visible to customers (e.g., operating systems, configure to order/build to order (CTO/BTO) options, software highlighted on web sites, etc.) is entered into DB Hero. As set forth in the specification below, periodically, some of the data from DB Hero is pushed to a comprehensive global database referred to herein as ePic, including both stock keeping unit (SKU) data and software data.
- Software data that is not as visible to customers (such as operating system updates, device drivers, utilities, etc.) are added to the bill of materials (BOM) through the comprehensive global database. Software is checked into the comprehensive global database by developers, vendors or engineers, along with metadata that describes the software for process tools. The BOM for a specific series/language/region is frozen/locked and the process to create the factory deliverables (software image, software modules, and data) can then be started. As set forth in the detailed specification below, various process tools and manual process can be used to create the factory deliverables, all of which use data stored in the comprehensive global database.
- Additionally, the factory deliverables are tested and validated to meet quality standards. The factory deliverables, and the metadata that describes them, are then delivered to the factory to be used in mass production.
- To better understand terms used herein, the range of potential software offerings for a given sales cycle is defined as a set of classes and specifications. The class structure captures how the various software items will be offered to the customer, and is a specific type of software. Specifications, on the other hand, are individual software items that are associated with classes. Thus, a specification is an option that the customer may choose within a class, and a class may have more than one specification while a specification is assigned to only one class. Software offerings (classes and specifications) are associated with individual series, with the resulting structure being called the “configuration range,” The configuration range for a SKU is a list of all the Classes (and specifications) that are offered for that SKU.
- By way of non-limiting example only, a “class” might be “pre-installed office software”, and specifications within that class from which the customer can select might be “MS Office professional”, “MS Office Small Business”, “MS Office Basic”, and “MS Works.”
- With the detailed description below it will be appreciated that the database herein supports software variations in CTO/BTO, language, region, and OS. In addition, this database, and the tools that use it, allow for the creation of CTO systems, based on individual customer orders, in the mass production process with every piece of software preinstalled and ready to use, allowing for a virtually infinite number software offerings to customers as opposed to a few pre-defined options.
- Also, unnecessary duplicate data entry is eliminated, hardware components are automatically mapped to software releases, and developers can specify language and geographic region supported for each software release at the time of software check-in, with the correct release being assigned to each BOM automatically. Further, BOMs are created using templates and snapshots for efficiency. Moreover, BOMs are automatically generated based on part attributes to reduce effort, and groups of parts, major versions, and releases can be defined and reused. Automatic checking of the BOMs is provided to reduce errors. In addition, installation and recovery tools use a list of software releases directly instead of microcode, which is used only for customer recovery, with microcode bit mappings being constrained to each recovery media set that is defined. This solves the problem of limited microcode bits and makes the changing of a recovery key easier.
- Below are details of one non-limiting implementation of present principles, illustrates that the present methods may be undertaken by a computer system 10 including one or more enterprise computers 12, each potentially having its own monitor 14 which can display the screen shots described below. The enterprise computers 12 can be used by developers and software engineers to execute the invention. Thus, the logic and the databases herein (including the so-called “DBHero” database 16 and global database 18, referred to herein as “epic”) may be distributed over plural computers if desired, and some of the method steps may be undertaken by human users of the enterprise computers 12 while other method steps can be undertaken automatically by logic resident on computer readable media in computers. The computer readable media can include but is not limited to RAM, ROM, floppy disks, hard disk drives, optical disk drives, solid state memory devices, etc.
- Referring briefly to out of turn, logic for creating BOMs is shown. Beginning at start state 20, a software developer or integrator selects a software series, discussed above, from a list of series. The series can include data on software that an end user ordinarily “sees”, e.g., operating systems and configure to order/build to order (CTO/BTO) software options.
- A human language and/or geographic region is selected at state 24 and then based on the selected language and region, at state 26 a processor in one or more of the enterprise computers 12 shown in can retrieve a list of component parts, including images and modules. These component parts typically include software the end user ordinarily does not “see” such as operating system updates, device drivers, and utilities.
- The software integrator then selects the image or module to be built at state 28, and at state 30 a BOM snapshot from a list is selected for the part selected at state 28. In response, a processor in one or more of the enterprise computers 12 shown in then downloads, at state 32, BOM items from a file store that may be resident in the global database 18 shown in to create an image to be loaded onto a computer to be vended. The image is checked in to the global database 18 at state 34 and uploaded to the file store, from whence it may be downloaded in the factory and loaded onto a computer to be vended. The process ends at state 36.
- A detailed description of a non-limiting implementation of the invention follows below.
- Enable a global software CTO process which can be used for all VAIO business styles (CTO, BTO, Retail).
- Redesign the software process from design through manufacturing to be a global process.
- Define a global modular software specification.
- Define a global recovery specification.
- Integrate the software and hardware design process.
- Shorten lead-time to market.
- Reduce engineering costs.
- Shift engineering resources from maintenance roles to value-add development roles.
- Maintain product quality in the new process.
- Create a flexible process and system.
- Automate tasks where appropriate to create greater accuracy and speed in activities.
- World-wide scalability.
- Global access to system (including third parties).
- Data portability.
- Multi-language handling for software items.
- Seamless interfaces to DH Hero.
- Turn-key factory deployment.
- LangRegion Specifications (Specs) in DB Hero will be reused between series.
- Software parts in DB Hero will be defined so that the “Part Name” and “Major Version” will be separate fields.
- No language/region specific information will be entered for parts into DB Hero unless royalty/licensing requirements differ by language/region for the given software part.
- Product Planner
- Determines the VAIO hardware and software offerings to be made to customers.
- Program Manager
- Works with product planners, sales and marketing, and engineering to produce a detailed product plan and offering strategy for each VAIO product series.
- Software Developer
- Develops software to be included in VAIO product offerings.
- Prepares software so that it may be delivered to the factory for installation on products.
- Software Integrator
- Uses OPK (OEM Pre-installation Kit) in combination with build systems to prepare images.
- Prepares data used in the factory to convert manufacturing bills of materials (BOMs) to a list of software items for installation.
- Prepares data used to facilitate the software recovery by the customer in the event of a failure with their VAIO product.
- Project Test Lead
- Person in charge of preparing test cases and test strategies for a series and/or project (project would be Windows beta or VAIO mouse—this concept is not managed by ePic).
- Assesses defects and devises test strategies to ensure they are fixed.
- Test Lead
- Tester in charge of an individual software release/component
- Maintain test cases as requirements change.
- Resolves defects.
- Tester
- Tests software deliverables to ensure quality product.
- Identifies and tracks defects.
- Reports quality status.
- Sometimes maintains test cases as requirements change.
- Factory Engineer
- Deploys the tools and software deliverables to the factory floor so that they may be automatically installed.
- Collects data produced in the factory installation process and delivers it to a data warehouse.
- Customer
- Makes hardware and software choices when placing an order for a custom product.
- Initiates the recovery process in the event of a system failure.
- The customer does not interact with the SIFD system directly.
- 3 Party Developer
- Checks current software releases.
- 3rd Party Factory Engineer/QA Tester
- Downloads or receives software deliverables and tools.
- Product Planner
- The Software Integration and Factory Deployment Project solution will operate within the context of the new design process specified as part of the DB Hero project. represent a non-limiting version of DB Hero process.
- do not include software related tasks. One objective of the proposed invention is to integrate the software and hardware design processes.
- 1. Software Planning and Design
- a. Description
- i. Program Managers and Product Planners define software offerings.
- b. Inputs
- i. Previous cycle's software offerings.
- ii. New software offerings.
- c. Outputs
- i. Configuration (Config) Range and Component Structure.
- d. System Interactions
- i. Offering structure and planning parts are entered in DB Hero.
- ii. Planning Parts and Component Structure are transferred to ePic.
- a. Description
- a. Description
- i. Register engineering parts and develop software.
- b. Inputs
- a. Description
RStudio Connect API Reference 1.0.1
Build 1.7.4.2-16
This is a reference document explaining the RStudio Connect API. Please note that paths are relative to the base API URL (i.e., )
The RStudio Connect API can be used to perform certain user actions remotely. You will need to install a tool or library that can make HTTP requests, such as:
- httr (R HTTP library)
- cURL (Linux tool for making HTTP calls)
- requests (Python HTTP library)
Versioning of the API
The RStudio Connect Server API uses a simple, single number versioning scheme as noted as the first part of each endpoint path. This version number will only be incremented in the event that non-backward compatible changes are made to an existing endpoint. Note that this occurs on a per-endpoint basis; see the section on deprecation below for more information.
Changes that are considered backward compatible are:
- New fields in responses.
- New non-required fields in requests.
- New endpoint behavior which does not violate the current functional intent of the endpoint.
Changes that are considered non-backward compatible are:
- Removal or rename of request or response fields.
- A change of the type or format of one or more request or response fields.
- Addition of new required request fields.
- A substantial deviation from the current functional intent of the endpoint.
The points relating to functional intent are assumed to be extremely rare as more often such situations will result in a completely new endpoint, which makes the change a backward compatible addition.
Experimentation
RStudio Connect labels experimental endpoints in the API by including in the endpoint path immediately after the version indicator. If an endpoint is noted as experimental, it should not be relied upon for any production work. These are endpoints that RStudio Connect is making available to our customers to solicit feedback; they are subject to change without notice. Such changes include anything from altered request/response shapes, to complete abandonment of the endpoint.
This public review of an experimental endpoint will last as long as necessary to either prove its viability or to determine that it’s not really needed. The time for this will vary based on the intricacies of each endpoint. When the endpoint is finalized, the next release of RStudio Connect will mark the experimental path as deprecated while adding the endpoint without the prefix. The path with the experimental prefix will be removed six months later. The documentation for the endpoint will also note, during that time, the original, experimental, path.
All experimental endpoints are clearly marked as such in this documentation.
Deprecation and Removal of Old Versions
It is possible that RStudio Connect may decide to deprecate an endpoint. This will happen if either the endpoint serves no useful purpose because it’s functionality is now handled by a different endpoint or because there is a newer version of the endpoint that should be used.
If a deprecated endpoint is called, the response to it will include an extra HTTP header called, and will have as a value the path of the endpoint that should be used instead. If the functionality has no direct replacement, the value will be set to .
Deprecated versions of an endpoint will be supported for 1 year from the release date of RStudio Connect in which the endpoint was marked as deprecated. At that time, the endpoint is subject to removal at the discretion of RStudio Connect. The life cycle of an endpoint will follow these steps.
- The is public and in use by RStudio Connect customers.
- RStudio Connect makes available for testing and feedback. Customers should still use for production work.
- RStudio Connect moves version 2 of the endpoint out of experimentation so, all within the same release:
- is marked as deprecated.
- is marked as deprecated.
- is made public.
- Six months later, is removed from the product.
- Twelve months later, is removed from the product.
Note that it is possible that RStudio Connect may produce a new version of an existing endpoint without making an experimental version of it first. The same life cycle, without those parts, will still be followed.
Authentication
Most endpoints require you to identify yourself as a valid RStudio Connect user. You do this by specifying an API Key when you make a call to the server. The API Keys chapter of the RStudio Connect User Guide explains how to create an API Key.
API Keys
API Keys are managed by each user in the RStudio Connect dashboard. If you ever lose an API Key or otherwise feel it has been compromised, use the dashboard to revoke the key and create another one.
Once you have an API Key, you can authenticate by passing the key with a prefix of (the space is important) in the Authorization header.
Below are examples of invoking the "Get R Information" endpoint.
cURL
R
Python
Endpoints
The URIs for all endpoints below must be prefixed with to function properly. Unless otherwise noted, all endpoints which accept a request body will require the body to be in format. Similarly, all response bodies will be returned in format.
Audit Logs
These endpoints let you obtain auditing information.
This endpoint returns a portion of the audit logs, as well as paging information that can be used to navigate the audit log results.
This endpoint uses keyset pagination. The Keyset Pagination recipe in the RStudio Connect User Guide has example code for fetching multiple pages.
Request
Parameters
| integer (int32) (query) Number of logs to return. The minimum supported value is 1 and maximum supported value is 500. Note that is a "best effort" request since there may not be enough logs to satisfy the limit. It has a default value of . |
| string (query) Gets the previous page of audit logs relative to the given id. |
| string (query) Gets the next page of audit logs relative to the given id. |
| boolean (query) Whether the audit logs should be listed in ascending order It has a default value of . |
Responses
| AuditLogs The audit logs results and paging information |
| APIError The requested operation is invalid. |
| APIError The requested operation requires authentication. |
| APIError You do not have permission to perform this operation. |
| APIError The requested object does not exist. |
A server error occurred. |
| APIError An error occurred invoking the API. |
Bundles
These endpoints let you manage and obtain information about content bundles.
Get detailed information about a specific bundle.
Request
Parameters
| string (path) (required) The unique identifier of the desired bundle. |
Responses
| Bundle The bundle details. |
| APIError The requested operation is invalid. |
| APIError The requested operation requires authentication. |
| APIError You do not have permission to perform this operation. |
| APIError The requested object does not exist. |
A server error occurred. |
| APIError An error occurred invoking the API. |
Delete a specific bundle.
On-disk data and database records are removed as a consequence of this call. Deletion is not allowed while the bundle is still active.
Request
Parameters
| string (path) (required) The unique identifier of the desired bundle. |
Responses
Returned when the bundle was successfully removed. |
| APIError The requested operation is invalid. |
| APIError The requested operation requires authentication. |
| APIError You do not have permission to perform this operation. |
| APIError The requested object does not exist. |
A server error occurred. |
| APIError An error occurred invoking the API. |
Download a deployment bundle.
Download a compressed archive () containing the code/data from one deployment of the associated content.
See the endpoint for details about the construction of bundle archives.
Request
Parameters
| string (path) (required) The unique identifier of the desired bundle. |
Responses
| string (binary) A compressed archive file. |
| APIError The requested operation is invalid. |
| APIError The requested operation requires authentication. |
| APIError You do not have permission to perform this operation. |
| APIError The requested object does not exist. |
A server error occurred. |
| APIError An error occurred invoking the API. |
List bundles associated with a specific content item.
Results are sorted by ID.
Pagination
This endpoint uses offset pagination (using page numbers). The Offset Pagination recipe in the RStudio Connect User Guide has sample code for fetching multiple pages from a list endpoint.
Request
Parameters
| string (uuid) (path) (required) The unique identifier of the desired content item. |
| integer (int32) (query) The page to return relative to the given . If is 0 or negative, an error will be returned. It has a default value of . |
| integer (int32) (query) The number of items to include in each page. This parameter is "best effort" since there may not be enough bundles to honor the request. If is less than 1 or greater than 500, an error will be returned. It has a default value of . |
Responses
| Bundles The list of bundles. |
| APIError The requested operation is invalid. |
| APIError The requested operation requires authentication. |
| APIError You do not have permission to perform this operation. |
| APIError The requested object does not exist. |
A server error occurred. |
| APIError An error occurred invoking the API. |
Content
These endpoints let you manage and obtain information about content hosted by RStudio Connect.
Create a new content item.
Authenticated access from a user having either "publisher" or "administrator" role is allowed. All other clients are rejected.
Request
Parameters
| Content (body) (required) The request body required when creating a new content item. |
Responses
| Content The details for the newly created content. |
| APIError The requested operation is invalid. |
| APIError The requested operation requires authentication. |
| APIError You do not have permission to perform this operation. |
| APIError The requested object does not exist. |
A server error occurred. |
| APIError An error occurred invoking the API. |
Get detailed information about a specific content item.
Unauthenticated clients are rejected regardless of the content access type.
Authorized, non-administrator clients without viewership rights to this content are rejected.
Authorized, administrator clients without viewership rights are permitted to obtain information about this content. The computed for these users will be , representing that these users cannot view the content itself.
Authorized clients with viewership (or collaborator) rights are permitted to obtain information about this content. The computed for these users will reflect the level of access.
Request
Parameters
| string (uuid) (path) (required) The unique identifier of the desired content item. |
Responses
| Content The requested content details. |
| APIError The requested operation is invalid. |
| APIError The requested operation requires authentication. |
| APIError The requested object does not exist. |
A server error occurred. |
| APIError An error occurred invoking the API. |
Update fields for a specific content item.
Authenticated access from a user having either "publisher" or "administrator" role is allowed. All other clients are rejected.
Authorized clients with collaborator or administrator rights are permitted to modify content item fields.
Request
Parameters
| string (uuid) (path) (required) The unique identifier of the desired content item. |
| Content (body) (required) The request body required when creating a new content item. |
Responses
| Content The details for the newly created content. |
| APIError The requested operation is invalid. |
| APIError The requested operation requires authentication. |
| APIError You do not have permission to perform this operation. |
| APIError The requested object does not exist. |
A server error occurred. |
| APIError An error occurred invoking the API. |
Delete a specific content item.
On-disk data and database records are removed as a consequence of this call.
Request
Parameters
| string (uuid) (path) (required) The unique identifier of the desired content item. |
Responses
Returned when the content was successfully removed. |
| APIError The requested operation is invalid. |
| APIError The requested operation requires authentication. |
| APIError The requested object does not exist. |
A server error occurred. |
| APIError An error occurred invoking the API. |
Deploy (activate) a deployment bundle.
Deployment requests spawn an asynchronous task to make your previously uploaded data available for serving. The workflow applied to the bundled files varies depending on the type of content.
Executable content has its environment reconstructed. This includes using the R package to install R package dependencies.
Documents (R Markdown reports, Jupyter Notebooks) are rendered and the result made available.
Interactive content (Shiny applications, Plumber APIs) available to be launched on the next client visit.
The deployment workflow for static content (HTML, plots) is lighter-weight than for executable content. File time-stamps are updated to ensure that browsers do not cache previous results and instead see the newly promoted files.
The response from this endpoint includes a task identifier. Poll the endpoint to track the progress of this task.
Request
Parameters
| string (uuid) (path) (required) The unique identifier of the desired content item. |
| ContentDeploymentInstructions (body) The request body when requesting the deployment of a bundle. |
Responses
| ContentDeploymentTask The requested content details. |
| APIError The requested operation is invalid. |
| APIError The requested operation requires authentication. |
| APIError The requested object does not exist. |
A server error occurred. |
| APIError An error occurred invoking the API. |
Upload a new deployment bundle.
Upload a compressed archive containing code/data that represent one deployment of this content. Bundles must be compressed archives.
All deployment bundles include a describing the contained files and their runtime dependencies.
A bundle for a Shiny application include an or and , and any images or data files required by the application.
An R Markdown document bundle includes the file along with any R scripts and data files needed to render the report.
Bundles containing HTML content would include the CSS, Javascript, and images required by that document.
The archive paths for the file and primary source files like or must not specify a directory structure. Directories may be used for secondary data and scripts.
Here is how you might use to create an archive for a Shiny application. It includes the manifest, the application, and an image.
Here is another example of creating a bundle for that same application but from its parent directory. The Shiny application is in a sub-directory.
Both commands will produce an archive with the and at the top-most level.
Publishers with collaborator rights to this content (including the owner) are permitted to upload deployment bundles. Users without these rights are rejected.
Administrators must be a collaborator for a content item before they receive upload rights.
Request
Parameters
| string (uuid) (path) (required) The unique identifier of the desired content item. |
| string (binary) (body) (required) A compressed archive file. |
| string (header) The MD5 sum of the archive file. |
Responses
| ContentUploadBundle The requested content details. |
| APIError The requested operation is invalid. |
| APIError The requested operation requires authentication. |
| APIError The requested object does not exist. |
A server error occurred. |
| APIError An error occurred invoking the API. |
Groups
These endpoints let you manage user groups.
This endpoint lists or searches for local groups.
- For a search, results are sorted based on similarity to the . A search ignores . The first page of results will always be returned.
- For a non- search, results are sorted by group name.
- For LDAP authentication, this endpoint executes an unbounded LDAP query. Instead, is applied locally by RStudio Connect.
Pagination
This endpoint uses offset pagination (using page numbers). The Offset Pagination recipe in the RStudio Connect User Guide has sample code for fetching multiple pages from a list endpoint.
Request
Parameters
| string (query) Filters groups by prefix (group name). The filter is case insensitive. |
| integer (int32) (query) The page to return relative to the given . If is 0 or negative, an error will be returned. For a search, the first page of results will always be returned. It has a default value of . |
| integer (int32) (query) The number of items to include in each page. This parameter is "best effort" since there may not be enough groups to honor the request. If is less than 1 or greater than 500, an error will be returned. It has a default value of . |
| boolean (query) Whether or not to return the groups in ascending order, sorted by name. For a search, results are sorted first by exact match, then by increasing word length. It has a default value of . |
Responses
| Groups The search results |
| APIError The requested operation is invalid. |
| APIError The requested operation requires authentication. |
A server error occurred. |
| APIError An error occurred invoking the API. |
This endpoint creates the given group on the RStudio Connect server.
- This endpoint is used only for LDAP authentication. Password, PAM, SAML, OAuth2 and Proxied authentication providers should use the endpoint.
- Publisher or administrator access is required to access this endpoint.
Group Creation Workflow on LDAP
The API lets you identify an existing group in the LDAP system and create a corresponding group on RStudio Connect. This is a two-step process:
- Use the endpoint. This endpoint will return a list of potential matching groups in LDAP. A group that does not exist in RStudio Connect will lack a . Note the for the desired group.
- Use this PUT endpoint with the to create a corresponding group on RStudio Connect.
The Create a Group from LDAP recipe in the RStudio Connect User Guide contains a recipe with sample code.
Request
Parameters
| (see below) (body) (required) The request body needed for creating a group on the RStudio Connect server. |
Body Schema
The body for this request must be specified as follows:
| string (required) The temporary ticket used for creating a group on the RStudio Connect server. It is obtained from the endpoint. |
Here is an example of what it may look like:
Responses
| Group The group object |
| APIError The requested operation is invalid. |
| APIError The requested operation requires authentication. |
| APIError You do not have permission to perform this operation. |
| APIError The requested object does not exist. |
| APIError The request could not be completed due to a conflict. |
A server error occurred. |
| APIError An error occurred invoking the API. |
This endpoint creates the given group.
- This endpoint is available only when groups are enabled in RStudio Connect and only for Password, PAM, OAuth2, SAML and Proxied authentication.
- Publisher or administrator access is required to create groups.
Request
Parameters
| (see below) (body) (required) The new group values. |
Body Schema
The body for this request must be specified as follows:
| string (required) The group's desired name |
Here is an example of what it may look like:
Responses
| Group The group object |
| APIError The requested operation is invalid. |
What’s New in the HTTP Analyzer IE Add-in Edition 1.7.4.2 serial key or number?
Screen Shot
System Requirements for HTTP Analyzer IE Add-in Edition 1.7.4.2 serial key or number
- First, download the HTTP Analyzer IE Add-in Edition 1.7.4.2 serial key or number
-
You can download its setup from given links:
HTTP Analyzer IE Add-in Edition 1.7.4.2 serial key or number & PC Free Download
HTTP Analyzer IE Add-in Edition 1.7.4.2 serial key or number& Key Download
HTTP Analyzer IE Add-in Edition 1.7.4.2 serial key or number
About Author
